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
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.


Ah but you see, you have to understand the FOSS community a little more than just “using a license that FSF and OSI endorsed”.
In terms of inter-project politics, systemd is almost wholly owned by IBM. They can override any will they want, they can change anything they want, all while fucking the community over. In short, IBM, using systemd as a massive octopus growing it’s tentacles all over mainstream Linux distros, is gaining considerable weight to pull in the Linux world.
They can essentially dictate matters to everyone they want, because you don’t want your distro to stop being supported, do you? And now, another IBM-majority project, GNOME, is almost dependent on systemd (despite the very good word of both gnome and systemd that this wouldn’t happen, IT HAS) and KDE is also being slowly pulled in that direction, with DrKonqi becoming systemd only in it’s latest update.
Essentially, we are handing over 30 years of work in FOSS to IBM, literally the caricature of evil tech company, and now they control the mainstream and can dictate their will.
Allow me to remind you that this same IBM almost immediately after taking over RedHat, started closing down the source sharing of RHEL, which is it’s own whole thing so I digress.
Let my final word be this, R.M.S as much of a problematic piece of shit he is, correctly predicted we being fucked over by DRM and subscription services 20 years ago and was ridiculed for it.
Don’t you think it’s time to take a fucking hint? You don’t have to be an anarchist to see where this is going.


You do realize that it’s not a binary between systemd and SysV, right? There are modern replacements for SysV other than systemd, like dinit, OpenRC, s6 and they all strive to address the shortcomings of SysV


BASED,
Try dinit too. It’s probably the easiest to use alternative to systemd


Except, they are. Pottering is the front man who does the dirty work for IBM and Microsoft to take over Linux by forcing distros to adopt systemd.
Those of us old enough to remember the “vote” that resulted in Debian going to Systemd remember it was almost at gunpoint.
Death to systemd, long live FOSS culture


LMFAO in my turf if we need to constantly check some values we either have a hook or a wrapped Stream<T>
Weak diss


You could also not be an idiot and write a debug script that checks those values or atleast provides an interface
But I guess they don’t teach that kind of thing in the javascript and python school of dogshit programming
It’s not much use with a professional codebase as of now, and I say this as a big proponent of learning FOSS AI to stay ahead of the corpocunts
INDEPENDENT
FRONT
SUSPENSION


People love to hate on Mozilla without knowing shit. Some of it is literally 4Chan grade manipulation as well.
Like the whole ToS debacle. People just aren’t interested in truth just rage 24/7


I’ve done more off-roading in my IKCO sedan (Iranian car manufacturer)
Because as much as they’re ridiculed today by libcucks of OSS, FSF was a formidable force of software once. At some point in history literally the only way to avoid paying absolutely insane manufacturer license fees for things like compilers was using GNU tools.
If they put their ass into it, they can pull it off tbh