25 ms·
I am ecstatic to see that some node.js frameworks are trying to move toward being aggregations of standalone modules rather than growing into monolithic coupled
by courtewing 15y ago
I am ecstatic to see that some node.js frameworks are trying to move toward being aggregations of standalone modules rather than growing into monolithic coupled frameworks.
Monolithic frameworks are plentiful in the PHP community, but recently some of the larger frameworks have started moving toward this aggregate component model. Unfortunately, the PHP frameworks are much older than node.js, so many of the corresponding micro-communities are entrenched in the idea that their framework is "best". This means that while it is awesome that frameworks are allowing you to consume individual components, you still do not see it happening very frequently. You almost never see the frameworks themselves sharing components, for example.
Obviously the module system baked into node.js helps steer the community toward the concept of consuming modules, but I'm optimistic that the community is also young enough to completely embrace the idea of frameworks being little more than aggregates of the most common modules for building apps and also that "sharing" between frameworks is not something to frown upon.
- bergie 15y agoOne big difference is that Node.js had an easy way to share small libraries between projects almost right from the beginning. Something like NPM is only now starting to appear in PHP, and seems to be slowly breaking projects out of the reinventing-the-wheel mindset. A great example is Drupal using the Symfony2 HTTP foundation (request and response objects, etc) http://bergie.iki.fi/blog/composer_solves_the_php_code-sharing_problem/ http://bergie.iki.fi/blog/composer_solves_the_php_code-shari...