Re:Why TypeScript Isn't the Answer
by WalkerCodeRangr on Sunday March 30, 2014 @01:28PM
(#7496971)
Sorry you feel I am wasting your time. I am actually working up to the point of what I think would be better. The purpose of writing about the inadequacies of the existing tools is to provide a justification for creating an alternative.
I also want to gauge interest in creating another alternative to see whether it would be worth my time and effort.
One of the reasons why you think TypeScript isn't the answer is "TypeScript doesn’t fix anything in JavaScript". You seem to fall into the trap of saying "Don't use JavaScript or anything that's like JavaScript" when in real life projects both are popular and effective. It's easy to laugh at the == operator but people don't use it, etc.
Re:Why TypeScript Isn't the Answer
by ScottBurson on Sunday March 30, 2014 @04:16PM
(#7497733)
As George Santayana didn't say, those who fail to study the history of programming languages are doomed to repeat it.
As long as language designers persist in making unnecessary and unfortunate errors in their designs, we need to point these out.
Stop wasting yours and others' time writing and reading these kinds of blog posts and concentrate on actually building something worthwhile.