Hacker News Reader

Comment by madmaniak | Hacker News Reader

You're not missing anything and you will not receive any reasonable explanation for using TS. It's a step back 20y in programming. Easy to recognise when you were programming 20y ago also.

View on HN

A step back 20 years in programming is quite a statement to make. What is your backing for saying that? What is Typescript doing that other languages 20 years ago discovered was bad?

I was programming all these languages and 20y I do web technologies. Dynamic typed languages with a neat syntax was a huge step forward, developer became powerful with a single line of code. The biggest discovery was - you need all that tooling, because your language is overcomplicated. I also participate many conferences back and frontend each year (sometimes each month) watching this weird and artificially made transition backwards in concepts not only on frontend.

So yes ~20y ago was that point where developers discovered they are more powerful with dynamic typed languages and a boom for web applications started.

What about the lost productivity from debugging really simple errors that would have been caught by type checks?

You stop doing really simple errors if you allow yourself to train in this direction. Really simple errors are really easy to fix. After all boilerplate and effort you make in this kind of typed languages is not worth it. I'm not saying now about inventions like Crystal, where there is no effort + there is performance benefit. But TypeScipt adds complexity, boilerplate, and it still compiles to JS so no performance benefit.

https://news.ycombinator.com/item?id=18978404

None so far...

It seems like you're opposed to TypeScript and jumping to a quick dismissal. A lack of responses on an Ask HN thread is not evidence that answers to your question don't exist.

I'm just promoting the question, so I will have some answer.

Reply on news.ycombinator.com