2 ms·
Ok, I can believe that's true. I'm definitely talking pre-2010 here. But you speak of competing and avoiding pain - my point is why not just use something tha
by clienthunter 13y ago
Ok, I can believe that's true. I'm definitely talking pre-2010 here.
But you speak of competing and avoiding pain - my point is why not just use something that was decent from the get-go? I still don't get it.
Ruby/Clojure/Python/Javascript/Scala guys will wax lyrical about why they're awesome - ever seen Rich Hickey talk? That man has an ideology and a fiery passion for it. I never see anything remotely like this come out of the PHP world, just vague pseudo-defensive statements.
- citricsquid 13y agoPHP is ubiquitous. Not many people can walk into a company and convince their bosses to dump their entire stack, retrain all of their developers and then migrate to a new platform. If someone is programming for fun it may make sense to work with a platform that is more developer friendly (although as I mentioned, PHP is heading that way already so it's no longer the case that obviously PHP is terrible for everyone) but most developers don't get to choose to work in their favourite environment and fortunately a lot of people that had to work in PHP decided to make the most of it and work towards improving the ecosystem. All that matters is the people working with PHP build stuff, whether they do it with a skip in their step or they go to events and tell people how great PHP is doesn't matter, what matters is that they write code and a lot of people work in PHP because a lot of websites use PHP. There are currently 2000 jobs open on freelancer.com for PHP, for Rails there is 20.
- clienthunter 13y agoI never doubted it's ubiquity. If necessity and inertia are the answer to my query then I suppose I get that. I'd still be the guy in the room pushing for a piecemeal rewrite though.
- johnesj33 13y agoIf a company using PHP decides to switch to a different stack, chances are their developers will just need training, not retraining.