I always try to learn all I need to know to get a job done, then I try to learn the details when I need them.
Do you have a job that needs TypeScript? Learn it.
If you don't have a job that needs TypeScript, then dont learn it.
If nobody tells you if you need it or not, try to figure out the expected complexity of the project and if you comfortable with it, use JS, if you aren't comfortable with the expected complexity, then use TS.
That's the thing - I can't tell what does or doesn't need it, and all of my programming experience has been statically and strongly typed. So it sort of feels like every project needs it to me, but that's obviously not the case.
If you wanna easy going with coding, you will probably have more luck with TypeScript.
Programming with JavaScript is basically programming with untagged unions only, which feels like a nightmare for many devs.
Since you'll need to bundle up your JavaScript anyway, you can go with the TypeScript tooling, as it won't add much more overhead as the JavaScript tooling.
Easy going sounds good, but not at the expense of actually understanding my code. That does sound like a nightmare, but if that nightmare is the state of the art I'm just prejudiced.
Really appreciate your thoughts! Agreed about the tooling - seems like a six of one sorta deal
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.
I always try to learn all I need to know to get a job done, then I try to learn the details when I need them.
Do you have a job that needs TypeScript? Learn it.
If you don't have a job that needs TypeScript, then dont learn it.
If nobody tells you if you need it or not, try to figure out the expected complexity of the project and if you comfortable with it, use JS, if you aren't comfortable with the expected complexity, then use TS.
That's the thing - I can't tell what does or doesn't need it, and all of my programming experience has been statically and strongly typed. So it sort of feels like every project needs it to me, but that's obviously not the case.
If you wanna easy going with coding, you will probably have more luck with TypeScript.
Programming with JavaScript is basically programming with untagged unions only, which feels like a nightmare for many devs.
Since you'll need to bundle up your JavaScript anyway, you can go with the TypeScript tooling, as it won't add much more overhead as the JavaScript tooling.
Easy going sounds good, but not at the expense of actually understanding my code. That does sound like a nightmare, but if that nightmare is the state of the art I'm just prejudiced.
Really appreciate your thoughts! Agreed about the tooling - seems like a six of one sorta deal