lambalicious

@lambalicious@lemmy.sdf.org

I write English / Escribo en Español.

Vidya / videojuegos. Internet. Cats / Gatos. Pizza. Nap / Siesta.

This user’s posts under CC-BY-NC-SA license. Ask me if you need a different permission.

This profile is from a federated server and may be incomplete. Browse more on the original instance.

lambalicious,

I don’t get the issue with “maintaining Xorg”. Like, I get that it has a “cost”, I just don’t understand why that cost would be an issue since it’s basically fixed, marginal cost (and has been since like 2015): the software is already mature, so it’s unlikely to see relevant changes, or even minor changes (if that’s what we want to mean with “dead”). That means, it can be affixed to a specific toolkit and environment to build (if this isn’t being done already - which any mature project like RedHat should be!) basically guaranteeing it’ll build forever. You can just set a virtual button or a yearly crontab to do it. Fixed, marginal cost.

Contrasted to that, what Wayland is doing is kinda a representation of the worst ways of capitalism: centralize the profits, socialize the costs and the externalities (redesign, recode, rebuild), and blame society (the Linux communities) for it, all for a variable cost that is unbounded in time and space because you never know what’s gonna cost a small project like a text editor to reimplement the entire desktop stack “just” for Wayland.

lambalicious,

But keeping around X isn’t the solution - iterating on Wayland is. Adding protocols to different parts of the stack with proper permission models, moving different pieces of X to different parts of the stack, etc. are a long term viable strategy. Even if it is painful.

The problem is, that’s always used as an excuse to force people to be gratis beta testers. I’ve been around for the wrecks that were (and still are) Pulseaudio and Systemd. Wayland is even worse: it doesn’t even fully start a session in my machine. If as devs you want to “iterate”, sure, go ahead; but leave it in the dev branch; as a user, don’t try to sell me Wayland again until it’s actually over.

lambalicious,

Isn’t that just chroot?

lambalicious,

Joke’s on them, I use emacs as an OS.

I need to edit text files over SSH tho, haven’t been able to find a good text editor…

lambalicious,

Anime soundtracks site

Not using the line “Awaken my archivists!”

lambalicious,

And why would this need systemd of all things? Should basically be doable over something like SSH / TFTP, right?

lambalicious,

Switch over to an ISP that doesn’t do that. Leave record with your country’s customer protection service and/or open press / open culture office that’s why you did it. There. Done.

lambalicious,

A fair point.

Still, in this case you should direct your issue to your country’s consumer protection and culture protection services. Since they are essentially charging you for an incomplete service.

Of course, there’s other measures that one can take by themself to route around the issue, such as using a VPN. But they don’t deal with the real issue at hand that is what the thread title says: that the ISP is doing something that it shoudn’t.

lambalicious,

What are you talking about, it’s about 110 songs with a good enconder, that’s like 8~10 albums.

lambalicious,

I’m not saying it in relative terms, but in absolute terms. 350 MB is lots of space that can be useful, it’s certainly not “close to nothing”.

Like, I fear to imagine how much shipping fic would I have to publish annually in order to fill 350 MB in my lifetime…

lambalicious,

Apparently at least the downvoters on that post, yes.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • localhost
  • All magazines
    •
    Loading…
    Loading the web debug toolbar…
    Attempt #