4 ms·
this is all wrong, sorry. modern js is still js. the fact that linters are _required_ to keep code sane is proof enough. typescript is a different language, i'
by baq 9y ago
this is all wrong, sorry.
modern js is still js. the fact that linters are _required_ to keep code sane is proof enough. typescript is a different language, i'd wager it doesn't count, even though i agree it's a considerable improvement.
au contraire, many developers know exactly what programming in js looks like, especially compared to other languages. i used to think that c++ and boost compilation was crazy. now i look at glorified web pages with 200MB+ of dependencies and wonder how we got there.
i agree that js was a perfect choice for node.js, because it was the only choice for node.js - to use the same language that runs in the client. that doesn't make it a good - or even sane - choice in the greater perspective. python was and still is a good choice - twisted was used to create async services before ajax was a word. you can also take a guess from where the promise/deferred pattern took at least some of its inspiration.
- deleted 9y ago[deleted]
- bryanrasmussen 9y agoWhat language do you use that does not have a linter?
- yoodenvranx 9y ago> wonder how we got there I fully blame the virtually non-existant standard build- and module system in C/C++/JS for a lot of the current problems. This is one of the reason I really want to learn Rust. Compared to make/npm/gulp its infrastructure looks heavenly.
- nawitus 9y ago> python was and still is a good choice - twisted was used to create async services before ajax was a word. Async was not part of the core language when Node.js was first released. Even today the library ecosystem of Python is fragmented, not everything works asynchronously.
- rwaldron 9y ago"linting" is subjective, preferential—not required. Python built linting into the language itself and it's super annoying.