Walker Coderanger
walkercoderanger.com · Personal blog · on HN since 2014
Walker Coderanger writes critiques of JavaScript and its alternatives, including CoffeeScript, TypeScript and Dart, plus build tools and open-source advice.
What HN saysHN commenters link it in JavaScript debates, citing its argument that TypeScript is not the answer and its sketch of what CoffeeScript should have been.
17HN people shared it
6linked it in comments
18stories submitted
230story points
10 years agolast shared
2014people per year2026
Most-shared posts
- 1The JavaScript Minefield7 people · 8 points · first shared 2014 · 1 comments on HN
- 2What I Think CoffeeScript Should Have Been4 people · 5 points · first shared 2014 · discussion on HN
- 3Why TypeScript Isn't the Answer3 people · 42 points · first shared 2014 · 50 comments on HN
- 4The State of JavaScript Build Tools 20152 people · 7 points · first shared 2015 · 1 comments on HN
- 5Advice for Open-Source Projects2 people · 6 points · first shared 2015 · discussion on HN
- 6Why Dart Isn't the Answer2 people · 4 points · first shared 2014 · discussion on HN
- 7Why CoffeeScript Isn't the Answer1 people · 136 points · first shared 2014 · 142 comments on HN
- 8Are JavaScript Linters the Answer?1 people · 16 points · first shared 2014 · 12 comments on HN
- 9The JavaScript Minefield: A Proposal1 people · 5 points · first shared 2014 · 1 comments on HN
- 10CSS is Not Composable1 people · 1 points · first shared 2015 · discussion on HN
What HN people wrote when they linked it
ausjke · 2015-10-20
http://www.walkercoderanger.com/blog/2014/02/typescript-isnt-the-answe… so this blog is arguing typescript is not that good either.
Can we have a typescript-alike tool that integrates the "best parts of javascript" and defaults to 'use strict'? if there is one I'm in.
berserker-one · 2016-04-26
Maybe because JavaScript encourages bad habits? It's a very sloppy and undisciplined language, esp. with its loose typing, crazy coercions and wildly inconsistent semantics. This language has far more "warts" than any other programming language in wide use today. Jeff Walker calls it a "minefield": http://walkercoderanger.com/blog/2014/02/javascript-minefield
Jaecen · 2014-11-17
This looks to be an implementation of the concepts (but not the language) proposed in http://www.walkercoderanger.com/blog/2014/04/what-coffeescript-should-… Several of the terms used are exactly the same.
dmur · 2014-03-30
He covers that here: http://www.walkercoderanger.com/blog/2014/02/javascript-minefield/
rads · 2014-03-30
A little further down the same post [1]:
Given that a safe path through the JavaScript minefield isn’t enough, it seems like we need a detailed map of the minefield. Many books and blogs have been written to provide that map. JavaScript: The Definitive Guide by David Flanagan is one of the most detailed of those books. The JavaScript Garden is a good place to start learning about the mines online. [2]
[1] http://www.walkercoderanger.com/blog/2014/02/javascript-minefield/
[2] http://bonsaiden.github.io/JavaScript-Garden/