You say "just" 15 years, but Waymo is still only available in a few cities. That seems more like a slow, cautious rollout to me, not a fast takeoff. Society has had a lot of time to get used to (and tired of) the idea and come up with regulations.
My guess is that the deployment of other types of robots will often be a similarly slow grind.
That's unlike the Internet, smart phones, and coding agents, which got user adoption at a much quicker pace.
Edit: actually, that's a Node.js-specific API. For browsers, it seems like they should have a platform-independent JavaScript/TypeScript API that includes a WebAssembly file (if needed) instead of expecting you to compile WebAssembly yourself.
The "and physical" is the part I'm particularly skeptical of. Sure, drones are scary, but nobody's really solved getting a robot to deliver a package to your front porch in a civilian setting, and it seems unlikely to be solved quickly.
You don’t need a Mac Mini just for that, but they’re fairly inexpensive (or were anyway) and quality is very good. The people who buy them may never use all the performance available, but they’re more interested in convenience than getting the cheapest thing possible.
You can sort of justify it by assuming it will last a long time and they’ll use it for other things, too.
The TypeScript compiler is (was) slow, but you don’t need it to minify code. This sounds like some other problem with the tools in your project’s build. (There are faster tools available these days.)
A faster type checker will help with performance problems in text editors since type info is needed for a lot of queries.
Deno resolves import statements in its own way. For example, you can import URLs and JSR packages directly, but the file is usually loaded from Deno’s global module cache. To resolve imports you need to look at the deno.json file and deno.lock file. They also added Deno Workspaces (monorepos) which adds more complexity.
This means you need to plug an import resolver to the TypeScript compiler. Deno uses the TypeScript compiler API, but all the import resolution code is in Rust. I’ve done a partial reimplementation in TypeScript using a coding agent, but there’s quite a lot to it.
I don’t think Deno will be able to upgrade until the TypeScript compiler API is ready.
I’m wondering about privacy tradeoffs. Looks like they’re similar to Discord where the chats won’t show up in web searches and you can’t read anything without joining. But if anyone can join, it’s not like Signal either and end-to-end encryption wouldn’t make sense.
There's a Cambrian explosion of promising-sounding AI tools, all of which seem to work reasonably well for their authors, but it's unclear which ones to try. It seems like what we're missing are in-depth product reviews?
Accordion videos I like: https://mastodon.social/@skybrian/tagged/accordionsongs
Social media: https://bsky.app/profile/skybrian.bsky.social https://tildes.net/
Blog (inactive): https://skybrian.substack.com/