Where is the Real Ajax/Flex Revolution Happening?

andzik writes "Even with all of the buzz around Rich Internet Applications these days, using toolsets like Ajax and Flex, most sites that utilize these technologies seem to be incremental improvements, not revolutionary interface changes. Where does the Slashdot community feel the best opportunities are to substantially create different/better user experiences using RIA tools? What will be the killer app? Are we just not seeing them because the best improvements are being made to web based applications and not in the public space?"

On a related note, Vertigo asks: "Not so long ago everybody believed that it was a good thing to have the freedom to modify your software to suit your needs or to mangle your data in any way. But now that users are flocking to non-modifiable, one-size-fits-all web 2.0 apps like Gmail or Flickr, are we moving away from our open source ideals? Those services do provide many important benefits, but in the process of their enthusiastic adoption did we not loose sight of the most important issues?"

Semi OT: OpenLaszlo

[WoTG]

I've just discovered OpenLaszlo [openlaszlo.org] earlier this week. It's a (now) open sourced web RAD system. It compiles into Flash files so almost anyone can run the apps, and it feels a lot less hacky than Javascript ever did... blasted browser wars, "standards", and all. Pretty interesting technology -- especially if you can't wrap your mind around building an application in the Flash "everything is a movie" model. The IDE is an Eclipse plugin.

I think the original point to my post was that AJAX is nice but I don't think that the standards are there yet.

Standardisation is the killer app

[mdavids]

AJAX is a transition point in the web's evolution beyond the browser. The real killer app is what happens when these applications' communication protocols standardise. It's not so long ago that when you wanted to run a blog, you either hand-coded HTML or had to have a server running slashcode. Now you can choose between dozens of free and non-free web apps or hosted services, and it doesn't really matter which you choose because your audience can aggregate from any of these via RSS, and view your content in whatever client they choose. I'm sure Blogger.com is still a viable business, but it's increasingly irrelevant.

Similarly, it's rapidly becoming possible to share calendaring information with others via CalDAV without caring which client and server options you and your collaborators prefer.

Whenever I do a Drupal site for an organisation I like to encourage them to set up an LDAP directory, so that they can use the same authoritative data source for authenticating to Drupal and other systems, internal address books (usable from a multitude of clients), and finely-grained control over sharing personnel data with affilliated organisations. The ability to do all this is very cool, and not at all dependant on my choice of OpenLDAP (which is, frankly, a bastard to get working), as the critical element is the LDAP open standards.

These are pretty simple examples, but I don't think it's too much to expect that open standards for interacting with applications like Flikr and Del.icio.us will emerge, along with increased choice over back-ends and interfaces and effective commoditisation of the services. Value moves up the chain, innovators move on to the next big thing, and it all starts over again.

At least that's how it should work.

Matthew.

Excuse me?

[uber-human]

You want to use C for web coding? The two just don't mix!
JavaScript is flexible, simple, and already has the features needed for web development (like DOM).
C is NOT the answer to everything.