“Systemd is great”, then systemdeeznuts and go use it. Don’t make it a huge piece of shit half-imitation of svchost.exe that forces incompatibilities, so we can fuck off and use our own shit if we want to.

We welcome you in BSD world

I use it because it has native compressio and also an entire incremental backup tool built in (btrfs send/receive can throw snapshots of a filesystem across networks)

Although my actual daily driver is FreeBSD with ZFS

I am running Wayland on an IVB GT1. Your hardware is not possibly shittier than this AND capable of handling modern tasks. Also wayland just needs the infrastructure of doing accelerated draws which if your GPU doesn’t support then it won’t work with X anyway unless you’re running truly exotic 2D accelerators from the 90s

That’s complete horseshit. There are lile 3 major implementations of Wayland and 2 exist because the other one wasn’t ready at the time. There are other hobby implementations, but they all work together. Just like how different network stacks can all talk TCP to each other and be fine. Nobody calls TCP fragmented because there are different network stacks…

There are also smaller projects.

Also, the model of a protocol allows Wayland to be deployed on truly exotic operating systems. As long as the top level is compliant, shit just works.

Kekw we’ll see

X11 has a shitload of unwanted and unused features that your favorite X11 compositor is actively fighting AGAINST to render your GUI.

I implore you to pick up the X.Org source code and your favorite X11 shitshow’s source code and realize why Wayland follows the same paradigms that apple adopted in 2001 and Microsoft in 2006.

Yes, the insane old ways are being phased out for a reason. Sorry that we don’t keep the world in a heavily romanticized version of 2003 forever.

Yes, them not saying anything why they support that hiterlite scum is quite concerning. I think the CEO is just mad he got caught trying to startup a Nazi bar

“You can’t call everything racism!”

looks inside

Blatant Racism

mfw europeans are hitlerite

I don’t think we should work with scum like DHH and vaxry just because some asshole lib might accuse us of purity tests

If “not working with people who are maniacs who want you dead” is a purity test I’m dusting off my Inquisition book

Every day I regret becoming a network engineer more and more

You have a clusterfuck of a clusterfuck because corpocunts make more money from keeping everyone on shit old stacks

The network engineer to communist/anarchist pipeline is real

Yeah and those are the ones currently identified (btw that issue isn’t completely fixed) because rust never was nor advertised itself as sound. Meaning, you gotta be careful when writing Rust code too. Not as much as C++, but it’s not a magical shield against memory problems like people have been shilling it as.

A) Rust doesn’t have a formal specification other than “whatever the fuck our team hallucinated in this compiler version”

B) Doesn’t matter the definition if it fucks your day because you’re not careful.

Sure sure Heil Rust but be mindful of the fuck you’re doing before you get bit ¯\_ (ツ) _/¯

Have you heard about cve-rs?

https://github.com/Speykious/cve-rs

Blazingly fast memory failures with no unsafe blocks in pure Rust.

Edit: also I wish whoever designed the syntax for rust to burn in hell for eternity

Edit 2: Before the Cult of Rust™ sends their assassins to take out my family, I am not hating on Rust (except the syntax) and I’m not a C absolutist, I am just telling you to be aware of the limitations of your tools

Always check your programs on -O0 or pay the price

Shit gets really fun when you find out your code is a edge case for compiler optimization and should never be optimized away (although this is very very rare for -O2)

No there is not. Borrow checking and RAII existed in C++ too and there is no formal axiomatic proof of their safety in a general sense. Only to a very clearly defined degree.

In fact, someone found memory bugs in Rust, again, because it is NOT soundly memory safe.

Dart is soundly Null-safe. Meaning it can never mathematically compile null unsafe code unless you explicitly say you’re OK with it. Kotlin is simply Null safe, meaning it can run into bullshit null conditions.

The same thing with Rust: don’t let it lull you into a sense of security that doesn’t exist.

Ignoring warnings is really not a good way to deal with it. If a compiler is bitching about something there is a reason to.

A lot of times the devs are too overworked or a little underloaded in the supply of fucks to give, so they ignore them.

In some really high quality codebases, they turn on “treat warnings as errors” to ensure better code.