enumerator4829

joined 1 year ago

The fundamental architectural issue with Wayland is expecting everyone to implement a compositor for a half baked, changing, protocol instead of implementing a common platform to develop on. Wayland doesn’t really exist, it’s just a few distinct developer teams playing catch-up, pretending to be compatible with each other.

Implementing the hard part once and allowing someone to write a window manager in 100 lines of C is what X did right. Plenty of other things that are bad with X, but not that.

Tell me you never deployed remote linux desktop in an enterprise environment without telling me you never deployed remote desktop linux in an enterprise environment.

After these decades of Wayland prosperity, I still can’t get a commercially supported remote desktop solution that works properly for a few hundred users. Why? Because on X, you could highjack the display server itself and feed that into your nice TigerVNC-server, regardless of desktop environment. Nowadays, you need to implement this in each separate compositor to do it correctly (i.e. damage tracking). Also, unlike X, Wayland generally expects a GPU in your remote desktop servers, and have you seen the prices for those lately?

Programmers use butterflies.

Real sysadmins use programmers.

[–] enumerator4829@sh.itjust.works 4 points 5 days ago (1 children)

The M-series hardware is locked down and absofuckinglutely proprietary and locked down and most likely horrible to repair.

But holy shit, every other laptop I’ve ever used looks and feels like a cheap toy in comparison. Buggy firmware that can barely sleep, with shitty drivers from the cheapest components they could find. Battery life in low single digits. The old ThinkPads are kinda up there in perceived ”build quality”, but I haven’t seen any other laptop that’s even close to a modern macbook. Please HP, Dell, Lenovo, Framework or whoever , just give me a functional high quality laptop. I’ll pay.

Moving people from closed commercial offerings onto something self hosted is enough work without gatekeeping US open source projects, even if they are flawed. If we want to move normal people away from the commercial offerings onto something better, we can’t do things like that. Better save such warnings for when they are actually needed (”Project X has been dead for five years and is full of security holes, you should migrate to project Y instead”). Keep the experience positive regardless.

You do you, but different people have differing requirements and preferences. Don’t scare them away please.

[–] enumerator4829@sh.itjust.works 1 points 1 week ago (1 children)

Because dockers record with regards to security is questionable, and some people like to get automatic updates from their distro. For me personally, I think the design of Docker is absolute garbage. Containers are fine, but Docker is not the correct mechanism for it. (It’s also nothing new, see BSD jails and Solaris zones.)

Immich on Nixos works perfectly, and I also get automatic updates.

If you stay on X, you can keep using the same window manager for longer. My XMonad config is over a decade old, and I bet my old dwm config.h still compiles.

The relative size of the double handling is the potential problem. I think Nvidia is just trying to extend the gold rush for a bit longer.

[–] enumerator4829@sh.itjust.works 1 points 1 month ago (1 children)

Agreed, it’s not perfect, especially not with regards to drivers from some of them. But:

https://insights.linuxfoundation.org/project/korg/contributors?timeRange=past365days&start=2024-12-31&end=2025-12-31

I expect that the ability of B2C-products to keep their code somewhat closed keeps them from moving to other platforms, while simultaneously pumping money upstream to their suppliers, expecting them to contribute to development. The linked list is dominated by hardware vendors, cloud vendors and B2B-vendors.

Linux didn’t win on technical merit, it won on licensing flexibility. Devs and maintainers are very happy with GPL2. Does it suck if you own a Tivo? Yes. Don’t buy one. On the consumer side, we can do some voting with our wallets, and some B2C vendors are starting to notice.

Do this:

  • Calculate the total power cost of running it at 100% load since 2014
  • Calculate Flops/Watt and compare with modern hardware
  • Calculate MTTF when running at 100% load. Remember that commercial support agreements are 4-5 years for a GPU, and if it dies after that, it stays dead.
  • In AI, consider the full failure domain (1 broken GPU = 7+ GPUs out of commission) for the above calculation.

You’ll probably end up with 4-6 years as the usable lifetime of your billion dollar investment. This entire industry is insane. (GTX 1080 here. Was considering an upgrade until the RAM prices hit.)

[–] enumerator4829@sh.itjust.works 7 points 1 month ago (6 children)

Nvidia sells plenty of GPUs for actual money, they are good for it.

No, the real issue is the depreciation for the people owning GPUs. Your GPU will be usable for 4-6 years, and 2-4 of those years will be spent as ”the cheap old GPU. After that time, you need new GPUs. (And as the models are larger by then, you need moahr GPU)

How the actual fuck do these people expect to get any ROI on that scale with those timeframes? With training, maybe the trained model can be an asset (lol), but for inference there are basically no residual benefits.

I agree with your morals and your end goal.

How do you want to fund the development of Open Source? Because currently most of it is funded by corporations, in turn funded by ”corporatist simping”. The expectations of the average user simply can’t be fulfilled by hobbyist developers, and then we need funding. How do we get the Windows user ”John Smith” to personally fork over money to the correct developers?

Proton/Wine/KDE would not be in their current state unless they got that sweet proprietary Valve money. In our current world we need to use corporate money to further open source, not fight it. Follow the stream and steer the flow. Given time, we can diversify funding and control.

view more: next ›