Re: Heron Needs a Killer App
Posted: Aug 26, 2005 2:44 AM
> > Would you not consider Smalltalk a fading language?
> I would not - it remains the source of nearly all new
> ideas in programming and is enjoying a resurgence.
I went through a Lisp Tutorial for 30 minutes, maybe
its coz I've been Javarized for 5+ years but man,
that stuff seems a bit too complex.
> generics - duck typing makes these unnecessary.
In my opinion, Generics are a complicated addition to a
language, I cannot say I'm was initially fond of its addition to Java for instance (but as one gets more
comfortable with its use, I think they're a powerful
tool), so OK I hear you on that one.
> traits - First implemented using Squeak Smalltalk
> If you want to see what people will be doing two years
> out, see what the smalltalkers are doing now.
In my humble opinion, I've found that everything that
can be done in one language can be done in another
(might require extra work - but can be achieved in
any case), most of us fullfill tasks as is needed
which is why I'm assuming a good chunk of us coders
use Java as we feel comfortable with it.
> How long does it take you to find and fix a problem? You
> have to identify it, write the change, add the println,
> recompile, reinit the VM, see if it works, edit, compile,
> rerun. That's a long cycle.
Believe it or not because of Java's OO nature, and
we usually spend significant design on structuring
classes and Design, it doesn't take that long.
> this immediacy - guess how many more problems I can find
> and fix per hour than you can.
I highly doubt that, by the way has this turned into
a SmallTalk vs. Java debate?
> How can we keep up? Our development environment is at
> t least an order of magnitude more efficient than yours.
Once again is this a Small Talk vs. Java issue?
Anyways, over the weekend I'll run some Googles on
SmallTalk out of curiosity so I hopefully have a
better understanding of its capabilities.
> I may be atypical, but my introduction to biology started
> with cell structure and we worked up in size from there.
> Kind of like programming.
I guess approaches are different I din't see a Microscope
till mid-semester (they first give us diagramatic
impressions of what we would see, identify them
then comes the microscope. Makes sense in programming
to first crunch out what everything is then break it
down (if need be with a debugger).