Re:Ask HN: If you started making a web app today which tool ...
by ramon on Monday May 30, 2016 @09:05AM
(#11801104)
Ok, but if it's react it's a web or mobile web project. Then you'll still need to render DOM in the browser and it doesn't matter if you have more or less processing in the backend, you'll always need to care about your frontend.
If you think TypeScript has a lot more benefits then fine, you may go forward with it. I'm just conservative in this perspective. I understand you may transpile (build process), that's fine, I don't like working in Visual Studio, I prefer Atom and having my code without transpiling, not sure how it will work out with your build process when creating a zip to upload to Lambda, but best of luck.
Re:Ask HN: If you started making a web app today which tool ...
by smt88 on Monday May 30, 2016 @09:31AM
(#11801218)
I disagree that performance always matters. I don't pre-optimize. If I can create better UX by focusing on performance, I will. Currently my front ends are so light that a human can't tell the difference.
I don't use Visual Studio either. VS Code is based on Atom, and it has great TypeScript support. I use WebStorm, which is a better IDE overall right now.
I understand people not wanting to transpile, and it does suck that JS forces so many of us to do it.
As for TypeScript, I'm not sure I understand what you mean. How is it locking me in any more than React or something?
If TypeScript dies as a project, I would still be able to transpile my latest code and then continue writing pure JS...
Also, whatever risk there is of that happening, the productivity boost of TypeScript far outweighs it for me.