The Keene View on Web 2.0, Ajax and SaaS

The much-hyped but poorly defined terms Web 2.0, Rich Internet Application (RIA) and Ajax are best understood when they are defined together.

Buzzwords represent job security for entrepreneurs like me who would be practically unemployable were it not for our secret knowledge of the true meaning of words like Web 2.0. However, even I must admit that these Buzzwords 2.0 get in the way of clear communication.

In addition, while there are many standalone definitions of terms like Web 2.0, it is much easier to understand these buzzwords mean by considering them together. With that in mind, here are my definitions of Web 2.0, Rich Internet Application and Ajax, complete with helpful graphics:

• Web 2.0 represents a market shift in consumer attention from expert-generated content (Yahoo) to user-generated content (Google)
• Rich Internet Applications represents a requirements shift for more interactive, PC-like web sites to simplify consumer creation of content (Blogger, MySpace)
• Ajax is an architectural shift to support RIA requirements

Definition of Web 2.0 - Shift In Consumer Attention

Consumer eyeballs still rule the web. The huge power shift over the last 5 years has been from expert-driven content (which could be created using expert tools like Adobe Dreamweaver) to user-driven content (which requires web based tools that are easy to use). The shift in consumer attention is also driving a shift in business focus as corporations look at ways to engage more effectively with their customers and employees.

Definition of Rich Internet Application - Shift in Web Requirements

In order for more people to participate in creating content for the Internet, the content creation tools have to be both simpler and more interactive. Rich Internet Applications seek to erase the difference in user experience between browser-based applications (Gmail) and traditional client/server applications (Outlook). A quick comparison of Gmail versus Outlook shows that RIAs have a big usability gap, but the Internet brings the offsetting benefit of dramatically simpler application distribution.

Definition of Ajax - Shift in Web Architecture

Ajax is an architecture which makes the browser smarter and more interactive by running Javascript programs on the client. Don't tell anyone, but the old name for putting logic on the client was fat client programming. Everything old is new again and it turns out the only way to make an interactive client is to do more processing in the browser.

The following diagram shows the fundamental changes between the Web 1.0 architecture (circa 2000) and the Ajax architecture.

Where is all of this leading?

Web 2.0 is driving new application requirements and in turn creating a demand for new development tools that can meet those application requirements. Building increasingly visual and interactive web applications requires a WYSIWYG Ajax tool - something like a Microsoft Access for the Web. Flex and Silverlight, Adobe and Microsoft are providing proprietary tools for building RIA applications.

For an example of an open-source tool for building RIA applications based on Spring, Hibernate and Dojo, check out WaveMaker . Download Wavemaker to see what a visual Ajax tool looks like! Wikipedia also lists a number of other Ajax frameworks for building RIA applications.

References
A number of others have gone before me in defining these terms individually. Jonathan Schwartz recently pointed out that Java has always had RIA capabilities (but he also admits they didn't work very well until recently). Here are my personal favorites definitions:

• Web 2.0. Tim O'Reilly at O'Reilly Media has a good definition of what is web 2.0
• Rich Internet Application. Adobe initially defined the term rich internet application. The Burton Group also has a good white paper on Ajax and RIA (registration required).
  
• Ajax. Jesse James Garrett of Adaptive Path originally defined Ajax.

Labels: AJAX, RIA, Rich Internet Application, Web 2.0

I spoke yesterday with Michael Cote of Redmonk and Ryan Stewart of Adobe (the RIA blog is here, on ZDNet here podcast is here). What follows are some of the highlights of our discussion on the state of the RIA market.

Today, there are two ways to build your first Web 2.0 application:

1. Buy $300 worth of O'Reilly books and kiss the next few weekends goodbye


2. Download WaveMaker and follow the 15 minute tutorial

For anybody but the most hardcore or masochistic tech-heads, this seems like a no-brainer decision.

If Web 2.0 is about putting more power into the hands of end users, that message hasn't hit the Ajax world yet. In general, Rich Internet Applications toolkits from Dojo to Flex are well beyond the reach of anything but the most sophisticated developers (not that I am a particular fan of Flex).

WaveMaker is focused on lowering the price of admission for Web 2.0 application development. WaveMaker provides an easy on ramp to building web applications, allowing non-expert developers to build rich internet AJAX applications

How complicated an application can you build with a visual Ajax tool? Well, we built the WaveMaker studio using WaveMaker, so you can build a very complex application indeed using visual Ajax tools!

What kinds of applications are best for a visual Ajax tool like WaveMaker? We see our community building three kinds of applications:

1. Rich Internet Application prototyping. Business analysts


2. Rapid Application Development using database driven forms generation


3. Face of SOA applications. Assemble rich internet applications by combining web services and data services.

WaveMaker is the PowerBuilder for Web 2.0 - we make it easy for large community of people to get benefits of rich internet applications.

As usual, the bogeyman for all this Rich Internet goodness is Microsoft. The current fragmentation of the Ajax market and related squabbling between toolkits fanboys makes Microsoft's Silverlight solution a much simpler choice for developers.

More importantly, before the introduction of WaveMaker's visual Ajax studio, Microsoft's visual studio was winning over the novice developers by default. It's time for the open source world to provide a compelling and CIO-safe alternative to Silverlight and WaveMaker is just the company to do it!

Labels: ASP.NET, Dojo WaveMaker, Flex, RIA, Rich Internet Application, Silverlight, Visual Ajax

I know I'm dating myself, but Bill Cosby had a pretty funny routine where a PE Teacher explains that the purpose of air is to pump up basketballs and volleyballs.

Now Adobe has launched their Air product (with a matching Kevin Lynch NY Times article, and GigaOm fan dance) to allow platform to allow browser apps to escape from their little Firefox and IE prisons and flit gaily across the desktop like "real" apps.

Now what exactly are the benefits here? According to the NY Times article:

1. I can click an icon on my desktop instead of a bookmark in my browser. Yawn.
   
2. I can run an application without the browser border. Snore.
   
3. I can run an application offline. Now this is cool, but hardly new, following earlier moves by Google Gears, Dojo Offline and Mozilla Prism

As I have written, Air, Flex and Silverlight are"back to the future" approaches for Rich Internet Applications that would have us believe that the future of the web lies in a proprietary animation engine (Flash) or an ancient and proprietary fat client architecture (Silverlight).

At WaveMaker, we believe open-source toolkits like Dojo are the best enterprise Ajax choice a more flexible, open-source browser choice. To be fair, we in the Ajax community still have a lot of work to do to be truly ready to take on giants like Adobe and Microsoft - but that's where the power of the community can make a difference.

Speaking of community, you can come find out more about the the Dojo toolkit at the upcoming Visual Ajax User Group meeting. On Thursday, March 20 from 12-1:30 PST, Alex Russell, one of the co-creators of Dojo, will be talking about the Zen of Dojo - how to make Dojo development effortless for beginner and expert alike. Come in person or sign up for the webinar by sending email to rsvp@visualajax.org.

Labels: Adobe, Air, AJAX, Dojo WaveMaker, RIA

Although the computer industry is still young, we have already seen several waves of development tools. These waves follow technology and architecture trends: new technologies like the PC make new architectures possible, like client/server, which in turn require new tools, such as PowerBuilder.

Each wave of development has had a distinctly character - either logic-based or visually based. The tools to support each of these waves have been tailored correspondingly.

While the last 8 years have been dominated by thin-client architectures and code-based tools for expert users, the rich client technologies and collaborative user expectations behind Web 2.0 argue strongly that a new wave of development tools is beginning.

Here is my take on the four big development waves:

1. Green screen (1960-1990): centralized development with code-based Cobol tools


2. Client/server wave (1991-1997): departmental development with visual-based tools like PowerBuilder, Notes, Access, Oracle Forms.


3. Thin client wave (1998-2007): centralized development with code-based Java tools


4. Rich client wave (2008+): Web 2.0 democratizes development and dramatically opens up both the responsiveness and functionality of the client with an avalanche of Internet-based widgets and services. Can today's code-based tools targeting expert Java and C# developers ride this wave? History would say no.

It is hard to remember today - when all the development tools are code based - that all the client/server development tools were visually based. Ten years ago, visual tools like PowerBuilder and Notes dominated the development world. Now, the programming world has shrunk to just two code-based tools - Eclipse and Microsoft Studio.

We believe that the industry stands on the edge of a new wave of computing, driven by the Rich Internet Application architecture. Web applications are moving from static, limited html pages to much more responsive and powerful widgets and services.

The explosion of widgets and services available on the Internet is driving a demand among business users for more useful business applications. As thing client applications get more visual, coding tools like Eclipse and Microsoft's mis-named Visual Studio are increasingly awkward.

To underline this point, a recent customer was able to re-build an application in our visual tools using 98% less code than in .NET/Visual Studio. Note that it is important for visual tools to support coding for advanced services - we are not advocating code-free development, just code-lite development, particularly for visual web applications.

After nine months of hard work, we are ready to start making waves. Over the next month, we will be introducing a product that will launch the next wave of enterprise computing. Our vision is to be the Powerbuilder of Web 2.0.

To underline our commitment to this vision, we have changed the company name to WaveMaker. And that is exactly what we intend to do!

Labels: Eclipse, powerbuilder, RIA, WaveMaker

I just waded through a good article in DevX by Alexey Gavrilov on building Rich Internet Applications with Adobe Flex, Microsoft Silverlight and Sun JavaFX. The article worked step-by-step through how to build simple web applications with each of these products.

I had expected that there was some connection between Web 2.0, open source and the leaders in RIA. Instead, I found a set of time-warp technologies, each embodying its own uniquely idiotic approach. For the sake of brevity, I will here summarize the crowning idiocy of each approach:

• The fat-client approach. Microsoft has determined that the only problem with browser-based apps is that it doesn’t run fat client apps. Silverlight fixes that bug.


• The supermodel approach. Adobe was so entranced with the beauty of Flex’s audio-video capabilities that they forget to add little things like the ability to work with strings or dates.


• The once more with feeling approach. Sun decided to take another stab at making good on their most famous lie about Java, “write once, run anywhere.” Unfortunately for them, the Javascript Genie is out of the bottle.

None of these approaches supports Javascript as the primary scripting language. Don’t tell Adobe, Microsoft or Sun that Javascript is hot and that those crazy open source people are starting to assemble lightweight applications to run in web browsers.

Having said all this, the open source AJAX community has plenty of work to do in cleaning up its own house. The good news is that if this is what we’re fighting against, we have only ourselves to blame if the evil scientists win!

Labels: Flex, Java FX, RIA, Silverlight, Web 2.0