Facebook PHP Source Code from August 2007

Post by jafaku » Sat, Oct 12, 2013, 6:23 PM UTC

pestaa wrote: post #30

Encosia wrote: post #20

Earlier quoted context omitted.

I remember listening to an interview with Markus from Plenty of Fish, where he essentially said that he didn't worry too much about site errors because most unsophisticated users would attribute them to things like their ISP, browser (if they knew what that was), or their own error more often than to the site itself. Personally, I can't bring myself to not care like that, but it seems to have worked pretty well in th…

I must admit my comment was unneccessarily bitter, but my observation is completely different. Many friends and family members are now seeing data loss on Facebook weekly at least . I wouldn't call them tech savvy either, yet they can attribute the issue to Facebook, after having learnt the simplest basics of how the web should actually work.

Post by [deleted] » Sat, Oct 12, 2013, 6:25 PM UTC

nwh wrote: post #64

robryan wrote: post #57

Earlier quoted context omitted.

They would be applying some search logic in memory in PHP. Depending on what you are doing it does make sense to load in a heap of data from the database then narrow it down in PHP.

That sounds grossly ineffective. Reminds me of some production PHP I saw once, returned the entire database (`SELECT * from 'db'`) and manually walked through it with a for() loop. It wasn't very efficient at scale.

Post by MAGZine » Sat, Oct 12, 2013, 6:32 PM UTC

kaolinite wrote: post #90

g8oz wrote: post #89

Earlier quoted context omitted.

Ship too late and none of it will matter.

I guess shipping is more important to you than the possibility of losing user details (or worse). Christ, I hope I never give my details to a company you found. Shipping quickly is important but it's also important to write quality code. Small bugs that can easily be fixed are fine but security problems or bugs related to payments, for example, are not.

Post by pault » Sat, Oct 12, 2013, 6:44 PM UTC

7Figures2Commas wrote: post #76

a1a wrote: post #44

Earlier quoted context omitted.

You make a fair point and I guess everything is relative. My post was not meant to trash the code, but rather to point out that this code shows us that the primary objective shouldn't necessarily be writing the perfect code.

> My post was not meant to trash the code, but rather to point out that this code shows us that the primary objective shouldn't necessarily be writing the perfect code. That's a dangerous argument. I mean, if startups stopped pursuing the most elegant code, they wouldn't need, nor would they be able to hire, the "best" developers. And then what? 1. Lots of startups would be able to get off the ground and grow with le…

Post by smsm42 » Sat, Oct 12, 2013, 6:59 PM UTC

lifeformed wrote: post #60

How did someone "expose the PHP source code"? Did they actually find a way to make the code show up client-side, or was it just someone who managed to get access to the backend stuff? The way it's worded makes it sound like the former, but that seems unlikely...