Announcing TypeScript 2.7
TypeScript is a great improvement over JS, still held back by the horrible state of the JS module system in browsers. You write your code and it does what you want, then you spend a month figuring out amd vs esnext vs systemjs and Babel vs browserify vs requireJS vs webpack vs god knows what else.<p>And then when you find the solution that works.. two weeks later it is deprecated, the docs are gone, there is no clear migration path, and there are only conflicting blog posts full of misinformation by people that only know what worked for them and don’t actually understand what it is that their steps actually do or how they work.<p>(Yes, as you can tell I did not start off life as a JS web developer. TypeScript made the development part palatable to me, but the deployment remains a nightmare as far as I can tell.)<p>I wonder if the TS team has explored using webasm to at least get around the compilation&#x2F;translation issues.<p>Edit: I actually know the difference between the technologies I mashed into a single list (they’re not arcane concepts in low level development, it would be akin to confusing make with clang++ with gdb with Linux with ARM). I didn’t bother spelling it out because it’s not the point (I don’t have a specific question) and because to too many people that is what it seems like.<p>Edit 2: Please see my reply to @coltonv below: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=16278062" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=16278062</a>