Commentary

John Foley
Editor, InformationWeek  

Web 2.0 Development For The Common Man

Talk about tilting at windmills. WaveMaker CEO Chris Keene is challenging Microsoft's Visual Studio while simultaneously pointing out the drawbacks of Java development. Keene may be suffering delusions of grandeur--or perhaps he's onto something.

Talk about tilting at windmills. WaveMaker CEO Chris Keene is challenging Microsoft's Visual Studio while simultaneously pointing out the drawbacks of Java development. Keene may be suffering delusions of grandeur--or perhaps he's onto something.Keene has been beating the drum of faster, easier Web 2.0 development since joining WaveMaker (then called ActiveGrid) in January 2007. The company's WaveMaker Visual Ajax Studio pulls popular open source development tools -- Spring, Hibernate, Dojo, etc. -- into a visual application builder. (InformationWeek featured WaveMaker as our Startup Of The Week earlier this month.)

Not long ago, WaveMaker released the results of a survey on Web 2.0 development that it commissioned from Precision Marketing Group. The key finding: 83% of respondents said their companies wanted to move applications to the Web but lacked the resources and expertise to do it. Keene argues the answer is to empower "nonexpert" developers to do that work using WaveMaker.


More SMB Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

By nonexpert developers, Keene's referring to developers whose experience has revolved around client-server software, say Microsoft Access or Lotus Notes, not salespeople or accountants. "Developers with 10+ years of experience with client/server tools have no clear way to 'upskill' to building Web 2.0 apps…" he writes in his blog. "WaveMaker is focusing on the skills migration."

Without such tools, Keene says, building rich Internet applications is beyond the scope of many developers. I talked to him about this recently, and you can see the interview below.

What do others think: Can a toolset like WaveMaker's lower the barriers to Web development?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links