That would the language that makes a hard requirement that you have a
C programmer on your team, because it can't do calculations at
anywhere close to hardware speeds.
The language run-time that requires manual interventions to prevent
memory leaks because it uses reference-counted GC?
On Sat, Jun 6, 2009 at 17:07, Johan Steyn<johan.steyn@gmai...> wrote:
>> Fritz Meissner wrote:
>> > In that case I'd be fascinated to hear what isn't a terrible language ?
> I wouldn't say Java is terrible. It avoids many errors that are common in
> C/C++ (where I started), but introduced other pitfalls - of which Heinz
> mentioned some.
> I wouldn't ever consider using .Net, and in my free time I (used to) dabble
> in a bit of Python, which to my senses is just plain no-nonsense
> straightforward done right. I have no interest in Perl anymore, and I
> haven't looked at Ruby, which I think gained popularity on the back of Rails
> rather than the language itself in it's own right.
> IMO, if you know some C for low-level, fast native apps, Java for enterprise
> apps, and Python for scripting - with obviously some intersection among
> them, then you are pretty much sorted to tackle any programming task without
> needing to know any other language.
> That said, I haven't looked at Lisp since 1992, but I don't see a need for
> it other than stretching my mind - which is a good thing in it's own right