How many people didn't get media attention, don't have the ability (time/money) to sue, lost that case, and those where the intimidation and "punishment" was successful?

At some level the people doing this intimidation believe it'll be successful. Is that from experience?

I think the idea of "all growth is good no matter the cost" has been taken to an extreme.

And "growth at all costs" makes sense if there's lock in and you can monetize those "now locked-in users" later - but that doesn't really seem true on the consumer side. It seems pretty trivial to switch out which model and provider on the consumer side.

Any "lock in" has then to be on the model or inference side, and that's still advancing in multiple areas from so many different sources I'm not sure I'm comfortable saying that will also be a "winner takes all" situation either.

My approach is generally "enjoy using it while it's cheap and subsidized, but understand that might not last forever". If it does remain cheap after the subsidies end, great, you can just keep using it. But if it doesn't and you've lost the ability to work without you'll be in for a world of hurt.

Claiming that there's some small subset of their services (like inference per token) that's "profitable" doesn't mean anything when it relies on everything else that company is still paying for. If you could make money from it at current prices - why aren't they?

Otherwise it's just "how much they're willing to subsidize".

But it's arguably less accurate to the original recording.

DPMI was pretty much an "Operating System API/ABI".

While many people would likely justify their piracy with the idea that "The people who made it don't receive that money" - that isn't always true, and even then they did get the cash from selling the rights.

It's not as it playing that one specific game is a human right, after all.

The guy who posted the photo of brown skinned people with the "imagine the smell" comment was American and lost his job. The UK wasn't involved in any way. [0]

The comedian you might be thinking of is Graham Linehan - he was arrested for inciting violence against trans people and has a long string of twitter posts quoted as possible reasons. (and had a similar post with the comment of "a photo you can smell" but with a photo of a trans rights protest, so perhaps the origin of the confusion?).

[0] https://timesofindia.indiatimes.com/world/us/indians-dogpile...

Wake ups are death for mobile form factors, even if not really doing much work.

When the limit of effect a flamewar would have is if Star Trek or Star Wars got the top billing, or Vim was recommended to new programmers instead of Emacs, it was a fun novelty.

But now there's real money and power resulting from this shit stirring of course people will use it as a means to an ends. They've optimised professional shit-stirring because it's so valuable now.

And even then there's normally a "Sufficiently Different Sector" requirement for those personal projects - which makes sense, but it is inevitably worded vague enough that it would likely require going to court for pretty much any project to show it's not directly related. And that would be near prohibitively expensive for me as an individual if the relationship actually became adversarial.

And I couldn't find any tool that supported the mks "project" files that linked multiple rcs revisions into a single "commit", so something a little custom was needed anyway. At least for the ancient mks version used.

Quite a bit of effort was put into it during the "official" migration, but they eventually gave up too as even the oldest backup archives they could find had the same issues.

That meant the files has the entire "$Revision: 1.3 $" nonsense and "file changelog" at the top too - though many newer files never bothered to include the tags to actually get RCS to replace them. Inconsistent as hell.

And while the "family" of devices the software was for traces it's origin to the mid '90s, functionally none of the code was older than ~5 years at that time.

Naturally even with only a few tens of engineers it regularly messed up, commits stepped on each other's toes and the entire tree got corrupted regularly. For fun I wrote a script that read it all and imported the entire history into git - you only had to go back a few years before the entire thing was absolute nonsense.

I have no idea why that was still being used then, but I assume it had been in use from the very start of that entire hardware family. Perhaps as it was fundamentally a "hardware" company - which until surprisingly recently seemed to consider "source control" to be "shared folders on remote machines" - "software" source control wasn't considered a priority.

I wonder if this sort of trend will continue?

But USB 3.0 is pretty much the only "speed" that hasn't changed - it always required the extra connectors for 5Gbps from the start - but no more. What about those ports is now not "3.0"?