Maintainable JavaScript (2014) • Hacker News Board

Re: Maintainable JavaScript (2014)

#21

Post by 131hn » Sat, Jul 16, 2016, 1:53 PM UTC

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.

Re: Maintainable JavaScript (2014)

#22

Post by ben_jones » Sat, Jul 16, 2016, 3:44 PM UTC

malcolmgreaves wrote: post #18

Touche wrote: post #16

Earlier quoted context omitted.

Adding a build step adds complexity.

No. Using a weak, dynamically typed language adds complexity. Using a compiler isn't adding complexity.

Except the transpiled code is still dynamically typed. People act like when they started writing Typescript they stopped writing bugs..

Re: Maintainable JavaScript (2014)

#23

Post by ben_jones » Sat, Jul 16, 2016, 3:46 PM UTC

131hn wrote: post #21

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 synchron…

Agreed, 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.

Re: Maintainable JavaScript (2014)

#24

Post by philbo » Sat, Jul 16, 2016, 4:05 PM UTC

gcanti wrote: post #17

blubbi2 wrote: post #11

Earlier quoted context omitted.

Probably easier to just use an assertion library here. E.g. assert.ok(element)

I wrote a library [1] and a babel plugin [2] (bonus point: is Flow compatible) in order to deal with those cumbersome runtime type checks. [1] https://github.com/gcanti/tcomb [2] https://github.com/gcanti/babel-plugin-tcomb

Heh, me too: https://github.com/philbooth/check-types.js

Re: Maintainable JavaScript (2014)

#25

Post by douche » Sat, Jul 16, 2016, 4:24 PM UTC

deevus wrote: post #14

Do people still use Grunt these days?

Of course they do, if they've got a working setup. I haven't seen that Gulp is really any faster or easier to setup, so...

I'm way too young to be a grumpy old man, but I kind of wish people had just decided to learn how to use Make instead of re-implementing it over and over.

Re: Maintainable JavaScript (2014)

#26

Post by jiggly_piff » Sat, Jul 16, 2016, 5:10 PM UTC

deevus wrote: post #14

Do people still use Grunt these days?

Webpack accomplishes everything you would need grunt/gulp for and is much more powerful. Grunt is essentially obsolete at this point

Re: Maintainable JavaScript (2014)

#27

Post by continuational » Sat, Jul 16, 2016, 5:59 PM UTC

131hn wrote: post #21

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 synchron…

Not to mention Flowtype or Type Script.

Re: Maintainable JavaScript (2014)

#28

Post by [deleted] » Sun, Jul 17, 2016, 2:18 AM UTC

[deleted]

Re: Maintainable JavaScript (2014)

#29

Post by navalsaini » Sun, Jul 17, 2016, 2:21 AM UTC

131hn wrote: post #21

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 synchron…

Hello. 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/ 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

Re: Maintainable JavaScript (2014)

#30

Post by ehnto » Sun, Jul 17, 2016, 3:31 AM UTC

jiggly_piff wrote: post #26

deevus wrote: post #14

Do people still use Grunt these days?

Webpack accomplishes everything you would need grunt/gulp for and is much more powerful. Grunt is essentially obsolete at this point

While true, that doesn't necessarily mean everyone needs to run off and learn Webpack. The treadmill of technologies in JS can be very exhausting so if Grunt is working for your project, why spend the cycles learning entirely new tooling?