No South park hum? But Rick and Morty is there so it's not a policy against foul-mouthed cartoons; Smiling friends is also missing but perhaps it's too unknown or too recent to be there.

Pre-AI it’s tedious to find/fix/verify the subtitles — and there are a lot of episodes of South Park. Literally the reason why it’s not there :|

If you sort the top 50 best rated episodes of all time on IMDb you would already have 90% or the quotes people search for, so I would focus on your those if you ever try to take a stab at it.

Talking about AI, Google, and shady tactics, I wouldn't be surprised if soon we discover they are purposefully adding video glitches (deformed characters and so on) in the first handful of iterations when using Veo video generation just so people gets used to trying 3 or 4 times before they receive a good one.

Well the current models that cost per output sure love wasting those tokens on telling me how I am the greatest human being ever that only asks questions which get to the very heart of $SUBJECT.

You are right! Would you like me to pretend I'm able to generate better responses if you just give me more input but will end up just wasting your time and your money? And with some luck when you inevitably end up frustrated you will conclude that it was your fault for not giving me good enough input and not mine for being unable to generate good output, in other words that to you just need to get better at GPTing.

They laughed at my base64 encoded icons, now there, enjoy your downtime.

Snark detectors are all the way up tho

Except Gemini has lied to me about local events, it told me that in my city (specifically in my city, mentioning it by its name) a musical event was happening and I lost transportation time and cost, so it can be pretty spotty.

Oh they aren't conspiring against democratically made decisions about AI, instead they are "ammassing war chests to fight AI regulation", how submissively worded, but that's expected when they have a grip on all mayor communication channels.

He mentions curta in the fourth paragraph, and also having a simple design as one of the goals.

Microsoft should just bite the bullet and make a huge JS standard library and then send GitHub notifications to all the project maintainers who are using anything that could be replaced by something from there suggesting them to do such replacement. This would likely significantly reduce the number of supply chain attacks on the npm ecosystem.

JS also has a stability issue. The language evolved fast, the tools and the number of tools evolved fast and in different directions. The module system is a mess and trying to make it better caused more mess. There's Node.js, TypeScript and the browser. That's a lot to handle when trying to make something "std".

Meanwhile I have been using Ruby for 15 years and it has evolved in a stable way without breaking everything and without having to rewrite tons of libraries. It's not as powerful in terms of performance and I/O, it's not as far-reaching as JS is because it doesn't support the browser, it doesn't have a typescript equivalent, but it's mature and stable and its power is that it's human-friendly.

This is harder than it sounds. Look at the amount of effort it took to standardise temporal (new time library) and then for all the runtimes to implement it. It’s a lot of work.

And what’s more, people have proposed a standard library through tc39 without success - https://github.com/tc39/proposal-built-in-modules

Of course any large company could create a massive standard library on their own without going through the standards process but it might not be adopted by developers.

If you look at the list of compromised packages, very few of them could reasonably be included in a standard library. It's mostly project-specific stuff like `@asyncapi/specs` or `@zapier/zapier-sdk`. The most popular generic one I see is `get-them-args`, which is a CLI argument parser - which is something Node has in the form of `util.parseArgs` since v16.17.0.

Well they clearly lacked marketing? Pretty sure a red text in npm every time that package was installed that says "hey we have a better way to do this with node alone" would have made a dent in the library usage, but they didn't do anything of the sort.

That is literally how the CycloneDX SBOM packages work, well, after the fact and after the disclosure process.

There's an xckd for that :)

The one with 12 competing standards going to 13 competing standards, or something like that.

Pretty sure Microsoft is exponentially bigger than 99% of the library authors out there, and add to that the giant communication channel that GitHub gives it over developers, so the analogy breaks pretty fast.

Or it's worse, because there's a good bunch of devs that don't trust MS by default?

Even the most hardcore GNU supporters don't think Microsoft would add a supply chain attack to such initiative, or that their software security is worse than the average NPM (popular) package maintainer.

Just the lock in and telemetry are dangerous :)

And they're company policy as opposed to honest mistakes like security vulns.

the esp32 in the side of the head should give it away

The author does point out glass doors being an issue that he asks about.