> I'm kind of reminded of when Microsoft claimed it took a team of Ph.D.s to write a terminal application that updated at 60fps, and then Casey Muratori did it over a weekend.

This is the same Microsoft that is now rewriting the TypeScript type checker, parser and its developer tools in Go after realizing that the bottleneck was...the performance of TypeScript itself, which is a basic compiled vs interpreted difference.

> And this was before AI was writing code in earnest; when LLM-induced brainrot really sets in, civilization is in for a world of fresh hurt: lots more generated code, almost all of it garbage.

Some folks using LLMs wouldn't realize why it makes zero sense to use TS / JS for building performant and optimal applications. This is why people were experiencing significant rendering bugs in terminal apps (they are not designed for that) and slow starts with Claude Code, which was completely vibe coded with Ink.

If you don't understand the basic fundamentals of what you are working on with LLMs and bugs are creeping up left and right, then you are just sinking in your own comprehension debt.