This space left intentionally blank.

  • 0 Posts
  • 55 Comments
Joined 1 year ago
Cake day: July 1st, 2023
  • Billegh@lemmy.worldtoLinux@lemmy.ml•Why Wayland adoption to have official support in programs is so slow?
    281·
    1 month ago

    Because Wayland is fundamentally very different from the older X protocol, and many programs don’t even directly do X. They leverage libraries that do it for them. Those libraries are a huge part of the lag. Once GTK and Qt and the like start having a stable Wayland interface, you’ll see a huge influx of support.

    A big part of the slowness is why Wayland is a thing to begin with. X hid a lot of the display hardware from apps. Things like accessing 3d hardware had to be done with specialized display clients. This was because X is natively a remote display tool. You can use X to have your program show its display somewhere else. Wayland won’t do that because that’s not the point. Applications that care will have goals for change. Applications don’t care will support it once someone else does it for them.

    Right now, the only things that would benefit from Wayland are games and apps that make heavy use of certain types of hardware. Half of those don’t care about linux, while the other half is OK with X and xwayland.

  • Billegh@lemmy.worldtoLinux@lemmy.ml•Switching back to Windows. For now.
    71·
    2 months ago

    I feel all of that. Debian is painfully slow to bring up-to-date, and all of Arch is neurotic.

    You might have a better time with Fedora as they are closest to Wayland, but Fedora is pathologically open source to the point that if there aren’t open source drivers for a thing you’re triple tucked…

    Gaming on linux has been, still is, and always will be a struggle. I hope you give it a try again in a year or so. I personally use Debian as my base system, with an Arch VM on CPU and GPU passthrough for work and gaming. You’ll get there eventually! ☺️

  • Billegh@lemmy.worldtoProgramming@programming.dev•POSIX.1-2024 has been published
    3·
    3 months ago

    Shell scripts were a mistake.

    I understand 1000% but I’m not sure I agree. With the peevishness of C and latent autism of assembly, something compiled or otherwise binary isn’t always simple and straightforward. Sometimes, you have a task that only needs to be done three times, and just replaying the commands is sufficient.

    sh, ash, and bash are all kinda dumb. Absolutely. But there are other shells that are significantly better. csh and zsh are both great. ksh has some history on it but is good too. But “shell scripts” don’t have to be in your shell language. The hashbang line will let you make a command file and so long as you can describe the command line you can get most shells to run it. Be that language line noise perl or python or even go.