4 ms·
This is nice video/article, but strongly outdated / missing "current" javascript maintainability standards. Not so much "javascript" specific advices here. No
by 131hn 10y ago
This is nice video/article, but strongly outdated / missing "current" javascript maintainability standards.
Not so much "javascript" specific advices here.
No words on ES6 classes, that help keeping a meaningfull syntax, rest parameters, template strings.
No words on nodejs callback as last arg best practice.
No words on generator & promises (nor async await) that totally change callback behavior. No word on synchronious throw / catch vs callback(err) pattern.
No words on code modularisation.
This video is 4 years old, believe we, javascript change, a lot (and the "maintainable" best practice)
No link to mozilla MDN, when it's now a de-factor standard for web & js documentation.
- ben_jones 10y agoAgreed, but I always find it interesting looking back at JS applications 4+ years ago (before I was a developer) and seeing how people groked the complexity. The design patterns in particular for javascript are interesting and I believe still the supporting pillars for frameworks such as Angular, Ember, etc. It's easy to forget those patterns in ES6 etc. because you don't need them as much (IMO) and that's probably a loss.
- continuational 10y agoNot to mention Flowtype or Type Script.
- navalsaini 10y agoHello. I recently wrote a nodejs framework which makes server apps more maintainable, by breaking up the app into loosely coupled modules. The framework is called https://github.com/archiejs/ https://github.com/archiejs/ and I have not yet posted it on show HN because the documentation is inadequate (and the roadmap is not clearly defined). PS... just wondering if you would like to be one of the first reviewers