4 ms·
With every "invention", framework that attempts to cover or correct a (of many) Javascript failing, I'm inclined to give Dart (or other clean slate language) a
by FeloniousHam 13y ago
With every "invention", framework that attempts to cover or correct a (of many) Javascript failing, I'm inclined to give Dart (or other clean slate language) a real shot. Pulling node into the client to get dependency support is clever, but suggests there must a better way.
I like Javascript for my own stuff, but it's a crap foundation for the future of computing (and I wouldn't want to support it for large systems).
- pkrumins 13y agoI don't see what's wrong with JavaScript?
- FeloniousHam 13y agoThere's been much ink spilled over Javascript's failings (eg. http://rdallasgray.github.io/blog/2013/06/09/whats-wrong-with-javascript/ http://rdallasgray.github.io/blog/2013/06/09/whats-wrong-wit...), but my high-level complaints: 1. becomes difficult to maintain large codebases for language-induced problems without multiple external libraries/frameworks/systems and/or expert practitioners. 2. code readability is all over the place (in contrast to, say, Python or Java). In fact, the best written JS I find to largely inscrutable. This is likely a personal failing, but I'm the one writing this list. 3. you have to write in a different language to get Object Oriented capabilities (eg. Typescript, Coffeescript). I'm inclined toward OO, so if I'm going to write in a different language, I might as well go all the way. In short, amazing things have been in spite of Javascript, not because of it (not strictly true, since you can go nuts with the meta-meta generic programming in JS).