The Keene View on Web 2.0, Ajax and SaaS

Ben Worthen of the WSJ recently posted an entry about Web 2.0 adoption. He sited a Forrester survey that concluded Enterprise Web 2.0 solutions would gain broad adoption in 2008 despite clear CIO resistance to the siren call of blogs and wikis.

As a strong proponent of Web 2.0 in the enterprise, we at WaveMaker want very much to see a rapid adoption of these technologies at the corporate level. On the other hand, wishing won't make it so - the grab-bag of technologies and ideas that constitute Web 2.0 are bound to confuse the IT community.

There are two possible observations here:

1. Damn the data, full speed ahead. Just like drug companies that sink a great deal of money into disappointing clinical trials that they then attempt to spin into medical break-throughs, analyst firms like Forrester won’t sell many copies of a Web 2.0 report that concludes Web 2.0 ain’t happening in the enterprise anytime soon. Thus there is a strong incentive for the report authors to refute their own data in the survey summary.
2. Web 2.0 is being pulled into the enterprise, not pushed. Since the PC, all client-side technologies have been pulled into the enterprise by business users, not pushed into the enterprise by central IT. The main themes of Web 2.0 – rich interface, collaboration and user-driven content – have more to do with how users interact with their computers than with computer infrastructure.

At my WebGuild panel this week, Rod Johnson of SpringSource observed that open source technologies like Spring and WaveMaker build unstoppable momentum within the IT organization by solving fundamental problems that much bigger players either cannot or will not solve.

For Spring, the tailwind came the intractable complexity of the EJB standard that left developers desperate for a simpler, more lightweight java application server. For WaveMaker, the tailwind comes from the complete dearth of visual tools for web development that would enable MS Access, Lotus Notes and PowerBuilder developers to come out of the client/server dark ages and build the kinds of web-based applications that their end users want.

Labels: access, powerbuilder, spring, WaveMaker

Mike Gunderloy of Larkware blogged about our MS Access to MySQL migration here. Mike is well known in the Microsoft community, although he has another blog, A Fresh Cup, that he bills as "notes from a recovering Microsoft addict," where he waxes eloquent on Ajax applications, Ruby on Rails and all things Enterprise 2.0.

The interesting point is that although there is a great deal of enthusiasm around Web 2.0 tools like Ruby on Rails, there are no Web 2.0 equivalents of the trusty drag-n-drop client/server tools like MS Access and PowerBuilder.

Face it, if you have to learn about Rails concepts like meta-programming and scafollding just to build a Web 2.0 app, your average VB developer is just going to continue taking a pass on this whole web thing and hope that it blows over.

Until there are Web 2.0 tools that provide a natural evolution from client/server development to web development, an entire generation of programmers will continue to hang fire. At a minimum, this will require drag and drop web development tools that don't require an entire bookshelf of manuals to get started building useful apps.

Labels: access, powerbuilder, ruby on rails

The MySQL developer community just published an article I wrote on migrating MS Access applications to MySQL.

The Enterprise Web 2.0 revolution is happening at the edges of the organization (democracy always enters by the side door). As proof of this, a recent MySQL user survey showed that 20% of MySQL users are using MySQL to port MS Access applications (in fact, this is the largest single segment of MySQL users!)

This article came out of a Birds of a Feather session at the MySQL User Conference. It summarizes best practices, tricks and tips for turning “fat client” MS Access apps into open-source, Web 2.0 apps using MySQL and ActiveGrid studio. Stay tuned for a joint ActiveGrid/MySQL webinar in early October, to be followed by a seminar tool and a sitcom spinoff on YouTube.

Labels: access, migration, mysql