The Linux Thread - The Autist's OS of Choice

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
What's more annoying is when they put their caches in ~/.tmp. I used to mount a tmpfs there, but had to stop when I realised why a bunch of programs weren't caching things properly. As a result a good third of the backup space my /home/ occupies is nonsense like picture thumbnails.

Cache: Data stored so that future uses of it will be quicker. Can be semi-permanent.
T(e)mp(orary): Data stored while actively working on it. Always temporary.


Then just set it up how you want.

 
I know how to delete files, that's not the issue. I just don't want to back them up.
I use ZFS snapshots to back up, so the easiest solution would be to just make a /home/user/.tmp dataset, and excluding it, but it's not worth the bother to save at most a few gigabytes.

Oh right, yeah in that case a dedicated ~/.tmp ZFS dataset excluded from backup snaps would be the go to but I've never had storage issues so I sympathise with you
 
Last edited:
The nice thing about standards is that there are so many of them to choose from!
xkcd 927
 
Question about Wayland.
To create a window and handle input on Linux, do I now need to implement both Xlib/XCB and libwayland-client? Or is XWayland standard? Assuming I'm not using a library like GLFW or anything similar.
 
Question about Wayland.
To create a window and handle input on Linux, do I now need to implement both Xlib/XCB and libwayland-client? Or is XWayland standard? Assuming I'm not using a library like GLFW or anything similar.
Yes, have both. XWayland is not to replace, it is used as a host for X11.
 
  • Thunk-Provoking
Reactions: HalHalliday
>"X11 is outdated and insecure, we need to develop one universal display server that covers everyone's use cases!"
>still has to wrap X11 to work properly after 16 years of development
>there are 2 competing standards
No, not really. X11 development is effectively deprecated, the only updates it's getting are patches and Wayland compatibility improvements.
There's one current standard, and one previous standard that just about everything is still backwards-compatible with.
 
Its only been the last few years when KDE (and more recently Valve) have been pushing Wayland further then Gnome and Red Hat did in the last 15 years, where it has become viable to use as a daily driver. These days, I find hardly any difference between KDE on X11 and Wayland.
I love how Red Hat has so clearly designed Wayland for Gnome, yet it still has major issues there. No sane person would want to use Gnome anyways.
 
Question about Wayland.
To create a window and handle input on Linux, do I now need to implement both Xlib/XCB and libwayland-client? Or is XWayland standard? Assuming I'm not using a library like GLFW or anything similar.
Are you making a window manager?

Depending on what you are doing. If you are just wanting to work with Wayland you likely shouldn't need to worry about xwayland. Especially if it's just a program, not an entire compositor/window manager. It really depends on specifics I'm sure.
 
Depending on what you are doing.
Trying to replicate my stack, in case I ever need to switch to or support Linux natively.

On Windows it's win32 + dx11 + wasapi, simple.
Looking at Linux, I got confused as to what the fuck Wayland is even trying to be. Replacement for X11, but also not? A library, but also a protocol? What? I've seen there's XWayland for backward compatibility, so I wanted to know if it's a standard thing and therefore everywhere, and if it won't go away tomorrow, 'cause a tranny threw a hissy fit.

To put it simply, if I can just do xlib + Vulkan + ALSA, and I'm good.
I get that it might be a stupid question, but the last Linux I used was Fedora 13 - no Wayland there!

Also: total micro-pajeet death.
 
Trying to replicate my stack, in case I ever need to switch to or support Linux natively.

On Windows it's win32 + dx11 + wasapi, simple.
Looking at Linux, I got confused as to what the fuck Wayland is even trying to be. Replacement for X11, but also not? A library, but also a protocol? What? I've seen there's XWayland for backward compatibility, so I wanted to know if it's a standard thing and therefore everywhere, and if it won't go away tomorrow, 'cause a tranny threw a hissy fit.

To put it simply, if I can just do xlib + Vulkan + ALSA, and I'm good.
I get that it might be a stupid question, but the last Linux I used was Fedora 13 - no Wayland there!

Also: total micro-pajeet death.
fedora is one of the distros currently pushing towards moving completely to wayland.

anyway. unlike what some people may say in this thread. wayland definitely isn't going away. So I wouldn't worry about that specifically.

wayland. is basically intended to be the eventual replacement for x11. being the replacement, and not an update, or a fork. It does do some thing differently. Some things are a bit more secure, (that's a bit complicated really, on whether it matters or not, doesn't hurt imo though).

one thing that is different. is it's a set of protocols. and the desktop/window manager takes care of how it's implemented. There are things like wlroots, which almost all of the tiling wayland compositors are implemented on. that are basically an effort to reduce the duplication of work that goes into making basically the entire display server (not exactly but closer to that than how x11 window managers are done). Gnome and kde have their ways they did thing. But basically. what you just need to worry about, likely is the wayland protocols, what you want to do in relation to those, and maybe what desktop you intend to use. If its fedora, I imagine that's gnome.

and yeah. xwayland, is just there for compatibility. in the long run, if you are worried about something not being there at some point. that would be the thing, that isn't around, or is at least going to be a lot more rare as time passes. Like I mentioned a couple posts up. When I'm running wayland right now, I'm not using xwayland at all. I've been able to replicate basically everything I have on x11 at this point. So I imagine that will probably get more common as time goes on.

that said. you can do xlib. I just wouldn't count on that lasting forever. especially with fedora. On other distros like arch, gentoo, debian, probably mint. I don't see them dropping xorg, well idk some probably never. But fedora, not so much. Obviously you can use ALSA across whatever.

I mean. really anything else I can say. would probably just be better read from their documentation on it, rather than paraphrasing what I remember.
 
I found the most quintessentially Arch video series on Youtube (partial archive).
Day_1.webp

I don't know why one would do this, but I suppose I'm not Linux-pilled enough. It starts off fine, little special episodes here and there.
soy.webp

There's an episode with Ultrakill in it, which is basically to trannies and faggots what Roblox is to pedophiles. Maybe it's nothing.
uhoh.webpfalse_alarm.webpself_aware.webp

Or not.
bro.webp
The full power of Arch and KDE (Komplete Dick Eliminator?)

It somehow keeps getting worse as it goes on.
worse.webp
trotters01.webp
trotters02.webp

Gentoo was too straight to be included for more than one episode.
straightoo.webp

If installing NixOS leads to a full troonout somewhere along this autistic journey, I'm going to lose it :story:

Looking at Linux, I got confused as to what the fuck Wayland is even trying to be. Replacement for X11, but also not? A library, but also a protocol? What?
Wayland is a protocol, i.e. "Here's what we recommend. There is no central focus like X11, fuck yourselves and write your own compositors". There are bound to be quirks across GNOME, KDE & minimalist implementations. Browser compatibility bullshit, now available for desktop. Wayland has XWayland, so if you just target X11 you get something that has a chance of working decently across all systems.
 

Attachments

  • trotters02.webp
    trotters02.webp
    39.3 KB · Views: 16
  • trotters01.webp
    trotters01.webp
    19.5 KB · Views: 13
  • trotters01.webp
    trotters01.webp
    19.5 KB · Views: 16
  • soy.webp
    soy.webp
    17 KB · Views: 16
  • self_aware.webp
    self_aware.webp
    10 KB · Views: 16
  • false_alarm.webp
    false_alarm.webp
    9.5 KB · Views: 12
  • bro.webp
    bro.webp
    19 KB · Views: 15
The full power of Arch and KDE (Komplete Dick Eliminator?)
The Troon Desktop seems to be Gnome in my experience, so I'm surprised that KDE was the one that caused it.
Gentoo was too straight to be included for more than one episode.
You need to wait a day or 2 before gooning on Discord with Gentoo, so that's probably why a lot of the Troons from Arch are filtered out.
If installing NixOS leads to a full troonout somewhere along this autistic journey, I'm going to lose it
The jokes write themselves. I swear there's something with Arch and Nix OS that significantly boosts the odds of becoming a Troon.
 
Back