Calling this AI slop would be generous. If we made a list of the things wrong with it we would be here all day. Nothing has an effect on redline RPM, you can create compression and turbo combos that would instantly grenade an engine, the preset “super car” has 200hp?
The only thing it illustrates is the authors lack of understanding.
I fed the technical data of my motorcycle into the model and it told me right away that this build would destroy a real engine because the piston speed would be too great.
The real thing has been running for 56,000 miles, so it can't be that bad. *g
"Supercar" has 670hp 500lb-ft @ 5297rpm which seems reasonable. After configuring the tool with my car's specs, it was fairly close on the dyno; though, I'm very far from an expert. Imho, pretty cool, nonetheless.
I know this is about the Japan and not the US, but software patent law has been incompatible with traditional IP protection in the US for a long time and it really doesn't make sense in the current age.
Software patent law and AI inventorship are separate legal issues. For example, an AI could invent a mechanical device which is a more "meat and potatoes" kind of IP. But the question of whether the AI, or the human invoking the AI, should be listed on the patent is distinct.
I wonder if you think other OSes are any different?
TempleOS is the only thing that comes to mind that doesn't fit your description and it's not practically useful.
Any sufficiently large codebase is a mix of ideas and concepts implemented by different people with different priorities over a large timespan and if you can fit the entire thing in your head it's not very interesting or complex.
Qubes OS, the Linux distribution aspiring to offer a reasonably secure operating system, pioneering a "every app runs in a virtual machine" approach in the Linux laptop/desktop space, tracks this at the following issue:
The *BSDs, Mac, and Windows all keep critical code in the same tree as the OS.
Something like disk encryption would be immediately visible.
So you don't have this mess of 80 different distros with 60 different versions of systemd, 20 that don't use it, a million kernel versions and it's all thrown together in a Costco-sized trash bag and we call the output "Linux".
In my experience any software system (not just operating system) after crossing a certain limit on complexity and age looks exactly as hodgepodge of code pieces thrown together, sometimes from different sources even if developed by one org. All major OSs have long crossed those limits, I believe.
Windows for ages did not really keep all the code in one repo. There were like a dozen parallel repos for e.g. the shell, kernel, IE, etc. Also every feature was developed on team-level branches; integrating all those branches often caused unexpected bugs.
Every time I bought an electric unicycle, it got stolen at South San Francisco branch. It is totally reproducible, happened 3 times. One time I found some higher up at FedEx on LinkedIn and sent them an InMail. The regional manager really pushed this issue to highest priority for the branch. Branch managers got CC'ed in, drivers, people working at the warehouse; it was an all hands on deck situation. They reassured me that they have cameras everywhere and it couldn't be stolen.
It was stolen. They don't know who did it. FedEx is terrible.
FWIW, I've had really good interactions with FedEx for the most part.
Including for Apple hardware, where I had a FedEx driver pull into the end of my long driveway, wait 5 seconds and then leave. They marked the signature-required MacBook Air as "undeliverable, nobody home", while I was in fact home and waiting for the delivery. Called the local FedEx hub and they sent the driver back to me.
Python's packaging system is worse, but Javascripts packages / standard libraries are far worse than Python.
In python managing packages is a pain and there are too many package manager options, but for the most part there are good libraries, and chances are you don't even need one because the standard libraries are so good and mature.
In Javascript NPM is really all you need (even if yarn is a bit nicer), but you're gonna need to install 50 packages just to get a basic boiler plate app going and the quality of said packages is not always great.
Ehh, not exactly, personally I wouldn't agree that the first half of that statement is correct.
I think it's important to stress that this article (press release, really) is about MariaDB plc being sold. That was the previously-publicly-traded commercial entity which develops MariaDB Enterprise and other paid solutions. But the MariaDB Community Server code base is maintained by the MariaDB Foundation, which is totally separate. (That said, MariaDB plc is the largest outside code contributor to MariaDB Community Server as well; but they're technically not the maintainers of it.)
It's also important to understand that MariaDB and MySQL have diverged in functionality over the years, and MySQL is still actively developed by Oracle, who have consistently put some serious engineering effort into it. Many folks on HN seem to think that MySQL died and MariaDB replaced it, as some sort of successor across a linear history; that's not accurate and in reality MySQL is extremely widely used.
I like the "gun to the head" heuristic but I would probably rephrase it to be something like "If you only had 24hrs to solve this or the world would come to an end".
The only thing it illustrates is the authors lack of understanding.