Working with Web Technologies since ~20 years now and am seeking for a new challenge ever since. 😍
FinTech | Lead Developer @ Debtvision
Previously: FE Lead @ Mercedes-Benz.io
This is normally something that people tend to say that do not use it / have not made huge experiences with it.
TypeScript is, for very good reasons, the de-facto standard in JS Web Development. It's not like big companies just choose it because they are bored. Years ago, Slack has revamped the whole JS-based App to make it work with TypeScript.
The benefits are massive but I think there's enough resources on the internet so I'll be refraining just posting the links now :).
Long story short: What's described in the article can be summarized with two good samples:
(more related to what the author posted): I am creating a library that expects certain car manufacturer codes in the regex format: 'A{2,3}-[BC]+-[\d]+' . What's proposed in that article e.g. with the Concat utility type makes it possible for developers using your library to immediately see that AAAA-BCD-123 is invalid. With normal JS it would not show as an error.
I am building a library for Maths operations in which some situations expects Square Matrices. With recursive Types in TS you can ensure that. With JS you cannot. You only see potential failure when executing it (which is bad DX)
So far my 2 cents from the Perspective of a TS Instructor.
I mean people do use JS - literally - in TS. They just make it even more safe, especially, but that's just one benefit, when working in teams. Super-convenient once you get used to it. Nobody that went to understanding TS that I know ever went back to plain JS.
Believe me I've used it and also have a lot of experience with strictly typed languages - they are how I started out in programming almost 40 years ago. When I first came to JS it was liberating... so much easier to be creative, faster. Coming to TS felt like a backwards step. It really just rubs me the wrong way, slows development, and makes things that should be simple, just - irritating.
I appreciate a lot of people like it, but I also know a lot of people and companies who don't, and also people who've moved back to JS. Each to their own - whatever works for you.
Working with Web Technologies since ~20 years now and am seeking for a new challenge ever since. 😍
FinTech | Lead Developer @ Debtvision
Previously: FE Lead @ Mercedes-Benz.io
I think it depends. I do see how, for specific things, you'd choose plain JS.
In big companies were there is a lot of people movement (leavers, newjoiners, etc.) we always found it extremely helpful to have TypeScript.
Personally I love coming back to older side projects that have TypeScript in it as they are like a helping hand when you haven't touched the code in a year.
But yeah, whatever works for one, let's agree on that!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Another solution - make your life easier and use plain JS. All of this hassle - for what? It baffles me why people choose TypeScript
This is normally something that people tend to say that do not use it / have not made huge experiences with it.
TypeScript is, for very good reasons, the de-facto standard in JS Web Development. It's not like big companies just choose it because they are bored. Years ago, Slack has revamped the whole JS-based App to make it work with TypeScript.
The benefits are massive but I think there's enough resources on the internet so I'll be refraining just posting the links now :).
Long story short: What's described in the article can be summarized with two good samples:
(more related to what the author posted): I am creating a library that expects certain car manufacturer codes in the regex format: 'A{2,3}-[BC]+-[\d]+' . What's proposed in that article e.g. with the Concat utility type makes it possible for developers using your library to immediately see that
AAAA-BCD-123is invalid. With normal JS it would not show as an error.I am building a library for Maths operations in which some situations expects Square Matrices. With recursive Types in TS you can ensure that. With JS you cannot. You only see potential failure when executing it (which is bad DX)
So far my 2 cents from the Perspective of a TS Instructor.
I mean people do use JS - literally - in TS. They just make it even more safe, especially, but that's just one benefit, when working in teams. Super-convenient once you get used to it. Nobody that went to understanding TS that I know ever went back to plain JS.
Believe me I've used it and also have a lot of experience with strictly typed languages - they are how I started out in programming almost 40 years ago. When I first came to JS it was liberating... so much easier to be creative, faster. Coming to TS felt like a backwards step. It really just rubs me the wrong way, slows development, and makes things that should be simple, just - irritating.
I appreciate a lot of people like it, but I also know a lot of people and companies who don't, and also people who've moved back to JS. Each to their own - whatever works for you.
I think it depends. I do see how, for specific things, you'd choose plain JS.
In big companies were there is a lot of people movement (leavers, newjoiners, etc.) we always found it extremely helpful to have TypeScript.
Personally I love coming back to older side projects that have TypeScript in it as they are like a helping hand when you haven't touched the code in a year.
But yeah, whatever works for one, let's agree on that!