Am 27.04.2008 um 23:57 schrieb Santiago Gala:
I'm seeing a lot of activity using Ruby and/or Python, specially in
the
web front side. Modern frameworks such as Rails, Django, etc. In
general
diversity is increasing, but I've seen very interesting uses of those
two, and I'm guessing (I wish I had hard data) than nowadays typical
web
sites get better sustained productivity if written with Rails,Django,
etc. than with any of the "classic" java frameworks.
That's the fault of the "classic" java frameworks with lots of XML and
other bloat. It's not the fault of the Java language. You can have
Rails in Java too, see for example Grails. Newer frameworks like Sling
make development with Java fun again ;-) In the end the Java VM is a
very good platform, running all major scripting languages now. And
with OSGi you have a real good component system.
But let's not start another statically typed vs. scripting languages
argument. In the end both parties have their use case (a major one for
Java is this: it's very popular, does not require bleeding-edge
experts to program in and a lot of (enterprise) companies simply only
allow Java for their development, because it's proven and wide-spread
today).
Of technical concern is the fact that the java VM (or C#, a java
clone)
microarchitecture has a very small granularity for state, and a very
fine lock density (typically some mutable state and a lock per
object).
This plays very badly with modern hardware architectures,
It might not be optimized as Erlang, but it for sure does not "play
very badly". In fact, virtualization is a major trend and a VM is a
good platform there.
that are
happier with mostly read-only, not locked memory and concentrated
chunks
of writable memory (erlang excels there, even if it has an ugly syntax
and not so good libraries).
Erlang is just too complicated and ugly (albeit its concepts are
great!) to become popular and adopted by the mainstream.
Anyway, the discussion between everything-on-one-VM (Java) and many
processes (Ruby/Rails) doesn't lead to a single correct answer, just
as the general language discussion. Other languages might be good, but
there is a reason why the Apache Software Foundation hosts a lot of
Java projects that are developed, used and maintained by a lot of
companies.
So I'd definitely use Maven as the build system for the Java-part of
Shindig. And integrate it with the other languages. This depends on
what build system is good for them. If you use ant, it can be
integrated into Maven very well (eg. maven-antrun-plugin). Or you
could write maven plugins, which is actually quite simple (although it
seems very difficult at the beginning). This raises the following two
questions:
What are the shared resources in the end?
What are the most suitable build systems for the various languages?
WDYT?
Regards,
Alex
--
Alexander Klimetschek
[EMAIL PROTECTED]
>> Day JCR Cup 08 | Win a MacBook Pro: http://dev.day.com/ <<
