I think pushing the front-end to the browser is a wonderful thing. Now that browsers have the power to run an entire application inside of them, it makes sense to distribute that part and worry about scaling your API. Your front-end will never achieve better concurrency than running 100% on the client :).

As for the features themselves, I agree that slapping things together is a usability nightmare. This is also new/unexplored territory for the most part though, and it will take time for usability standards to catch up. Right now, most people on the bandwagon are just copying facebook/twitter and not thinking about how this affects their users.

Let's face it, the web is moving in this direction, and while it's great to sarcastically poke fun at people who are blindly following the masses (I'm all for this), constructive criticism would be a bit more helpful.

Yes, infinite scroll sucks, but non web nerds seem to really like it. I'd say implement it for feeds and other time-based data, but not for listing images/products/etc...or better yet, find a way to implement it via pushState.

Overall a funny post with great points. I don't think anyone is going to throw away their JS app because of it. I'm currently writing an app that NEEDS to use pushState because we have a music player that exists across page "loads." Ok, we could pop open a new window like Myspace does, but talk about usability annoyance...