In a lot of modern work flows this is incompatible with the development pattern.
For example, at my job we have to roll a test release through CI that we then have to deploy to a test kubernetes cluster. You can't even do that if the build is failing because of linting issues.
Man these are all things I'd love to see, don't feed me this kind of hopium BEFORE Barcelona.
Just give him a big raise & furlough him for 50% of the time, with the tacit understanding that he will hire some freelance help and work on a new regs car on his own dime and time.
Why not? It costs nothing, appart from transforming the old format into something the current site can work with, or more likely, have the old site support tbe old format.
And does this still work with modern cpufreq schedulers like amd-pstate and the Intel equivalent? IIRC I couldn't simply set frequencies or select the userspace scheduler on 10th gen Intel and frequencies don't seem to be honoured by AMD pstate drivers on Zen4.
This used to be me but mostly because I would experiment a little too much, never without reason.
Except a few Arch updates over a decade ago when they changed the default from hal to udev, or a Gentoo setup with WAY too specific USE flags, I don't think I can remember any failure like this ever. I've honestly had more issues with Windows nuking itself on a major update.
Mostly using Debian and Fedora these days, and it's been smooth sailing for quite some time.
Regardless of the relative size of the donation, it's enough to hire a full time person.
That's a whole different thing to me. That's not async, that's channels and multithreading.
I do that in Rust as well with mcsp channels and it's been fine.
It's the async/await bit that I find incredibly akward all the time.
I’ve heard gaming on debian isnt as ‘out of the box’ as it is with Ubuntu.
Depends on what your hardware is. Debian typically runs some older versions of pretty much everything. If you have newish hardware, you might need to run a newer kernel than Debian ships by default for full support. When that happens to me, I usually run the Liquorix kernel packages, which has been around for more than a decade and has never caused me problems on Debian.
For some graphics drivers, you might need a newer Mesa, which is typically available from Debians' own backports.
Don't do either unless you know you need to, because both lead to a somewhat higher risk for an unstable system.
You can just install Steam using Flatpak, and it works just fine.
Crash his car into the wall and break his wrist :(
The title is extremely misleading. They're comparing a Rust program using SIMD intrinsics to a Rust program which doesn't, without even using auto vectorization to let the driver look for SIMD opportunities.
This is a good example of why SIMD is useful and how fast it can be, but it is not an example of how Rust is faster than C or how humans are smarter than compilers. It doesn't even have a C reference source to compare to at all.
Based on the neofetch it's a Samsung Fold Z 4