4 ms·
The tooling for Typescript still isn't good enough to claim that accolade. There are still combinations of libraries, linters, editors, and frameworks, that thr
by tmpz22 7y ago
The tooling for Typescript still isn't good enough to claim that accolade. There are still combinations of libraries, linters, editors, and frameworks, that throw opaque errors that will roadblock students and junior developers significantly. Ultimately until browsers can accept Typescript directly without a compilation step it will remain a second-class citizen. Until then, all of Webpack, gulp, parcelJS, problems and inefficiencies are Typescript's problems and inefficiencies.
It's not fair - Microsoft and co. have done a tremendous job with the implementation and documentation of Typescript. But the reality exists nonetheless.
- jdxcode 7y agoYou're right the tooling could be better and that TS trips up beginners. Promises trip up beginners as well though but that doesn't mean they're not standard. TS is very, very close to being standard practice. It's already being used by over 50% of JS developers [0]. It doesn't have to be beginner/tooling friendly to be widespread. [0]: https://2019.stateofjs.com/javascript-flavors/typescript/ https://2019.stateofjs.com/javascript-flavors/typescript/
- waheoo 7y agoThis isnt a democracy. 50% isnt the bar for a standard. Thats like saying only 50% browsers can render html so its standard.
- jdxcode 7y agoI never said it was standard. I said it's very, very close. 50% (actually 58.5% of just those that would use it again) is certainly within the realm of critical mass.
- DanRosenwasser 7y agoAny specific examples where you feel the surrounding tooling is falling short?
- weq 7y agodealing with different JS environments, getting imports right, importing Vanilla js. ie. if i am building an electron app, we have atleast 4 different JS environments (UI thread, background thread, web worker, nodejs worker, nodejs-fork, test-runner environment) that all have different levels of compatibility with different JS standards. importing and exporting libraries in mixed mode is the worst thing about JS, bar none. The amount of obscur errors one needs to deal to get a debug-source-code-stepable pipeline up and running astounding.
- tmpz22 7y agoTypescript (the compiler), documentation, etc. as a language is pretty darn good. It could have more production ready examples, tutorials, and paths (I'd recommend a look at Microsoft's ASP.net Core tutorials which cover production-level material). But as I said the problem is Typescript inherits the whole mess of bundlers like Webpack and Gulp because they are REQUIRED to make any of it work in production. Ideally Typescript would own the entire bundler step - the closest example would be .NET owning the LINQ and Identity tools/libraries to make the .NET experience so much better.