Re:Why TypeScript Isn't the Answer
by azakai on Sunday March 30, 2014 @12:44PM
(#7496742)
The author has articles on why TypeScript, CoffeeScript and Dart are "not the answer" (and the first article in the 4-part series is what is wrong with JavaScript itself). Regardless of the merit of the arguments in each, this feels very incomplete without a 5th installment about what is the answer in his or her mind. It's easy to point out flaws, harder to be constructive.
[ Parent
| on HN ]
Re:Why TypeScript Isn't the Answer
by blatherard on Sunday March 30, 2014 @12:58PM
(#7496834)
Sounds like that's his plan, judging by the end of the coffeescript article (which was published just 2 days ago)
"Realistically, the issues I have raised with CoffeeScript don’t come up every day. Ultimately though, they are enough to say we need something better. I hope to share some thoughts soon on what such a solution might look like. However, based on feedback in the comments, we’ll need to discuss JavaScript linters first."
To be fair, they do conclude the final installment with:
"...we need something better. I hope to share some thoughts soon on what such a solution might look like. However, based on feedback in the comments, we’ll need to discuss JavaScript linters first."
Re:Why TypeScript Isn't the Answer
by WalkerCodeRangr on Sunday March 30, 2014 @01:13PM
(#7496898)
I'm getting there. Check back in a few weeks!