As I'm compiling the concept and contents for a brand new gobi
based
helma.org
site, I have repeatedly noticed the same
dividing line going down straight through the middle of Helma
and the entire industry.
Is Helma a Java Application Server or a Javascript Application
Server? No, it is a Javascript-able Java Application Server.
Java is a strictly-typed language, Javascript a dynamically typed
one, and Helma is kind of sitting on a fence between the two
worlds.
Freedom Languages vs Safety Languages
Cant we all just get along?
http://www.journalhome.com/codecraft/9003/
This same divide continues through many other topics such as
the embedded database vs the object/relational mapping, the
extent to which coding conventions for Helma apps should be
established and encouraged vs the creative freedom of scripting
with all its pitfalls, etc.
Of course, we do not want to sit on a fence, but getting off the
fence in either direction means not using the full power Helma
has to offer on both sides - and turning away potential users
that might find Helma to be an ideal environment for their
personally preferred coding and development style.
Instead of being split by this divide, Helma could just get rid of it.
So, I'm working on describing Helma in a way that eliminates this
tension. If you recently have come across some articles that you
think I should read,
please let me know
.
Also, what do you expect from a fresh helma.org site? Any
suggestions regarding the structure and content are of course
very appreciated. I'm hoping to time the new site with the
release of Helma 1.5 or soon thereafter, therefore it will be put in
place rather quickly and then grown from there.
In the future, helma.org will have two sites, one for the
development of Helma itself and one for the users developing
with Helma, just like we now have the
helma-user
and
helma-dev
mailing lists.
30.08.2005, 13:24