Ask YC: Whats better than AJAX?

What will be the most common web application framework for the next ten years. I'm just getting started in the industry and plan to put in my time. I want to do some indepth study and have been visiting the usual channels that discuss "the best" languages. Given that you YC folks are in the eye of the storm I thought to ask you. Best,

Well, if I was to predict the future I would say that we will see new browser architectures that will allow new types of code to be written that are not currently possible. I think web browsers will be more like a VM that can run any kind of code compiled to them instead of being forced to render only HTML and JavaScript. I would take a look at the things about web development that people currently complain about and would venture to say that some smart people will get together and address them.

If Adobe AIR and Microsoft Silverlight continue to gain traction then they could begin to replace AJAX-style implementations for feature-rich web sites.

The key word here is could.

Ok. This comment will be a little over the top, but here goes. I'm actually getting sick of how MS releases products. I never used to care enough to think that having everything under the sun covered was a problem. I think in the end, Microsoft's enormous technology and feature base will be what does them in.

To use Silverlight as an example, I think it sucks. It's bloated and I don't get it. I'm tired of playing catch up with MS technologies and all the freaking featues they pack into them. I mean: ASP.NET. ASP.NET AJAX VB.NET 3.0, LINQ, F#, C#, J# (being retired), VBScript, VS 2003, VS 2005, VS Team Foundation, Windows Workflow, Windows Communication Foundation and Windows Presentation Foundation. Seriously?

Windows Workflow in particular is extraordinarily huge. If keeping a program in one's head is important (and it is), then it's not going to happen with Windows Workflow. As I get more comfortable knowing what I want to code and how I want to code it, I'm finding myself just wanting to use stuff that gets it done in the path that is the most natural to me.

Silverlight? No, thanks.

AJAX is not a framework, others build theirs based on it. Anyway, it will be hot for at least 5 years so it doesn't really matter what will replace it.

Until then, the next version of XMLHttpRequest should somehow provide a way for the server to send a request to the client, not needinng the client to make requests all the time...

Or maybe you should be asking what will replace or make better the DOM?