[bhussai20]

I feel like this question is poorly formed in the age of resume-driven development. I prefer types of problems to tackle. But, I don't have preferred stacks so much as stacks I dislike less that are prescribed for my consistent employment.

My least disliked stack is the one that doesn't make me obscure, keeps my future career progression options sub-/Pareto- optimally open, while still making my pay competitive. So in essence I align with whatever is the easiest to adopt and train others on with minimal supervision.

i.e. JS, React, Express, Docker, AWS

[loh]

Sounds like we're on the same page.

I think TypeScript will actually overtake JavaScript eventually. It's just so nice to work with. JavaScript will of course always be supported and a prerequisite, but in terms of professional web and Node.js development on a broader scale, it's hard to imagine going back to writing plain JavaScript when TypeScript provides so much value for relatively little effort.

Also, I've updated the original title in light of your comment.

[pcthrowaway]

I don't know why this was downvoted, but I agree fully regarding Typescript, and was going to post the same thing. I've read good arguments against it by some people, and I agree, it does slow things down a lot.

But if you're not able to write things bug-free on the first try already, Typescript can bring a lot of value as well.