why aren't all 13 resolved? a statement only gets an assessment when the public
record can support or contradict it. opinions and what-ifs never can, and 0 checkable
ones are still open, waiting for their date. predictions held up or didn't;
assertions are supported or contradicted. on every card:
▮▮▮▮▮ certainty ·
▮▮▮▮▮ debate potential. speakers are clickable
Insight
Singleton: TypeScript is the optimal language for AI-driven development
“TypeScript is an amazing language for AI because there's tons of training data. In the models and it's strongly typed. And actually at the company, we built most of the stack in TypeScript, and we have this amazing property, which is we have type safety all th…”
Opinion
Howard: Building web apps is much worse now than 15 years ago
“Much to my, you know, horror, the story around creating web applications is much worse now than it was 10 or 15 years ago, in terms of, like, if I say to a data scientist, here's how to create and deploy a web application, You know, either you have to learn Ja…”
Opinion
Pocock: Developers building AI chat apps and UX mostly use TypeScript
“Everyone who's building this stuff, everyone who's building chat applications is mostly doing it. If you're concerned about UX, you're concerned about shipping great stuff, you're mostly doing it in TypeScript. At least that's what I see.”
Prediction Not checkable as stated
Swyx: TypeScript could win the AI engineering ecosystem over Python
“I think it could be that TypeScript is going to win AI engineering, and that's something I haven't anticipated or seen, or I don't even know how to sort of Position around this, because I think it really does mean a lot of different things for what frameworks …”
Insight
Bubna: AI Agent Developers Prefer TypeScript Over Python
“And the interesting thing with, like, the agent stuff is people use their TypeScript SDK a lot more because they're not actually doing anything that needs ML.”
Assertion Supported
Swyx: TypeScript overtook Python in the annual GitHub developer survey
“I think this year is the year that TypeScript overtook Python in the GitHub survey, and I didn't really foresee that coming.”
Disclosure
Reggio: Brex chose full TypeScript over Kotlin/Elixir for agent codebase
“When we started building this new agent code base, like, as we were saying, like, we were answering the question, what would you do if you built a, you know, a Brex disruptor today? And it's like, it wouldn't be to pick Kotlin and Elixir as the backend. And so…”
Insight
Hezarkhani: Structured TypeScript architectures allow AI agents to operate autonomously for longer
“We feel pretty strongly in like high structure allows for agents to work autonomously for longer. And so our default stack is TypeScript front end TypeScript back end with a shared file where, or a shared folder where all of our shared types and schemas and th…”
Opinion
Mlejnsky remains bullish on JavaScript and web developers driving AI adoption
“I still remain very bullish web developers and JavaScript world, TypeScript world, even though we have, like, a ton of usage from Python but there's so many web developers, and it's easier and easier to use LLMs. I really think that you need to cater to these …”
Insight
Goyal: Python Dominates AI but TypeScript Dominates Product Building
“At the time, and still, like, AI is sort of at least nominally dominated by Python, but product building is dominated by TypeScript.”
Assertion Supported
Harrison Chase says TypeScript yields better LLM tool-calling performance than JSON
“I saw some paper that used TypeScript notation instead of JSON notation for tool calling and it got a lot better performance.”
Disclosure
Mann: Raycast extracts LLM tool definitions directly from TypeScript JSDoc
“Basically what we came up with, it's essentially you just write a TypeScript function and you document your TypeScript function with JSDoc. And then we extract all the information from there and basically make that and pass that information to the LLMs.”
Disclosure
Brady: Elicit generates TypeScript types from Python OpenAPI specs instead of GraphQL
“We don't use GraphQL. So we've got the types defined in Python. That's the source of truth. And we go from the open API spec and there's a tool that you can use to generate types dynamically, like TypeScript types from those opening API definitions.”