4 ms·

> Instagram team have been as successful had they chosen > PHP? I think not. Can you elaborate, why you think so? PHP worked OK for Facebook and Wikipedia.

cageface 15y ago
The time you don't waste fighting with the language and coding around its deficiencies is time you can spend improving existing features and adding new ones. If you're trying to run a lean startup with only three backend people like Instagram these effects are very important. Those three engineers could have coded something similar in PHP but I'll guarantee you it wouldn't have been as good. Facebook can afford to throw money at the problem and nobody's really trying to compete with Wikipedia so they can get away with it.
- sanswork 15y ago
  I've developed large applications in PHP for years. Currently we're using other languages at my current company for a couple of reasons. They could have coded the exact same thing in PHP and I doubt it would have taken them any longer. The language isn't great but I never found myself truly fighting it just displeased with some of the syntax. Facebook started with PHP they weren't always the massive company they are today and managed to displace other entrenched social networks.
- knieveltech 15y ago
  Time savings? How's downloading the entire feature set for content creation, categorization,user management & authentication, and menuing in 45 seconds stack up to arsing around in a text editor setting up your file structure for a new development project?
- rimantas 15y ago
  > fighting with the language and coding around its > deficiencies That's still too vague. Sure PHP has it warts, but I don't recall anything I could call "fighting with the language". Yep, stack/needle mess and inconsistency in naming is annoying, but not exactly a huge time waster.
- wauter 15y ago
  > Facebook can afford to throw money at the problem Aaah the good old circular reasoning of dismissing the big guy - they did get big enough to be able to afford money by using PHP too you know.
weego 15y ago
This sounds very much like the new version of "I can tell it's a rails app by how it looks". The idea that the server tier language has a direct effect on the user at the level of code quality we are discussing is naive at best and trollish at worst.
- cageface 15y ago
  Are you seriously arguing that all backend languages are essentially interchangeable? Give competent team A six months to build something in PHP and competent team B six months to build something in any of the better options and team B will build a better product every time.
  - ErrantX 15y ago
    Do you have any evidence to back up this assertion? Because I would imagine it depended a lot on the skill of the teams in question - and if evenly matched they would produce similar quality.

cageface 15y ago

The time you don't waste fighting with the language and coding around its deficiencies is time you can spend improving existing features and adding new ones. If you're trying to run a lean startup with only three backend people like Instagram these effects are very important. Those three engineers could have coded something similar in PHP but I'll guarantee you it wouldn't have been as good. Facebook can afford to throw money at the problem and nobody's really trying to compete with Wikipedia so they can get away with it.

sanswork 15y ago
I've developed large applications in PHP for years. Currently we're using other languages at my current company for a couple of reasons. They could have coded the exact same thing in PHP and I doubt it would have taken them any longer. The language isn't great but I never found myself truly fighting it just displeased with some of the syntax. Facebook started with PHP they weren't always the massive company they are today and managed to displace other entrenched social networks.
knieveltech 15y ago
Time savings? How's downloading the entire feature set for content creation, categorization,user management & authentication, and menuing in 45 seconds stack up to arsing around in a text editor setting up your file structure for a new development project?
rimantas 15y ago
> fighting with the language and coding around its > deficiencies That's still too vague. Sure PHP has it warts, but I don't recall anything I could call "fighting with the language". Yep, stack/needle mess and inconsistency in naming is annoying, but not exactly a huge time waster.
wauter 15y ago
> Facebook can afford to throw money at the problem Aaah the good old circular reasoning of dismissing the big guy - they did get big enough to be able to afford money by using PHP too you know.

weego 15y ago

This sounds very much like the new version of "I can tell it's a rails app by how it looks". The idea that the server tier language has a direct effect on the user at the level of code quality we are discussing is naive at best and trollish at worst.

cageface 15y ago
Are you seriously arguing that all backend languages are essentially interchangeable? Give competent team A six months to build something in PHP and competent team B six months to build something in any of the better options and team B will build a better product every time.
- ErrantX 15y ago
  Do you have any evidence to back up this assertion? Because I would imagine it depended a lot on the skill of the teams in question - and if evenly matched they would produce similar quality.