[ale] {OT} -- For the programmer on the list

Wolf Halton wolf.halton at gmail.com
Thu Jan 12 22:58:13 EST 2012


On Thu, Jan 12, 2012 at 8:49 PM, Steve Brown <scbrown3 at gmail.com> wrote:

> On Thu, Jan 12, 2012 at 4:10 PM, JD <jdp at algoloma.com> wrote:
>
>>
>> * Eats RAM (much more that a C++ program would use)
>> * Slow during runtime (old link
>> http://sprout.stanford.edu/uli/java_cpp.html )
>> * Garbage collection runs at the wrong time
>> * Extremely slow desktop program startup
>> * Ugly GUI controls - opinion
>> * Eclipse requires 16GB and a Core i7 to be usable; it is slow on a Core
>> i5.
>> * Java devs actually believe they don't need to understand the platform
>> they are
>> running on. I have stories of developers claiming that rewriting a C app
>> running
>> on Intel CPUs in Java running on a SPARC CPU would result in greater
>> performance. Complete BS, except that their C app was total crap to start.
>>
>
> I couldn't agree more. To the last point, if their C app was crap from the
> start, the Java devs could have had a point. I always think twice though
> when someone says rewrite. But I do concede that Java is most definitely
> not the first choice for speed. I think this is an ok trade-off, at least
> for the past companies I've worked for; hardware is cheap, coder time is
> expensive.
>
> I have never had a robust-enough development machine to get Eclipse to do
anything but sit there looking cute.  Being more sysop than programmer, I
use bash scripting and Python.  At intervals I consider formalizing some of
my code by writing it in C.  I do not run JREs on all of my servers, so
though "Write once, run everywhere" sounds good in the marketing slicks, it
would take extra time and one more thing to maintain and upgrade.  I think
I would rather ./configure than have to maintain lots of java
environments.

Wolf

-- 
This Apt Has Super Cow Powers - http://sourcefreedom.com
Advancing Libraries Together - http://LYRASIS.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.ale.org/pipermail/ale/attachments/20120112/eba59f6f/attachment.html 


More information about the Ale mailing list