> The techniques and technologies we’ve used on the new Twitter.com mean you only download and run code when it’s needed. So a mobile user won’t download the sidebar you see on the home page, and may not download the settings pages until they go to update their display name. However, it also means that the full functionality of the site is still available to them should they want to access it.

Can someone explain to Twitter's web developers that there's nothing groundbreaking about this idea? Like... lmao. That's how web apps should work. That's how traditional django and rails apps already work. I like JavaScript and React as much as any web developer but if you're loading unnecessary code that's actually degrading the usability then that's a problem to be fixed asap. And it's definitely not something worth mentioning in this press release.

Oh wait, this was post written by "software engineers", not "web developers". They're probably too smart for these details.