3 ms·

I'm slowly starting to genuinely understand DHH Omakase rant. The whole "modularity" part of Node doesn't seem to work out so well. Constantly have to look for

by seivan 11y ago

I'm slowly starting to genuinely understand DHH Omakase rant. The whole "modularity" part of Node doesn't seem to work out so well. Constantly have to look for third party support for simple but necessary things. Eg Strong Params, json builders or a Mailer. I wish there was JS framework that offered everything out of the box as a first party support or at least a decent API libraries could use. Like ActiveModel is used by various NoSQL gems.

dev360 11y ago
I think it depends on what you do. I spent first half of my career ordering a la carte.. In hindsight, I ended up building a lot of crap that the framework should have provided for me. This is the major reason why I have learned to be cautious with getting wowed by the apparent simplicity of micro frameworks. At the very minimum, I want a framework to have an opinionated model layer with migration support, and chances are you will get trickle down benefits from frameworks that have opinionated M layer.. Look at djangos form abstraction for instance. Or the way validation is handled in Django models, which in turn opens up for the possibility of creating a neat REST abstraction. These are the types of abstractions that you end up writing yourself or not writing at all when you go the 'light framework' route, but they are almost always handy and will save you time.
pluma 11y ago
Depends. Sometimes you want something like Rails or Django. Then express and similar "a la carte" solutions won't help you and you'll end up re-inventing frameworks and re-implementing the same old bugs and mistakes. Sometimes you just want a small single-purpose server. Then Node and NPM shine and big frameworks seem like unwieldy behemoths in comparison. Personally I'd say Node isn't a good choice for the former and you'd be better off with something powered by Ruby, Python or PHP (i.e. Rails, Django etc). And I say that as someone who's been almost exclusively using JavaScript for the past couple of years.

by seivan 11y ago

dev360 11y ago

I think it depends on what you do. I spent first half of my career ordering a la carte.. In hindsight, I ended up building a lot of crap that the framework should have provided for me. This is the major reason why I have learned to be cautious with getting wowed by the apparent simplicity of micro frameworks. At the very minimum, I want a framework to have an opinionated model layer with migration support, and chances are you will get trickle down benefits from frameworks that have opinionated M layer.. Look at djangos form abstraction for instance. Or the way validation is handled in Django models, which in turn opens up for the possibility of creating a neat REST abstraction. These are the types of abstractions that you end up writing yourself or not writing at all when you go the 'light framework' route, but they are almost always handy and will save you time.

pluma 11y ago

Depends. Sometimes you want something like Rails or Django. Then express and similar "a la carte" solutions won't help you and you'll end up re-inventing frameworks and re-implementing the same old bugs and mistakes. Sometimes you just want a small single-purpose server. Then Node and NPM shine and big frameworks seem like unwieldy behemoths in comparison. Personally I'd say Node isn't a good choice for the former and you'd be better off with something powered by Ruby, Python or PHP (i.e. Rails, Django etc). And I say that as someone who's been almost exclusively using JavaScript for the past couple of years.