TypeScript

“The combination of ES5 (and successors), Typescript, and community consensus resulted in everybody using the good parts without even having to think about it”

“my conclusion at the end of my work with Node was that the next time I do anything significant with it, I would start with TypeScript first”

“typescript is "worse is better" in the right ways that it's a much better choice for both frontend/backend being the same and better type systems”

“TypeScript's type system is extremely expressive while still allowing you to retain the flexibility of a scripting language.”

“Typescript encourages bad code. It also gets in the way of good code, doesn't really prevent bugs in prod, and complicates the toolchain.”

“there's tons of tooling around it, and it's relatively unambiguous that it can solve and express Real World(tm) engineering problems”

“TypeScript 7.0 was literally a line by line translation. With essential features necessary for adoption still like a year off.”

“TS7 is going to cause problems for downstream users because Go is the wrong language to use for something that has to run in WASM.”

“It's all under the Apache License 2.0 and certainly big enough that if they started pulling anything untoward, it would see a fork.”

“We've had to paper over it with TypeScript and frameworks that impose constraints just to stop several classes of bugs, and even then it doesn't go terribly well.”

“I personally don't have a need for TS which introduces an extra build step, extra ritual when defining functions, and no performance benefit over vanilla JS.”

“Typescript, Kotlin, Python and Ruby (via Sorbet or DryStruct) are all really easy to write all those data structures and code.”

“In fact, I'd say (without actually measuring it) that _most_ bugs I've ran into in Typescript are due to someone having bypassed the typing”

“the lack of metaprogramming facilities, no access to the type annotations at runtime, and the lack of operator overloading”

“It might be best to pick languages where it's just harder to screw up, the canonical example being to prefer typescript over JavaScript.”

“severe degradation in output quality I have seen from an LLM working with plain JavaScript as opposed to TypeScript”

“TypeScript tried to accurately model (and expose to language services) the actual behavior of JS with regards to null/undefined”

“as it can leverage vast ecosystems of packages, has concurrency features, a solid type system, and decent performance”

“It actually has a very strong type system, while still being a dynamic language that doesn't have to be compiled”

“it's the programming language that successfully brought high-level type system concepts like type algebra, conditional types, etc. to their widest audiences, and it deserves a ton of credit for that”

“TS provides a significant drop in entropy while benefiting from what is a sweet spot between massive corpus size and low barrier”

“TypeScript is smart enough to handle that logic in the if block and know whether animal has been validated as Dog vs Cat”

“It would have been an affront to have a 6.0 that shipped without the means to work for so so many javascript frameworks/libraries.”

“whereas no recent LLM has never ever ever confused .js for .ts or suddenly started writing Node .v12 and angular into a Node 22 and vue project.”

“the never type in TS actually being a proper bottom type + having control-flow based types vastly superior to what rust offers”

“Most practical type systems are not technically complete, consistent, or reliable, and all have "escape hatches". That doesn't make them useless.”

“Having one set of tools to use across everything, being able to share logic and types without needing to go through lossy translation layers”

“I personally used namespaces and I could have only the TypeScript compiler running and producing a single JS file for rapid development”

“a highly pragmatic and well designed general purpose programming language with an unique and very powerful type system”

“Typescript is a bandaid to make sensible type system on top of Javascript, and it still leaves option open to use Javascript lack of rules.”

“Something I can't stand with Typescript for example is when the local development server has as strict rules as the production builds.”

“TS does have some minor things like enums that need to be transformed and are actual code, but those are very few, and leftovers from early days of TS”

“Embracing a functional style in TypeScript is probably the most productive I've felt in any mainstream programming language.”

“it has many advantages having a type system which lets you change whatever you want without fighting against the compiler/transpiler”

“Just because TypeScript allows developers to gently onboard static type checking by disabling or watering down checks, that does not mean TypeScipt is the reason you spend time validating your own bugs.”

“Typescript's type system is very powerful, but without strict compile-time enforcement you still spend a lot of effort”

“It's hugely beneficial to library users to automatically get correctly type return values from functions without having to do error-prone casts.”

“Both Rust and TypeScript have rich type systems that can express many kinds of runtime behavior with just types.”

“the ergonomics are better to me, and the packaging and ecosystem tooling are leaps and bounds above anything else”

“TS being compile time only really limits the language. It was necessary early on to drive adoption, but now days it just sucks.”