3 ms·
There's something I don't like when people talk about PHP, and that's putting Symfony/Laravel and XAMP/shared hosting PHP into the same bucket. I feel like it's
by Zababa 5y ago
There's something I don't like when people talk about PHP, and that's putting Symfony/Laravel and XAMP/shared hosting PHP into the same bucket. I feel like it's a dishonest way to present PHP as something it's not.
Symfony/Laravel PHP is basically like any other language, you could use Ruby with Rails, Python with Django, Java with Spring, Elixir with Phoenix and it's basically the same ballpark. But you give up the simplicity of setup and deployment.
XAMP PHP, on the other hand, is probably one of the most accessible way to do web programming, but isn't the same at all as Django, Rails or even Symfony/Laravel.
You use the same language, sure, but the two are very different beasts. You could probably add a third with the world of PHP-based CMS, like wordpress or drupal.
- azangru 5y ago> Symfony/Laravel PHP is basically like any other language ... But you give up the simplicity of setup and deployment. > XAMP PHP, on the other hand, is probably one of the most accessible way to do web programming, but isn't the same at all as Django, Rails or even Symfony/Laravel. I'm confused by this assessment. As far as I understand, it is not unusual for hosting providers to offer shared hosting that supports php, but not other popular server-side languages, and makes it possible to run Symfony or Laravel, but not Django, Rails, Spring, or Phoenix.
- Zababa 5y agoMy point is that if you're using Symfony/Laravel and composer, the difference between shared hosting or anything else that would run your python/ruby/java/elixir code is relatively small.