I recently worked on a system that had the TERM variable botched and filtered and no nano, just vim. It was all hell. The escape sequences in vim wouldn’t work. I ended up suspendig it with ctrl+z, killing it, then editing the config with fucking ed and sed. That hoster sucks.
It’s because you don’t want to reinvent the wheel all the time. It sucks doing it. Lots of effort. It’s much better to build on existing stuff and maybe improve it for your needs.
I often switch between Wayland and X. My only concern is java does not yet support Wayland and old native libraries (e.g. 3D stuff for no longer maintained Java games) will probably break, once Java actually switches. Java and some Java games work with the xwayland compatibility layer, for now, but there are glitches sometimes. There are multiple projects porting Java stuff (e.g. Swing) to Wayland. All unofficial and incomplete.
I think that’s only true for the programs, not for the JVM/JRE code. The JVM/JRE doesn’t support Wayland without the xwayland compatibility layer. Also, some games use “native” libs that do optimized 3D stuff. Those are special Java classes, not part of the JVM/JRE that interface with C libs, kernels, system calls and hardware directly. Some will stop working without an X window to connect to. Some are long forgotten and won’t be ported.
Text editor war (lemmy.ml)
Low quality meme
The successor should be called Plan 69 from Bell Labs (files.catbox.moe)
Password requirements are getting out of hand (lemmy.ca)
A response to the "Boycott Wayland" article
Link to article: gist.github.com/…/9feb7c20257af5dd915e3a9f2d1f227…...
Data: It is... it is groovy. (startrek.website)