EthanEtienne

Yes and irony is often hilarious.

You try to use a cut scene or other how-to instead. *Good game devs.

Exactly, I just had to rant about that. Again though, cool CSS examples, but used for a very wrong task.

Really nice looking, I actually like Marco Barría's one (not as a spinner though).

Whenever you see a spinner or loading icon, you failed in UX design. Most of these feel slow and just plain wrong, they are pretty though, and the CSS is pretty awesome.

Use content progression instead of these damn spinners or loaders. Game dev's learned this a long time ago.

- my worthless 2c rant

I think I misread your comment, you wanted the article to be a how-to on how to plagiarize?

Yea this is a very common design pattern.

I here you, but sh!t happens. The lesson for me though is to choose your domain registrar as carefully as your infrastructure host, and have it be actively monitored like the rest of your infrastructure. I would still choose Pusher though. It's hard to scale everything in-house on limited resources, plus they make using WebSockets super easy (disclaimer: previous Pusher client).

OMG, sorry I have a hard time telling when people are being sarcastic, haha good one!!!!

Errr, dude, do you work for Microsoft? This is what got them into trouble in the first place, believing their own B.S. Sorry about the M$ slam, but damn, I keep hearing this over and over again, and it's so damn wrong (IMHO).

Mmmm, all I see is a beautiful site, I guess I'm brain washed.

Thank you so much man, you saved me and my team a bunch of development next week. ABSOLUTELY PERFECT TIMING!! We used the iframe trick, but it sucked. This is MUCH, MUCH, MUCH better, thank you!!!!

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.

Does anyone else see the irony in that he himself is a domain squatter? The shit he hates, he is himself.

Yea, I call complete B.S. Look how well the LinkedIn app performs. It's not as good as it could have been if it was 100% native, but it's no where near the bag of rocks the FB app was. I work on native iOS and HTML5 apps every day, HTML5 isn't close to native, but you can still get it to perform damn well enough. FB had no excuse for that shit they released, they should have held onto Joe Hewitt to fix it. (I don't know what the inside story was though).

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).