• 0 Posts
  • 32 Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle

  • That’s cool and all, but why would I want to? Display systems are invisible when they work right, and X has worked right for me (save for some pre-EDID config issues) since the 90s. I run a program, it pops up on my screen and I interact with it. That’s all I ask of it.

    None of the issues I’ve had with X (drivers, mostly) will be resolved with Wayland. For me, it’s a solution in search of a problem. The only reason I have even a passing interest is that it’s (theoretically) easier to maintain and change as computing changes.

    I’ll move to Wayland when I have to, but right now there’s no reason to not use X.


  • I wasn’t clear. I meant that the issues with X crashing were usually driver issues. I have no idea about Wayland - I don’t use it since it doesn’t do what I want by design.

    X does the job well enough to be invisible to most people. Yes, we need a clean start in order to move forward efficiently (lots of assumptions about computer displays from the 80s no longer apply), but it’s good enough for most people’s needs.

    Why bother with a display server? Some people - like myself - actually use that functionality. It’s not part of the design for Wayland. Personally, I think that’s a mistake - especially as things become more cloud-based - but I’m obviously in the minority.


  • Wayland wasn’t the first attempt at replacing X. It has made more traction than any other attempt, though. There’s no real hurry - it’s not like X eats your babies and runs over your dog.

    As far as robustness goes, that’s mostly the driver. I’ve yet to see a bulletproof display system, commercial or non-commercial. If you cut out driver issues, X is on par with or more stable than other systems. It had better be, given that it’s had decades of bug fixes with few new features to cause new bugs.



  • You’re listening to loud asshats and assuming they’re the majority. They’re not.

    One day Wayland will reach a tipping point where it will replace X. Until then, most users will just stick with whatever their distro installs. Most people don’t care one way or another.

    As for me, I’m probably gonna to stick with X until I have no choice because I actually use the network features that Wayland isn’t replacing. That doesn’t mean I hate Wayland - I’ve never used it - it just means it’s not the best software for me at this time. Most people never do anything with X that Wayland can’t do and won’t notice when it becomes the default.






  • It’s been bad for me.

    All those hate filled posts everyone talks about? I never saw those on Reddit, because I had a couple dozen technical subs (r/emacs, r/PLC, etc.) that I’d browse and rarely if ever strayed from those. Reddit was big enough that the specialized subreddits generated enough content for my use case.

    Some of those communities exist here, but they’re practically empty. So I wind up doom scrolling on All, which is full of tankie garbage and political propaganda.

    I dunno, while I like the idea of Lemmy, I don’t think it’s likely to ever get the traffic you need for my kind of use. I probably just need to diversify my phone use and visit other sites.





  • I don’t believe so - the docs mention several ways to boot a pi but most only work for newer models.

    An option might be to boot an SD card read-only and run everything over NFS. It’s trivial to do that sort of thing with some UNIX clones (OpenBSD, for instance), but I don’t know about a modern Linux.


  • It might be too outdated to do major services, but it’s still fine for its original use - interfacing with electronic components.

    You could build a weather station, monitor temperature and humidity in your attic and crawlspace, automatically water plants, etc. You don’t need much electronics knowledge for that sort of thing.





  • The “binaries last forever” is still very much true in my field (industrial automation). For example, companies develop functions to speed up and simplify PLC development and “lock” the code to keep their competitors from copying it.

    I was editing a PLC program on a government installation just today and ran into this. The government was never given the code (even though it rightly belongs to them) so I have to take it on faith that it’s bug-free. I rewrote it and left it unlocked.