News for hackers. Stuff that matters.
Re:The Great CoffeeScript to Typescript Migration of 2017 by apatheticonion on Friday May 15, 2020 @08:52PM (#23199370)
Though I use it daily, my biggest criticism of TypeScript is that it's not opinionated enough. From inception it was designed as sugar on top of JavaScript but not a replacement, and therefor they decided not to make decisions outside of the ECMAScript specification.

The advantage to this is developer buy in, the downside is how annoying it is to work with at scale.

In a monorepo, running 10 compilers in watch mode because TS can only consume external source which is compiled to JS. You can't consume TypeScript source directly (which would be nice if you want to use github as a package repository).

But it's fine. I'm happy paying the cost to not use JavaScript directly, but I am disapointed because it could be so much more.

Re:The Great CoffeeScript to Typescript Migration of 2017 by edjrage on Friday May 15, 2020 @09:57PM (#23199780)
Have you seen Deno? Would it help with your issues?

https://news.ycombinator.com/item?id=23172483

Re:The Great CoffeeScript to Typescript Migration of 2017 by johannesgoslar on Friday May 15, 2020 @09:53PM (#23199758)
There are project references and build mode, so 1 compiler for a monorepo also works.