You will always need some sort of oom killer unless you have endless memory (or swap space, which comes with its own problems in the form of grinding your system to an almost halt). Imagine all memory is in use, then some system critical task (or even the kernel itself) needs memory as well. If the kernel can’t kill a less important process to free memory in such a situation you might just crash your system.

Hearing Snow by the Red Hot Chilli Peppers while my mom is folding clothes (thats a very specific one). I have no idea how old I was exactly but I remember it vividly. The funny thing is that I didn’t understand a word of the song as german is my native language. Recently I stumbled across the song again and suddenly, as if struck by lightning, I remembered this weird mundane situation as if it was yesterday. The human mind is so weird.

Nur noch dieses Monat, dann bin ich zurück in meinem alten 9 bis 17. Echt respekt an alle die das Langfristig machen, habe jetzt nicht mal ein Jahr Schichtdienst gemacht und fühle mich 10 Jahre älter. Habe gedacht ich bin 20, da geht das noch, aber ehrlich, das Geld ist es nicht wert.

Ich benutze Eselspinguin bei dem Weg.

and you can afford to lose everything in the case of a power cut

But ext4 is a journaling filesystem, so a power cut shouldn’t harm it.

I have no idea about apple design guidelines and am not a UX designer, but wouldn’t a horizontal seperator look better? In gtk i would add one here, gives some extra space and more visual seperation.

I was the same, but I recently gave zig a try, it’s lovely to write.

Managed to segfault the compiler though, so maybe not quite ready yet.

So I don’t even use systemd myself I run OpenRC. Yet honestly I find the idea quite intriguing, having the service manager (PID 1) invoke the command seems like a cool idea to me.

It’s not really a sudo alternative as much as it is another way of doing something similar.

BMW badge (because BMW drivers seem to have something against blinking)

Alternatively you can launch sudo inside a terminal window. For example with xterm: xterm -e sudo [some command] [some arguments] […] This will pop up a terminal window to type your password in.

Pretty sure almost all terminal emulators have a similar argument.

I use a quartz64 from pine. Back when it came out it was beefier than the rpi4. With the 5 that has now changed but it still is a great little machine.

My instance runs on it aswell as my other webservices (A Homepage, cgit instance and a small blog). Handles everything really well with the 8GiB of RAM.

Setup is a bit of a pain, especially because I had the urge to run gentoo on it. Compile times are actually acceptable.

It costs 80 bucks, which is really acceptable.

Edit: Forgot to mention energy efficiancy, ARM is unbeaten by x86 in that department. People on here recommend old PCs a lot, which, depending on your local energy prices could quiet quickly void the savings made by buying it. Also it has a SATA port, which requires some tinkering with the Devicetree to get running but allowed me to use an old 1TB SSD i had in the house.

IIRC it comes with a firmware called InfiniTime preinstalled. So I guess that one.

Never worked with nim or godot, but it is able to call c routines? So I guess you would be able to call to gdnative?

Likely isn’t gonna be beatifull, but it should work.

Well we’ve had binary packages for ages for big builds like firerox and default is still to use source packages.

Still I’m really excited for this, having the whole, or big parts of the package tree, will speed up initial installations by a lot on weak arm systems for example. Now initial installation can be done quick and later you could still compile stuff yourself for the full gentoo experience.

Here is the source code of the status commans:

http://sprunge.us/4xaYvq

And here is the relevant cava config: http://sprunge.us/hiY6EA

Don’t say I didn’t warn ya about quality. Some path are hardcoded in, some are provided with defines. Generally just a big mess.

Comes with the works on my machine, might break yours warranty :D

Wayland is a Display Server Protocol, meaning it is a specification of how a program wanting to display something like a window communicates with another program, the display server, which handles drawing to the screen.

It matters because it vastly simplifies and modernizes display server infrastructure.

X is huge, with many parts from the 80s and 90s that were simply not needed today, creating a fully compliant X Server with all extensions was pretty much impossible, which is the reason pretty much only X.org existed as a full implementation.

Some benefits for users are no screen tearing, VRR and support for more complicated setups like having multiple monitors all with a different refresh rate, which was a pain in the ass on X but is no problem on wayland.

X is going to die, especially with the fact that frredesktop and the two big DEs, GNOME and KDE are working on it. Some distros come with wayland by default already.

If I develop anything with a GUI I use GTK4. It has a bit of a learning curve to it but honestly I’ve come to like it.

I am currently creating a program for simulating networks and the drawing area is great for drawing the actual simulation because it basically allows you to have a cairo area as a widget so your possibilities there are basically unlimited and cairo is just a great drawing API.

Also gtk is basically the only modern GUI toolkit that can be used with C, which is great because it is pretty much the only language I know well enough to program a big application with. (But GObject still feels like black magic to me)