Java on Snails is an open-source web framework philosophy that's optimized for programmer job security and sustainable effort. It lets you write verbose code by favoring configuration over convention.
In the past year, Ruby on Rails has shown that convention over configuration, metaprogramming, and dynamic languages can combine to enable you to make web applications quickly. Unfortunately, this blistering speed of development has left many programmers out of breath.
The csmonitor.com article, Is there time to slow down?, explains anthropologist Edward T. Hall's notion that there are two broad cultural approaches to time: polychronic and monochronic.
Polychronic people, [Hall] said, are involved with many things at once, while monochronic cultures emphasize doing one thing at a time. ... Polychronic people change plans frequently, consider schedules as goals instead of imperatives, and focus on relationships with people. Monochronic cultures emphasize the opposite. People stick to the plan, emphasize promptness, and are accustomed to short-term relationships.
Java on Snails is an effort to promote a more polychronic attitude towards development. Yes, you may have to type more when you use a traditional approach to Java web application development, but each semi-colon, curly brace, and angle bracket can be savored and bring joy to the developer who has adopted an appropriate mindset. And besides, all those XML sit-ups, as the Rails designers like to refer to the Java community's love affair with XML configuration files, can help build strong intellectual abs.
Given that Java on Snails is a web application framework philosophy, not an actual framework, it has no download URL. Instead, developers are invited to relax with a cup of tea and spend some quality time investigating Java's many web frameworks and database layer tools that may be combined to help you build your web application. Is not life too short to be in such a hurry all the time?
> <p> > In the past year, <a > href="http://www.rubyonrails.org/">Ruby on Rails</a> has > shown that convention over configuration, metaprogramming, > and dynamic languages can combine to enable you to make > web applications quickly. Unfortunately, this blistering > speed of development has left many programmers out of > breath. > </p> > Do you mean that you're forking Apache Struts because Struts Action 2.0 is just not good enough?
I know. Frank and I were talking this morning about how it was too late to post our April Fools Day idea, but then it occurred to me how monochronic that kind of thinking was. Posting two days late was I think a fitting demonstration of the polychronic attitue that schedules are goals not imperatives.