Even KISS. Sometimes things just have to be complex. Of course you should aim for simplicity where possible, but I've seen people fight against better and more capable options just because they weren't as simple and thus violated the KISS "rule".

Almost every good content creator is only on YouTube.

Don't be an idiot.

I think this is a really good point, but it's also kind of a missed opportunity for NoSQL. The ORM mapping is easily the most annoying thing about using a relational database, and I think it's what most people initially looking at NoSQL wanted to solve.

But what we ended up with is Mongo which solves that problem but also throws away pretty much every useful feature that relational databases have! No schemas, no type checking, no foreign keys, etc. etc. It's just a big soup of JSON which is awful to work with.

I wonder if anyone made any NoSQL databases that avoid the object/table impedance mismatch but also managed to keep schemas, foreign keys, etc.

I don't see why. You can be interested in Linux and like some aspects of it but still get annoyed at the blinkered zealots claiming that there's no reason to use Windows.

Pornhub's audience is 75% male, and Linux users are almost all male too (and ... no offence guys but probably more likely to rely on porn), so I wouldn't take that as a representative global figure.

Statcounter gives 1.4% which is much more likely to be unbiased (and sounds way more plausible based on my experience of real life).

Buying several OEM keys is still going to be cheaper than a retail one though.

Wait so what would you have to do if you were covered by the CRA? The article mentions limited reporting & policy requirements for "open source stewards". I'm curious what the requirements are for full on commercial entities though.

The only good free option for that is SolveSpace. Don't bother with FreeCAD. It still isn't usable. SolveSpace is remarkably good for an open source CAD program.

It does have some notable missing features though, e.g. no bevels, fillets, drafts, etc. and last time I used it it had accuracy issues with small holes. But for your use case it's probably fine.

Microsoft doesn't have a vetting process for publishing extensions in the store. Maybe the failure is that people assume they do?

Haven't tried Mojo yet but I have tried Julia and it kinda sucked balls. Sorry Julia fans, but it did. My main complaints:

• It's a research language like MATLAB, so the emphasis is on repl's, trying things out etc. But the compilation model is like C++. When you import a package it spends like 2 minutes compiling it. I think it's supposed to cache it but the second time it was still like 10 seconds for me just to import a package. I believe they've improved this since I used it but still, huge red flag.
• 1-based indexing. Come on guys. Anyone using this is smart enough to learn 0-based indexing. It's like putting a steering wheel in a jet fighter because you worry about pilots getting confused by a joystick. Again, red flag.
• The plotting libraries (a core feature for this sort of language) kind of sucks. In fairness nothing comes close to MATLAB on this front. I ended up paying for MATLAB because of that.

There's also this article which has more reasons.

I am leaving it a while longer before I try Mojo.

Thanks, I'll watch some.