Re:Under the hood: Rebuilding Facebook for iOS
by wallywax on Thursday August 23, 2012 @05:24PM
(#4424935)
The press room site is not their main site, and I believe is not even run by Facebook. Many companies outsource their investor relations and press websites. None of Facebook's primary site is running ASP or anything Windows-related (they use PHP). It's pretty safe to say that none of the people developing Facebook's main site, services and mobile apps are behind the press site...
Re:Under the hood: Rebuilding Facebook for iOS
by eslaught on Friday August 24, 2012 @12:15AM
(#4426168)
Facebook develops their main site in PHP. They even wrote their own PHP compiler[1], and various other pieces of infrastructure (e.g. [2]). I'm not a huge fan of PHP, but compared to other PHP projects I've worked on their infrastructure looks nice and modern.
Re:Under the hood: Rebuilding Facebook for iOS
by dlitwak on Friday August 24, 2012 @12:18AM
(#4426179)
I read a venturebeat article on the LinkedIn app, seems like they used some Node.js, a bunch of work arounds and A LOT of domain expertise to get it to work as well as it does. I personally found the article interesting as I'm trying to figure out native vs. HTML5. seems like, barring incredible expertise about the quirks of html/js, native is the way to go.
Re:Under the hood: Rebuilding Facebook for iOS
by evanlong on Friday August 24, 2012 @03:34AM
(#4426640)
LinkedIn app. It sucks. Rotation is clunky and slow.
Do you work on an HTML5 cross platform app everyday like FB engineers did? Guess what. That's when shit gets really tricky and hard.
Re:Under the hood: Rebuilding Facebook for iOS
by EthanEtienne on Sunday August 26, 2012 @05:14AM
(#4434729)
That's exactly why you should keep things as simple as possible. Adding features does not mean a better app. Simplicity first, make it USEABLE first.
I read the story on FB newsroom. I see that site is built on OLD asp.net webforms. Not even asp.net MVC. If their devs are constantly using the oldest of tech to create their site, it's no wonder their shit performs so badly.
Now I have no idea or backstory to why they choose these routes, they most probably simply didn't have any developers with enough experience or skill set to use newer better performing tech (I hear it's hard to find good developers).