3 ms·
I'd say rails because the nodejs + PHP codebases I've seen aged poorly, but the rails one are still clean. The problem with node is that things move too fast. W
by antoineMoPa 9y ago
I'd say rails because the nodejs + PHP codebases I've seen aged poorly, but the rails one are still clean. The problem with node is that things move too fast. What was beautiful in JS 4 years ago now looks like legacy mainframe fortran. Laravel (a popular php framework) is nice at one point in time, but even 0.x.0 migrations will break you application and force you to work for hours...
- bnycum 9y agoMaybe as a counterpoint to your Laravel statement. I started using Laravel on some work projects at 5.3 and have upgraded them up to this weeks release of 5.6 without major issues or time spent doing so. I don't know much about the versions before that though. Other than it's not your grandfather's PHP along the bad habits from the early 2000's. I personally think my Laravel code has been pretty clean and concise.
- saluki 9y agoy, going from Laravel 4.2 to 5.0 can take some work but the upgrades since then have been quick and painless. I came from Rails to Laravel. It has a similar feel and in some ways is more fun to work with. Part of that is the great community and lots of make your life easier features. Especially Laravel Forge and Envoyer. Forge makes spinning up servers easy and secure and deployments a breeze. Envoyer adds zero down time deployments. These are both paid SaaS but they fund the development of the framework and provide way more value than the monthly cost. Laracasts is also great for getting up to speed with Laravel.