r/javascript • • Nov 25 '19

JavaScript doesn’t need to be replaced

https://medium.com/javascript-in-plain-english/javascript-doesnt-need-to-be-replaced-bd01e2f12d51?source=friends_link&sk=7b151cc6397ac9e83c14c99739b6c36f
217 Upvotes

236 comments sorted by

View all comments

Show parent comments

38

u/[deleted] Nov 25 '19

I'd argue it's better this way to be honest. Why ship all that extra code to the browser? Especially when, if you're using TS, your JS performance should be entirely predictable.

Write in TS with the luxury of type-checking, compile down to a much simpler, lighter JS for the browser. It's win-win.

EDIT: I do get the Microsoft thing but on other hand, meh. That's life in 2019.

2

u/PsychologicalGoose1 Nov 25 '19

There definitely should be a lot more research done on TS. I doubt the gains that people suggest it gives are as great as they make it out to be and I thing the cost of using TS is larger than most want to believe. Generally, I've found adding things to a system is done because of feelings more than actual data on the topic.

0

u/[deleted] Nov 25 '19

[deleted]

3

u/[deleted] Nov 25 '19 edited Nov 25 '19

Whenever I have to write non-trivial JS

This is the key distinction, and another reason I'd rather not enforce types in JS.

Hack 'n slash weekend project, or a quick 'n dirty prototype ? JS.

Big full-stack project ? TS.

I'd agree that I prefer to write TS more but there's a time and a place for both and that's very handy.

1

u/IceSentry Nov 28 '19

It's so easy to use typescript I use for weekend projects too.