In my entire life I have never seen anything in programming anywhere near as unimaginably toxic as the Rust community.
They have a hammer and damnit if they aren’t going to prove its the best tool for brain surgery.
In my entire life I have never seen anything in programming anywhere near as unimaginably toxic as the Rust community.
They have a hammer and damnit if they aren’t going to prove its the best tool for brain surgery.
The drivers are infinitely better, and the stutter when creating a ton of windows (ie notification spam from kconnect) is basically gone.
Yeah I was thinking DNS over https was sneaking in, it’s a tricky little bastard and you have to kill Firefox to change that properly.
Check again, it is sneaky AF.
Good news! Elon says you can make the check out to: “X, not Twitter and not a complete business fucktastrophe”.
I think this is a reasonable assumption, but my experience suggests it will absolutely not be true for a lot of proprietary software.
That being said, that stuff will only be supported on rhel which will bend over backwards to keep it sort of working somehow.
Great, then we just leave everything alone and say 32-bit user land is broken past 2038, doubt too many people are dying to run 32-bit userland after that, but if they are I can guarantee they’ll be running old binaries probably without source.
Your argument is to have 2 subtly incompatible abis and one day binaries magically break.
You’re right it breaks c stdlib, but that’s literally the point, libc is broken by design, this is the fix.
No program with time32_t will ever work after 2038, so any compiled that way are broken from compilation.
You’re right that the length isn’t specified though, the issue is changing types for triplets silently has unfortunate side effects.
If you really want to be clever, mangle the symbols for the functions that handle time so they encode time64 as appropriate, but doing it silently is begging for trouble.
This seems overblown, we’ve faced these things before.
The straightforward path is adding new calls and structs and leaving the old code in place, then having tests that return -1 for time32_t and seeing what breaks.
It’s not pretty, but this is life in the new epoch, gentoo doesn’t have it harder than anyone else except when they’re trying to rebuild while the transition is happening.
I know nobody wants 2 apis, 1 deprecated, but this is an ancient design decision we have to live with, this is how we live with them.
Absolutely.
They partly were, they’re just not given nearly the same attention and are often terribly outdated and less engineered.
Also they aren’t tested as thoroughly, there was a call for hardware by the FreeBSD team not that long ago that I can’t find, they simply don’t have the same kind of resources.
Most FreeBSD dev is focused on server hardware like for Netflix and its ilk, I don’t know many other people who use it as a daily driver.
Easier said than done, and they can’t copy because gpl.
Cool, bsd works fine for laptops, but the power management is pretty shit.
Also the wifi support too.
Otherwise I love my freebsd thinkpad, works great when plugged in, but again the wifi is painfully slow.
Yeah.
My home server runs that many, but it’s a monster dual xeon.
The freebsd instances have a ton of jails, the Linux vms have a ton of lxc and docker containers.
It’s how you run many services without losing your mind.
I mean, the extension system means we could easily fix it, just deprecate the old paths, use the legacy xlib to set up extensions and write a lighter stack from there. A new input path too and you’re on your way.
It makes things a bit more complicated, but it’s also exactly how x86 managed to stay relevant all these decades, the old macro instructions are all slow microcode and you only use the safe stuff that’s hyper-optimized.
Meanwhile you get the one thing X has: It works.
Rust zealots are on an unstoppable jihad.
Expecting suicide fork bombers any day now.
Yeah sorry, c/c++ guy here.
I get that rust is the new shiny.
But now it means changing any potentially bound c function means I need to be fluent in a language I barely heard of before this year and has a syntax that makes c# look normal.
So, how about no?
Wtf man, I never even pushed that shit upstream!?
They know customers will pay, but mostly they can lock in long term contracts on favorable terms.
Hock is scarily good at his job, depending on how you define his job.