3 ms·
I prefer straight JS over CoffeeScript/TypeScript/Flow etc... I don't find require/modules to be too much of a mess.. unless you are using a lot of really larg
by tracker1 12y ago
I prefer straight JS over CoffeeScript/TypeScript/Flow etc...
I don't find require/modules to be too much of a mess.. unless you are using a lot of really large tool-chains with deep dependencies... npm dedupe helps point out problems there.
Breaking your logic into idempotent functional components without side effects as separate files/modules reduces a lot of what can be considered ambiguous or unexpected.
If you work with a functional flow, avoiding OO in JS as much as prudent, you can get a lot done without nearly as much confusion.
For now co/generators/promises get you really far along. In the future await/async will take it farther.