This works. I ran a linux distro in off hours on my work laptop for years this way.

Sure, at the surface level of tweeting back and forth, there is nothing vile. But the very act of using the platform funds an agent of chaos that is doing very real harm, and to ignore that because it is inconvenient is at the most charitable interpretation a selfish and callous act. There are other means of discourse, and those with input that is valuable will follow you.

Maybe, just maybe, if your followers aren’t willing to give up something vile because it’s giving them a dopamine hit, they’re not adding as much value to your life as you think.

Yeah… I question the efficacy of the methodology. A show that had nothing but perfect 10 episodes during its entire run wouldn’t make this list. But a real data-driven way to assess this escapes me… It’s the kind of question that would do better by survey, because elements a single number doesn’t capture, like how memorable the episode was and how it impacted the series as a whole which the episode ranking does not capture are absolutely relevant to what makes a good finale. I guess the fairest data-driven way to measure a good finale would be to capture the general ranking of the series as a whole before the finale, and then after it, and the biggest shift would indicate the finale with the strongest impact, but this is still not a perfect estimate for “best”.

My Nvidia card won’t properly resume the display after suspend with the default suspend script, but if I correct the script file, every time aptitude updates the nvidia drivers, it restores the bad version of the configuration file. If you set the file immutable with chattr, aptitude throws a fit and goes into a broken state when it can’t overwrite the file on a driver update.

So I keep a good copy of the script file in the directory, and in my pre-suspend script file I overwrite the main suspend script with the good version. Every single time.

Red Star OS!

More of that hard work on Tesla that the shareholders bought! 56 billion well spent.

Possibly. But it’s also pretty common in many instances of technology adoption that as more users come, the quality gets worse, and while open source doesn’t have to worry about a shareholder-driven profit motive driving it, it’s still easy to wind up with a muddled focus. I wouldn’t expect that Linux and all of the associated software projects that make the functional desktop are going to be an exception overall. If you’re an open source developer working on a project now, basically any user is some form of power user, and it’s easier to find consensus of what to prioritize on a project not only because Linux users tend to be better about understanding how their software works and are actually helpful in further development, they’re also likely to direct development towards features that make software more open, compatible, and useful.

Now fast forward to a future where Linux is the majority desktop OS, those power users are maybe 5% of the software’s user base, and every major project’s forum is inundated with thousands of users screaming about how hard the software is to use and, when bug reports and feature requests are actually coherent, they mostly boil down to demands for simpler, easier to understand UIs. I can easily imagine the noise alone could lead to an exodus of frustrated developers.

Some things are better for NOT trying to be the answer for everyone.