Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Oh wow. Wow. I hereby revoke my previous statement. These are some God-awful infrastructure decisions. Version control and a staging server are the most basic necessities for a scalable dev project. I even set them up when I'm working on a personal project, alone.

Exactly. This seems to follow the Kevin Rose formula: make horrible decisions (or be entirely absent from decision making) without any understanding of technology, then blame your developers and technology choice ("Digg V4 failed to due to Cassandra").

If it weren't for Facebook's success, I can bet you'd see people blamining PHP for Digg's failure: prior to Facebook, P in LAMP also stood for Perl (and occasionally Python) and LAMP wasn't "universally" considered proven (unlike J2EE + Oracle or .NET + SQL Server), nor has Facebook been even remotely close to a "vanilla" LAMP site (since at least 2005)-- with many mission critical subsystems also being built in Java and C++ .



> prior to Facebook, P in LAMP also stood for Perl

The P in LAMP has been associated with PHP for much longer than the existence of Facebook.


I've always seen it stand for Python, Perl or PHP-- with many shops specifically stating "P for PHP" or "P for Perl". Yahoo hasn't settled on PHP vs. mod_perl (as a replacement for a C based template system filo built) until early 2000s and (when I was there) still had many Perl based services in production.


When I interned at SBC/Yahoo DSL around 'mid 2000s, they used the LAMPerl stack quite extensively.


I think I remember around 2005 being surprised at hearing PHP stand in for the P, before that it had always been Perl. Though it probably had to do with the circles you ran in.


Maybe. We did LAMP before I heard the term, with a site in '98, but then it was definitely Perl. I've understood it as mainly Perl, and later PHP or Python as possibilities.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: