"When you go open-source, whoâ(TM)s responsible if something wipes an entire countryâ(TM)s data? Micheal McDoesntExist. Thatâ(TM)s who."

It's your in-house, in-country developers that fix it. You're not relying on a company based in a country run by an unstable regime that may or may not threaten your sovereignty.

Some of us have been there since the start (and looking at your uid, I'm guessing you have too). My name is in kernel commits from around the 98, and I was using Linux before then of course. I was even a Minix user on my ST at university.

Torvalds was anti source control. Others weren't and yep - started using Bitkeeper. Linus considered this "problem solved - you use what you like, I don't have to". Then he started using it. Then the reverse engineering debacle and then the "Well I'm not using any of the others, I'll write my own then" thing with git.

It certainly isn't down to him that people then started using it as the "if all you've got is a hammer" answer to everything - he's completely blameless in that. But I'm talking about the same kind of people that overused the Design Patterns book (one of the authors of which I've also met, although to my shame I can't remember which one - this was a corporate course and lecture being given at IBM Watson), the same kind of people that turned the very simple agile principles into the corporate behemoth Agile process-ridden abomination it became...those kind. They used git because of the hype, not because of the use case.

I'm going back from before he used Bitkeeper. There was a long period of time he didn't want to use source control at all. Bitkeeper wasn't used by him until the 2000s.

I mean, that's exactly what Linus did with git. A lot of his criticisms of existing stuff weren't justified (he went on misplaced rants about how version control software was bad in concept for years), and people have essentially cargo-culted git into areas it wasn't designed for because 'Linus is cool'.

Quick reminder that most commercial software doesn't actually have the problem that git was designed to solve - multiple masters. It was designed to be able to share kernel source trees between Linus' own, Red Hats and I think two others (Yggdrasil and SUSE? It's a long time back and I may be misremembering that). They all had their own quirks and patches, and they wanted to be able to handle commits to any of their trees and accept/reject as per their own preference.

This is pretty much the opposite of what most commercial software wants to do. It wants a single master, with known commits, so that a single known version gets shipped in the end. This is the exact opposite of what git was meant to be, yet it gets used there anyway. I notice the summary talks about a centralised system - yep, that's what you want for commercial, not a distributed multiple master.

Only of Netcraft confirms it.

I like this stuff but...

• Blade Runner (film not book) - 1982, 44 years old
• Godzilla - 1954, 72 years old
• Star Trek - 1967, 59 years old
• Star Wars - 1978, 48 years old

Even the Marvel stuff dates back to the 60s. I think pop culture is a bit stuck in a rut - there are good sci fi series out there, and new ones need to emerge as major cultural touchpoints as well. It's all feeling a bit retread at the moment.

in using legal proxies to erode constitutional rights

Well it is the day after the US midterm elections, so for some it will be the end of the world in a metaphorical sense.

There's something kind of ironic about an awards show (the Emmys) that is primarily for a particular medium (broadcast TV) leaveing their own medium to get more viewers.

Yes the Emmys recognize some programming on cable and streaming services, but it was originally for, and primarily for now, broadcast TV programming.

If it were open source and someone cared enough to fork it, then presumably there are open licensed contribution to the repo that Siemens won't own the copyright to.

What happens to those? Can they be taken closed source at all?

That "something" is "I'll do it because it gets me money. As long as I get paid, I'm good with it and let the courts decide later on if it's legal or not."

That would require him considering women as human beings rather than objects to fuck. He isn't capable of that.

Sometimes that choice is the right one. Not all parents are good parents. Some are downright toxic.

Just to note, the WSL containerisation approach is horrible for anything I/O intensive. WSL 1 had ELF binaries supported by the kernel and ran natively, this is a far superior approach to WSL 2's containerisation when it comes to raw speed.

I benchmarked this a few months ago and it was between 300%-600% slower on raw disk performance I/O.

Does this mean we should watch for price trackers online like we do for gas?