It drives me crazy. Just release it 18+months ago and iterate with versions, at least your users will have the feature in their hands.
It drives me crazy. Just release it 18+months ago and iterate with versions, at least your users will have the feature in their hands.
I have been an Arch user for years now and anytime I touch a debian based distro it is such a headache: weird patched packages that don’t compile anything past or present, insta dependency hell with PPAs, package names of 200 characters because apt doesn’t have a good way to represent metadata… It made me a strong believer that trying to fight the bit rot and stick to the old stuff is counterproductive: a consistent head based development with a good community fixing bugs super quickly results in less hours of work fighting the paleolithic era dependencies, safer (as security fixes are faster to get in, packages are foreign to hackers and constantly changing etc), easier to find documentation as you don’t need to dig into history to find which option existed or not, recent stuff is also easier to support for the developers of the various packages as it is fresh in their minds. Another point is to look at it from a tech debt lens: either you fix your stuff to work with current deps now or you just accumulate tech debt for the next engineer to fix in a way larger and combining a mountain of breakages in the future that of course IT and SREs will never want to do until the 15y old software is a disaster of security issues…
The presenter banging on the keyboard, seemed totally distracted for minutes to say 2 sentences. It doesn’t need to be perfect but that level requires way too much good will to not just close the video… There is nothing wrong to say, ok let me regroup for a couple minutes then fully jump in for your audience.
Your overall process is perfect: first try to solve it from the UI, then the console, then the magic sysreq key.
The fact that your kernel was not responding to the sysreq key could mean a couple things: is it enabled on your install? (cat /proc/sys/kernel/sysrq to check)
Before trying to understand why the kernel locked up, are you sure everything is solid on the hardware side? ie. Did you overclock anything? If yes did you burn test the PC on some GPU demo?
And égalité…
“one man’s trash is another man’s treasure” almost to the letter.
+1
So so so so many ads in that page that I genuinely lost the article in the middle, that’s a first.
The crashes are in the middle of browsers (both Firefox and chrome embedded in Spotify), if you try a simple mprime stress test (from the AUR mprime-bin) does it crash too?
One crash was in libxul and the other in libcef I doubt this is a specific lib
Literally every product. People feel so much safer after that :)
Late stage enshitification
Copies are just very strong statistical correlations.