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
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
Ohhhhhhhb lmfao you’re right
OnlyOffice sees little to no dev time and it is insanely behind LO in terms of development and features, please consider using LO for your own sake
Guys this comment is wrong I was thinking of OpenOffice
Well, not really, in this context
Cuntshit motherfucking whoresons
Pick up a fuckgun and join the resistance
I am not surprise that a feddit.nl is a blatant fascist orientalist
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
I think he is mistaking the method of power analysis to defeat cryptography with whatever the fuck he’s talking about
For the record, board power analysis cannot be done by your power provider
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.
Kekw we’ll see