On Aug 14, 2:03 am, "Psyc Geek (TAB)" <psycge...@xxxxxxxxx> wrote:
> On Aug 13, 1:27 pm, Matt <m...@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> > Moshe Goldfarb. wrote:
> > > On Wed, 13 Aug 2008 06:59:27 -0500, Matt wrote:
> > Show a case wherein it costs significantly more to develop using
> > something like Java to ensure platform independence.
> Java is a very verbose language.
> It is now like the Cobol of the 70's.
This may be one of the reasons why so many Java "frameworks" are so
popular. Everything from J2EE to Eclipse provide nice toolkits that
do a lot of the "micromanagement" and let the developer focus on the
actual guts of the application. In many cases, plugins are more like
shell scripts, with minimal declarations that simply interact with
existing components.
> A lot of jobs for struts and spring.
And Eclipse, and Tomcat and JBOSS and ... Many applications are
programmed in Java on UNIX or Linux servers, and AJAX or RIA (Rich
Internet Applications) based on frameworks make it possible to put the
bulk of the application on the server, where it can be easily updated
and enhanced. Using XML to the client assures that new tokens going
either way can usually be ignored, providing better backward
compatibility options. In short, the whole life-cycle management
process gets much simpler and easier to manage.
One of the problems with "Thick client" applications on the desktop is
that a minor change for security fixes, bug fixes, or new features can
be very difficult to deploy. Managing the deployment can also be a
very complex process. Mandrake Linux was able to address this
problem by providing automated updates to the software, but even then,
you might have V-2.1 clients through V-2.4 clients interacting with a
similar range of servers, and even each other. Not everybody wants
every update, and many corporations want to test and validate upgrades
before they turn them over to thousands of employees. This is why Red
Hat Enterprise Linux provides this type of support as one of their
options.
Shell scripts, python scripts, perl scripts, ruby, and Java are all
good ways to handle simpler applications such as forms interactions.
Frameworks such as Rails, CPAN, and Eclipse provide ways to leverage
reusable components to produce very reliable and very managable
applications with very little effort.
> Most want to go Ruby on Rails.
> Some are going PHP or Python.
>
> Why go Java? You can do it faster in Ruby on Rails.
> Less hassle too......
|
|
