3 ms·

Frameworks do not necessarily impose the complete design of the application. Spring Framework in Java, for example, is great, but the only essential part of it

Frameworks do not necessarily impose the complete design of the application. Spring Framework in Java, for example, is great, but the only essential part of it is DI container: you may not use persistence, presentation or security layer provided by it, if it does not fully fit your architecture. Good modularity defines quality of the framework and Rails is apparently not best on that criteria.

oafitupa 10y ago
Another example is Symfony2, which is completely decoupled (not just loosely coupled). Oh but php programmers are bad, am I right HN?
- vesak 10y ago
  No. PHP programmers aren't "bad", PHP is.
- proyb2 10y ago
  Magento and Shopify backend are awfully slow, it's the language, not the programmers.
  - andruby 10y ago
    Shopify is built on Rails, you know that right?
    - spdionis 10y ago
      And Magento is slow for a whole lot of reasons, nine of which are related to symfony.
      - AMHOL 10y ago
        Magento is slow because it uses EAV
      - oafitupa 10y ago
        You mean the first version of Symfony (Symfony 1, which was monolithic like Rails), and not the current Symfony (Symfony 2/3) which has nothing to do with the old one other than the name.
    - proyb2 10y ago
      I'm aware of that using Rails.
- spdionis 10y ago
  +1 for symfony being the perfect example if you're looking for a completely decoupled framework.