I don’t use tiktok, but some people have unusually based tiktok feeds. They can get direct footage from the genocide happening in Gaza, for example. I never get that recommended on YouTube, despite my very obvious socialist leanings, watching pro-Palestine content, etc.

This is the actual reason tiktok is being banned (if they don’t sell) after the election. One of the largest lobbying groups in America, AIPAC, in probably the most well-funded policy categories (pro-Israel policies) backs most of Congress. They’ve determined tiktok has far too much influence on American youth, and has made the Israel/Palestine divide a young/old divide more-so than a left/right divide.

There’s already a strong correlation between political leaning and age, which is problematic for the future of the fascist movement in America, but this issue falls outside the norm. You’ll find a lot of young conservatives calling for an end to the needless killing of civilians. They won’t call it a genocide because admitting Israel is a genocidal apartheid state is too far for them, but they can at least admit killing tens of thousands of children is not the right path here.

That kind of extremism (e.g not greenlighting any amount of culling of “human animals” Israel feels it needs to do) is unacceptable to the pro-Israel lobby, and they’re not used to getting this kind of pushback from the American public.

I’ve seen a couple of posts in here about sound. It’s wild that I’ve been through dozens of distros since the start of high school (12 years ago), installed them on at least 10 machines over that time, and can’t remember one issue with sound that took more than 15 seconds to fix (e.g discord choosing the wrong sound device because I have 6 things plugged in that can technically output sound, which also happens to my friends who use Windows).

Maybe I’m just lucky. The only issues I recall having in the last decade are essentially graphics related. Either game compatibility (though proton/wine is much better than it was in 2015) or desktop environments being finicky (freezing on sleep for example), but the latter afaict was entirely due to proprietary nvidia drivers. There are proper, high-performance open source drivers in the works, so nvidia might be on par with amd in 2-3 years on Linux (which is to say literally no issues for the vast majority of people, probably far more stable than Windows).

In the same time I’ve had lots of people come to me with problems that we’ve specifically troubleshooted and found Windows to be the issue even when it seemed like hardware problems. Like monitor flickering/black screening, and plugging in a different monitor the issue goes away. On the surface it seems like a hardware problem, but both monitors worked flawlessly on Linux for literally months. Full reinstalling Windows did not fix the issue. Upgrading from Windows 10 -> 11 did not fix the issue.

Same thing with another friend’s external SSD. For some reason it wasn’t being detected on his Windows 7 install. We installed Linux and the drive was picked up. Maybe Windows 10 would’ve also picked up the drive in this circumstance, but a lot of people hated the idea of Windows 10 at the time (this was just after Windows 10 was released, when Windows 7 still had a similar market share).

There’s likely a huge percentage of problems people attribute to hardware that are actually Windows being a shitty O.S, but nobody actually checks if Windows is the problem.

Yes, but not because the goal of having exceptions in types is bad, rather Java’s type system isn’t advanced enough to support the ideal solution here.

Scala 3 is working on experimental capture checking capabilities, which allows functions to express certain capabilities (file access, networking, db, etc.), and CanThrow capabilities (e.g exceptions at the type level) are one reification of this.

The CanThrow docs I linked have a good introduction into why Java checked exceptions are bad, and how Scala’s alternative is far better. Essentially it comes down to a lack of polymorphism in checked exceptions. In practice this means they’re incredibly verbose outside of simple usecases, and with a very easy escape hatch (RuntimeException), you don’t even get the guarantee of knowing a function without checked exceptions doesn’t throw.

Python will also have this latter issue. Python’s “typing” in general has this issue actually. Types aren’t validated unless you use an external tool, and even then Any is a leaky abstraction that can hide any level of typing errors, unlike in properly typed languages where it’s not leaky. You need it to be leaky in gradually typed environments, or you wouldn’t be able to use a ton of the Python ecosystem, but this vastly reduces the effectiveness of the typing solution.

I don’t know if Python’s solution here will address the lack of polymorphism that Java’s solution has, I’ll have to look into it more.