korrents

TypeScript

Do static types make software better? — the views on this, and who holds which

A typed superset of JavaScript that compiles to plain JavaScript.

FilterEveryone, all time19 from 8 people
  1. TL

    Tobias Lütke quoted

    Co-founder and CEO of Shopify

    SQLitedesign

    My bet? Sometime soon someone will (or has already?) create a embeddable, sqlite style mini execution environment that parses bash, typescript, or tool calls into a common IL execution plan that's easy to security check before executing. And design this specifically for durable execution environments.

    ↗@tobi on Xx.com

  2. 3 weeks earlier
  3. DM

    Dillon Mulroy quoted

    Principal engineer at Cloudflare as of 2026

    every time i’ve built something without effect over the past almost 3 years ive come to deeply regret it and wish i had just done it from the start

    ↗@dillon_mulroy on Xx.com

  4. 3 months earlier
  5. AR

    Alice Ryhl quoted

    Software engineer on Google's Android Rust team

    But okay, so to begin with, I think when it comes to TypeScript, Rust fits in as the backend language. That's where I would put it. I wouldn't use it in the front end. I think it's a pretty good fit for backends, API servers.

    ↗Why Rust is different, with Alice Ryhlyoutube.com 3rd of 23 in this recording

  6. AR

    Alice Ryhl quoted

    My opinion is that the least mature area is front end. There have been some attempts to compile Rust to Web Assembly and then run it on the web as a front end as a replacement for TypeScript. But if I was writing a web server, I would totally use Rust for the back end and TypeScript for the front end. I would not really go the web assembly route.

    ↗Why Rust is different, with Alice Ryhlyoutube.com 14th of 23 in this recording

  7. 7 days earlier
  8. AH

    Anders Hejlsberg quoted

    Danish software engineer and Microsoft technical fellow

    open sourceJavaScriptMicrosoft

    And we we full well knew that there was absolutely zero chance that we would appeal to the JavaScript ecosystem with a proprietary programming language licensed from Microsoft. No. No one was going to come. It had to be open source. There was just no two ways about it, right?

    ↗TypeScript, C# and Turbo Pascal with Anders Hejlsbergyoutube.com 13th of 26 in this recording

  9. AH

    Anders Hejlsberg quoted

    And the reason they came, I think, is absolutely because of the the better tooling. And I think we were totally right there that like adding a an erasable type system and then using that to enable great tooling is really where the pro where the programmer productivity boost is realized.

    ↗TypeScript, C# and Turbo Pascal with Anders Hejlsbergyoutube.com 15th of 26 in this recording

  10. AH

    Anders Hejlsberg quoted

    The thing that makes it interesting, I think, and and unlike pretty much any other programming language is the gradual typing. This This notion that you can have types, but you don't have to have types.

    ↗TypeScript, C# and Turbo Pascal with Anders Hejlsbergyoutube.com 17th of 26 in this recording

  11. AH

    Anders Hejlsberg quoted

    JavaScript

    So, if we're checking 99% instead of 100%, well, heck, that's better than the 0% that JavaScript checked, right? And it gives you like language features that no other languages can provide because they can't get to 100%.

    ↗TypeScript, C# and Turbo Pascal with Anders Hejlsbergyoutube.com 18th of 26 in this recording

  12. AH

    Anders Hejlsberg quoted

    JavaScriptPython

    that the language that's most suited for AI is the language that AI has seen the most of in its training set, right? And that's why you could argue AI does really well on JavaScript and TypeScript and Python because it's seen an awful lot of it

    ↗TypeScript, C# and Turbo Pascal with Anders Hejlsbergyoutube.com 19th of 26 in this recording

  13. AH

    Anders Hejlsberg quoted

    But but the thing is like doing programming languages, you come to realize it's a long play. I mean, if if you look back at the the stuff I worked on, it it it goes in 10-year cycles at least. And TypeScript didn't really, for example, or C# for that matter. I mean, it took it it takes 10 years to get to, you know, version one is great, but it has all sorts of issues, and then you got to do version two, and then it's not until version three that it really starts to be great.

    ↗TypeScript, C# and Turbo Pascal with Anders Hejlsbergyoutube.com 26th of 26 in this recording

  14. 3 weeks earlier
  15. JB

    Jamie Brandon quoted

    Programmer based in Vancouver who writes…

    The dynamic type system provides flexibility and easy meta-programming, while the static type system removes the overhead in most of your code.

    ↗Borrow-checking without type-checkingscattered-thoughts.net 1st of 2 in this piece

  16. 3 months earlier
  17. DM

    Dillon Mulroy quoted

    introducing better-result, my opinionated take on the rust result type for typescript after having written about 100 times npm i better-result *disclaimer*: if you can use effect-ts, you should use effect-ts

    ↗@dillon_mulroy on Xx.com

  18. 13 months earlier
  19. DM

    Dillon Mulroy quoted

    the most important typescript feature is discriminated unions and everyone should be using them more

    ↗@dillon_mulroy on Xx.com

  20. 13 months earlier
  21. DM

    Dillon Mulroy quoted

    JavaScript

    One thing that drives me crazy about the React ecosystem, and more specifically "tech influencers" and "thought leaders" in the space, is the infantilization of the developers using and working in it. I’m tired of reading takes like TypeScript generics, mapped types, etc should only be needed and used by library authors for most use cases. Or today’s discourse; Don’t use `useCallback’, ‘useMemo’, and React.memo. If you’re building anything beyond a simple CRUD app or a an incredibly focused app with few features, you _will_ need these features.

    ↗@dillon_mulroy on Xx.com

  22. 2 months earlier
  23. DH

    David Heinemeier Hansson quoted

    Creator of Ruby on Rails, CTO of 37signals

    JavaScript

    TypeScript just gets in the way of that for me. Not just because it requires an explicit compile step, but because it pollutes the code with type gymnastics that add ever so little joy to my development experience, and quite frequently considerable grief.

    ↗Turbo 8 is dropping TypeScriptworld.hey.com

  24. 4 years earlier
  25. TB

    Thorsten Ball quoted

    Co-founder of Amp and co-host of the Raising an Agent podcast

    Languages shape the way we think*, each in their own peculiar way. That's true for programming languages as well.

    ↗Learn more programming languages, even if you won't use themthorstenball.com 1st of 3 in this piece

  26. TB

    Thorsten Ball quoted

    Each language contains a different mental model, a different perspective for thinking about computation and how to write programs.

    ↗Learn more programming languages, even if you won't use themthorstenball.com 2nd of 3 in this piece

  27. TB

    Thorsten Ball quoted

    Every programming language is a lens through which we can look at the problem we're trying to solve.

    ↗Learn more programming languages, even if you won't use themthorstenball.com 3rd of 3 in this piece

  28. 4 years earlier
  29. DL

    Dan Luu quoted

    Programmer who has worked on hardware verification at Centaur

    designsoftware quality

    So the intermediate result appears to not be that TypeScript is reliable, but that projects mis-identified as TypeScript are reliable.

    ↗Literature review on the benefits of static typesdanluu.com 2nd of 5 in this piece