4 ms·
that's a false economy since you must also include however many bytes it takes to explain in a comment that you used == on purpose, and not as a typo- to warn f
by ZenPsycho 15y ago
that's a false economy since you must also include however many bytes it takes to explain in a comment that you used == on purpose, and not as a typo- to warn future maintainers not to switch it to === when they run it through JSLINT.
- maratd 15y agoYou put comments in code? I place all comments in a separate markdown file.
- ZenPsycho 15y agoI normally don't. Unless I do something silly like use == that could be taken as a mistake.
- vertr 15y agoCould you share a link that describes this? I'm having trouble finding anything about it.
- maratd 15y agoJust take a look at how Mootools or Node.JS takes care of their documentation. Same principal. There is no need for comments/documentation to muck up code.
- leptons 15y agoPut comments in code, and then run your code through YUI or similar to strip the comments and whitespace when deploying.