Re:My time with Rails is up
by ivan_gammel on Sunday May 22, 2016 @04:57PM
(#11750259)
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.
[ Parent
| on HN ]
Another example is Symfony2, which is completely decoupled (not just loosely coupled). Oh but php programmers are bad, am I right HN?
No. PHP programmers aren't "bad", PHP is.
+1 for symfony being the perfect example if you're looking for a completely decoupled framework.
Magento and Shopify backend are awfully slow, it's the language, not the programmers.
Shopify is built on Rails, you know that right?
And Magento is slow for a whole lot of reasons, nine of which are related to symfony.
Magento is slow because it uses EAV
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.