3 ms·
It's extremely mature, stable, reliable, and easy to reason about. Personally I wouldn't choose it but, for a larger company, if you already have engineers tha
by abritinthebay 10y ago
It's extremely mature, stable, reliable, and easy to reason about.
Personally I wouldn't choose it but, for a larger company, if you already have engineers that know it - and trust me many will - it's not a bad choice.
This is especially true if you are just serving a simple website for a product or service, even basic e-commerce. 90% of websites out there don't need Rails, or Python, or Go, or Node.
- qaq 10y agoY but it's so slow to evolve it's just sad. We've being using hacked on "traits solution" since 2006 (via build script) and PHP only got traits in 2012 and on and on. A lot of things that could make it more modern get shutdown.
- abritinthebay 10y agoModern for the sake of modern isn't needed for a good app. Especially a web app. Stability, availability of developers, and ease of debugging however are important. PHP has those. Granted it's not the only one, and I think there are better alternatives, but it's really easy to write a good app in PHP. Bad coding practices and bad application design will make ANY app have bad code. PHP just historically had a lot of that.
- tomschlick 10y agoLaravel is a pretty solid alternative in PHP vs Rails.
- qaq 10y agoY but if I have a choice I'd rather not use either :)