4 ms·
This seems to be a common essay from well-established companies who use PHP and then write "oh gosh we use PHP!" The key here, as it states, is that they "buil
by OzzyB 15y ago
This seems to be a common essay from well-established companies who use PHP and then write "oh gosh we use PHP!"
The key here, as it states, is that they "built their own framework/libraries", which essentially means nothing to indie-devs and other small non-well-established companies who want to build something...
So the trend is simply this:
1) We use PHP because it's what we know, easy to get started with etc.
2) It gets us by while we build our business
3) Profit! Re-factor our codebase, in PHP!
Thus, the blog post should read: "Hey Mailchimp is doing awesomely, so we refactored our PHP codebase with our very own custom framework!"
It's not that PHP is all bad; it just lost the "framework wars" IMO, and I think when companies come out and state things like this, it kinda proves it...
- Mikushi 15y agoNot really, being PHP, Python or Ruby, with the kind of load they are dealing with, no framework available out there is fitted.
- middus 15y agoThe key here, as it states, is that they "built their own framework/libraries" In the end, isn't that what everybody is doing anyway?
- OzzyB 15y agoWell yes, when you speak to experienced PHP devs that's their response when confronted with the "PHP sucks" argument -- they always say they have their own framework/libraries, which don't suck and thus in turn "PHP is fine"... I don't think everyone is doing that (building frameworks), or can, or even should when they're other possibilities outside of the PHP world...