News for hackers. Stuff that matters.
Re:A set of best practices for JavaScript projects by th4dv on Wednesday July 05, 2017 @07:36AM (#14701554)
A lot of companies these days create "Best practices" guidelines just to boost their online recognition. Very often I find these guidelines useless or even harming.
Re:A set of best practices for JavaScript projects by magic_beans on Wednesday July 05, 2017 @10:22AM (#14702602)
What in this document do you find useless or harming?
Re:A set of best practices for JavaScript projects by th4dv on Thursday July 06, 2017 @08:03AM (#14709692)
Basically every statement that says "Never do A" or "Always do B" without providing any justification for it. Documents like this only contribute to holy wars between junior developers by creating an impression that they should blindly obey some random set rules rather than forming balanced opinions.

This document should rather be called:

"Some practices for JavaScript projects that work for devs at Hive but might not necessarily work for you."

Re:A set of best practices for JavaScript projects by camus2 on Wednesday July 05, 2017 @05:22PM (#14706220)
> What in this document do you find useless or harming?

The use of TC39 proposals IN PRODUCTION. The authors of that document aren't serious.

Re:A set of best practices for JavaScript projects by magic_beans on Thursday July 06, 2017 @05:47AM (#14709167)
Presumably they use a tool like Babel to compile down to present day ES in production??