3 ms·
There's a huge difference between actual pragmatism and shooting yourself in the foot in the name of pragmatism. No, you shouldn't build your program out of so
by jey 17y ago
There's a huge difference between actual pragmatism and shooting yourself in the foot in the name of pragmatism.
No, you shouldn't build your program out of some overengineered metahyperpolymorphic Proton and Electron base classes in the name of "elegance". But the problem with PHP is that it goes completely to the other extreme: it has no internal consistency and little foresight. Simplicity is a great desideratum, but it shouldn't come at the expense of sense.
- deleted 17y ago[deleted]
- netcan 17y agoIn the context of a startup hire, think about it this way: He has created something very popular and widely used for an extremely difficult to please market with a huge amount of competition, some of it from scary places. The domain is a hard one.
- invisible 17y agoI hear this stuff all of the time about how PHP fails to the point of destroying an application because of some oddities in the language. As if taking (easy) steps to correct these in the application itself is impossible. I don't think that is true. What pisses me off the most about it is that every person that ever mentions this forgets Facebook, one of the biggest players on the Internet, is built on PHP. (Along with Digg, Yahoo, Wikipedia, Photobucket, SourceForge, Flickr, Yahoo, Friendster, Wordpress/derivatives, Magento........). Not that that is the only language they use, but this is a ridiculous claim to say the least. Yeah, PHP has faults. So do most languages - but sometimes those faults are also strengths.