[lug] Development & reporting tool choices

[Steve Sullivan]

While an interpreted language is great for rapid development (I'm
a python fan myself), there is one big drawback: no static type
checking.  And that means when your code runs into any unusual
condition that you didn't test after your last mod, it can easily
die ... in the customer's lap.

While compiled languages like Java can be harder to work with, at
least you know the types agree before you even run it.  Also, if
you have to interface with someone else's software, it's nice to
have a guarantee on the types being passed back and forth.

Each has it's place.  I use Python frequently for quick
prototypes, and even some web sites.  But if I want to create an
API that is part of a large system, perhaps with other programmers,
I turn to Java.

Steve

On Mon, Feb 09, 2009 at 06:20:39PM -0700, Rob Nagler wrote:
> George Sexton writes:
> > Startup on the dual-core, 64 bit machines is about 140 seconds. On the 
> > single core, 32-bit machine startup is about 200 seconds.
> 
> You forgot to add the compile time.
> 
> bivio.com starts in about 12 seconds on a 3ghz dual-core 32 bit (Dell
> 2650).  No compile time.  My guess is that it reads about 1500 Perl
> modules at startup.
> 
> Why people still program "compiled" languages in this day and age is
> beyond me.
> 
> Rob
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug