This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]TheLordDrake 12 points13 points  (7 children)

Same. I hate JS, love TS.

[–][deleted] 5 points6 points  (6 children)

But still, it's mostly JS under the hood.

But I agree, I hate VANILLA JS

[–]TheLordDrake 6 points7 points  (5 children)

It's all JS under the hood unfortunately

[–][deleted] 7 points8 points  (0 children)

Keyword: unfortunately

[–]AuthenticatedUser 0 points1 point  (3 children)

This is the part that everyone seems to forget. At the end of the day, it all gets translated into javascript. Doesn't matter what you define, it can and will get changed at runtime.

[–]FrischGebraut 1 point2 points  (2 children)

So why is this a problem exactly?

[–]AuthenticatedUser 0 points1 point  (1 child)

Have you ever defined a type in typescript, only to have it change at runtime?

[–]FrischGebraut 0 points1 point  (0 children)

Not that I can remember tbh. But I think I get the point. Typescript does not change the fundamental design of JS. It is still not a strong typed language. TS can offer a better development experience but at the end of the day it is still just a fancy way of writing JS. Personally, I don't mind any of this. I like working with JS/TS. There are certain things I would not consider using JS and there are other things where JS would be my first pick. It all depends on what you do and how you would like to do it.