cvut / javascript Goto Github PK

Revisiting the guide a some of this stuff is primarily an opinion without substantial reasoning. Case in point is the recommendation to avoid ES6 class. For me the primary reason is that it invites reliance on inheritance and hinders composition, which is actually described in few of Elliot’s articles (and raison d'être of stampit). I should add it in later revision.

(But to be absolutely honest, my primary objective with such an opinionated guide is to push devs out of their comfort zone and rethink practices before they repeat the same mistakes we are doing in other languages. They can disagree, but they need to think why.)

Both have pros and cons. Function expression leads to better consistency (you cannot use function declaration for function composition, currying etc.), but it’s not hoisted (so it requires specific ordering of functions). Also you cannot write export default const foo = () => { }, but I consider this as insignificant.

Just a dumping place for brainstorm.

Standalone guides

• Git, i.e. crash course, basic operations, commit messages, pulling, rebasing, tools
  • Pull Requests - QA checks, code review
• Java? (@jirutka)
• 12-factor apps?
• Licensing

JavaScript guides

• libraries: what to choose, what to avoid, how to choose
• react

Perhaps this is a time to rewrite this stuff to ADoc?

Guide recommends to avoid classes and prototypes but doesn’t have a separate section about object factories as a recommended way (though FP part about data/behaviour separation is close). I should fix that in a later revision.