I do find as a general rule that, even if I'm in control of the client
and the server, I still like having a dynamic scripting language embedded in my
applications. It lets me, tech support, or the customer change behaviors
without me having to do a recompile which makes my life like 100 times easier.
Of course there's a different between scripting some behaviors in an
otherwise compiled application, and trying to write an entire application in a
non-typed scripting language, but still, I think scripting languages are far
too valuable to completely dismiss.
Having never actually written a Ruby app more complex than a toy CRUD
application, I can't speak from deep experience as to what it's like as project
size gets bigger. I do, however, hugely share your concern about it, as I do
with any kind of loosey-goosey language that as code size gets larger,
maintainability gets damn near impossible. A developer can change two lines of
code in one module and bugs will start cropping up all over the flipping place.
Mind you badly designed compiled apps can suffer from the same problem,
but at least a type checked compiled application gives you a fighting chance.
Just my $0.02, but I'm sticking with java for the foreseeable future.
--- Pat
> -----Original Message-----
> From: Konstantin Ignatyev [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 12, 2005 9:15 AM
> To: Tapestry users
> Subject: Re: tapestry to JSF conversion
>
>
>
> --- Erik Hatcher <[EMAIL PROTECTED]> wrote:
>
> >
> > On Dec 12, 2005, at 9:08 AM, Leonardo Quijano
> > Vincenzi wrote:
> > >> Compilation isn't the key though. Testing (not
> > just unit testing)
> > >> is.
> > > As I like to re-test my 300+ pages applications
> > for a syntax error
> > > after a refactoring. I can use my time better, you
> > know.
> >
> > Ever hear of "continuous integration"?! ;) Commit
> > your changes,
> > let the server run the tests while you reply to
> > e-mails.
> >
>
> I guess the point is that statically typed language
> allows getting rid of many tests because compiler can
> do them.
>
> With dynamic access of any kind (Ruby, Java
> reflection, etc) we have to write much more tests than
> necessary.
>
> By the way IMO the necessity for all the dynamic
> conversions is kind of self fulfilling prophecy. The
> need caused by deficiencies of HTML probably because
> HTML considered being unmovable part, like deity given
> thing.
> Well, it is not the case: lets take CORBA or Hessian
> protocol for communications; Java Web Start based
> Swing client application for interactions; and vuala!
> – highly responsive, 0 clients side management,
> statically typed environment where we do not need to
> write and run gazillions of tests to check for
> assignments. Compiler does its job!
>
>
>
> Konstantin Ignatyev
>
>
>
>
> PS: If this is a typical day on planet earth, humans will add fifteen
> million tons of carbon to the atmosphere, destroy 115 square miles of
> tropical rainforest, create seventy-two miles of desert, eliminate between
> forty to one hundred species, erode seventy-one million tons of topsoil,
> add 2,700 tons of CFCs to the stratosphere, and increase their population
> by 263,000
>
> Bowers, C.A. The Culture of Denial: Why the Environmental Movement Needs
> a Strategy for Reforming Universities and Public Schools. New York:
> State University of New York Press, 1997: (4) (5) (p.206)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
