riskable

Why would a Linux user fool around with Davinci Resolve--proprietary software that's not even anything special? They'd just use Kdenlive, OpenShot, Blender, Shotcut, or any number of other FOSS NLEs that are all fully capable and feature-rich.

Not only that but Kdenlive has it's own well-supported PPA and .AppImage. It'll run on basically anything without much fuss.

For Microsoft, the key threat is that the Steam Deck isn't even a Windows OS device by default, let alone having Microsoft's Xbox services and Game Pass on it. Valve has used the platform, very successfully, to evolve Steam from being simply a digital store that runs (usually) on Windows, into being a very capable gaming OS in its own right.

That, perhaps more than anything else happening in the industry in recent years, is a threat to Microsoft's plans for the Xbox platform and gaming more broadly – and if the success of the Steam Deck is a key component of that threat, then creating an Xbox device to compete directly in that space seems like the logical response.

And there's the real reason why Microsoft cares. The success of the Steam Deck is a threat to Windows because it runs Linux. Also, the more games that run on the Steam Deck means the more games run on Linux.

Microsoft normally solves problems like this by abusing their monopoly and crushing their competition. In this case though, Microsoft is the underdog since Steam is the one with a much larger gaming monopoly. They're going to have to spend billions and billions if they want to stand a chance against the Steam Deck.

The other enormous problem they face is that Windows is very, very far behind when it comes to technology compared to Linux. Devices made for Linux vastly outperform the best hardware that runs Windows. Even if that hardware was made to run Windows!

Windows is decades behind Linux from a technological development standpoint. For example, Windows is still running the same filesystem from over 30 years ago!

What this means is that for any given portable hardware Linux is going to vastly outperform Windows in basically every benchmark from battery life to frame rate. That doesn't even include the fact that in Windows you're forced to install many background apps (and kernel level ~~rootkit~~ anti-cheat) that takes up memory and slows everything down just to get basic security and play games.

In hindsight, it was a mistake to let the mule drink.

I appreciate that they called them anti-Israel protesters and not antisemites (or similar).

Oh don't think for a second he plans to actually go after the real cartels. He just wants an excuse to kill random Mexicans.

After his orders to kill people we'll have news reports from actual Mexicans saying the people he order killed weren't drug dealers. And they'll be right.

I don't know if Republicans will accept this. As much as they fear betraying Trump, taking away their power in Congress is exactly the type of move that could get Trump impeached (a third time).

Here's how that's going to go:

• He'll send in the military and they'll successfully kill some "drug dealers".
• Mexico will be (rightly) pissed AF.
• Mexico will retaliate by just ending all exports to the US of some essential goods (e.g. tomatoes, car parts).
• The price of those goods will skyrocket. Business will close. White people who voted for Trump will bitch that, "he's hurting the wrong people" again (leopards eating faces).
• Mexico will refuse to take "back" their immigrants because of Trump's bullshit.
• Trump will "suddenly" need to jail a lot more "illegals" that he's rounded up.
• They'll start making up stories about how all the millions of people in the concentration camps are nasty criminals and murderers... As an excuse for the poor treatment and blatant raping and murdering going on.
• Right wing media will tow the party line. Anyone defending the "criminals" (which will include families with children) is a traitor to the country.

History will repeat itself.

without type safety your code is no longer predictable or maintainable

This sounds like someone who's never worked on a large Python project with multiple developers. I've been doing this for almost two decades and we never encounter bugs because of mismatched types.

For reference, the most common bugs we encounter are related to exception handling. Either the code captured the exception and didn't do the right thing (whatever that is) in specific situations or it didn't capture the exception in the right place so it bubbles up waaaaay too high up the chain and we end up with super annoying troubleshooting where it's difficult to reproduce or difficult to track down.

Also, testing is completely orthogonal to types.

It'd be ineffective and in fact, decrease the likelihood of obtaining that default assumption of innocence that cuteness provides. It'd be like tying a pink ribbon to the tail of a tiger. The ribbon itself would be cute but the tiger would still be viewed as a dangerous predator.

Might help with getting out of manual labor though 🤔 🤣

fast changing

This happens because JS is such a shit language! There's no best way (or even good way) to solve any given problem. This results in everyone reinventing the wheel every goddamned day.

Someone like you and me thinks to themselves, "this is such crap!" And they're right! 🤣 So they come up with a new way of doing things that's just a little bit better and they post it publicly.

Then some huge amount of new JS developers (there's always a steady stream) and a few old ones think, "hey, this isn't a bad idea!" So they start using the new thing. Then it becomes the hot new thing and suddenly huge amounts of JS code is depending on it.

Then people start to realize that this new way doesn't quite work so well in certain situations so they add on to it by making new utilities/GUI libs. Others see the wisdom in this and adopt these new tools.

These new "solutions" build and grow in complexity until new JS devs working with the new paradigm think, "this is such crap!" And they're right!

😂

Yeah that's annoying but it's a short-term problem. Python just recently cleaned up some long-standing issues that broke backwards compatibility in packaging (for certain things). Most public modules that broke made trivial changes to fix the problems (once they learned about them) and life went on.

However, for some fucking reason a whole bunch of dependencies related to AI are dragging their feet and taking forever to fix their shit. Insisting that everyone "just use Python 3.10" and it drives me nuts too.

This problem started to become a real thing almost two years ago (so they had plenty of warning and time to fix things) and yet here we are with still a handful of core dependencies that won't install for things like Stable Diffusion, Flux, and various LLM stuff because they're dragging their feet.

I blame corporate culture: Enterprises hate upgrading their shit and they're as slow as glaciers sometimes. There's probably tooling at Nvidia, for example, that needs a ton of work for Torch to work with new versions of Python and since all their documentation already was written for running on Python 3.10 (and Ubuntu 22.04 LTS) they've created a lot of work for themselves.

Any day now they'll finally finish fixing all these little dependencies and then we'll have another two years of ease before the problem rises again with Python 3.14 and it's massive GIL-free improvements that require big changes in code to actually take advantage of them.

Why? The most annoying thing that I remember about it was popular modules that hadn't been ported yet. In essence, a temporary problem; growing pains.

The Unicode/string/bytes changes were welcome (to me). But that might just be because I had actually encountered situations where I had to deal with seemingly endless complexity and ambiguity related to Unicode stuff and encodings. Python 3 made everything much more logical 🤷