<br><br><div class="gmail_quote">On Thu, Jan 12, 2012 at 8:49 PM, Steve Brown <span dir="ltr"><<a href="mailto:scbrown3@gmail.com">scbrown3@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote"><div class="im">On Thu, Jan 12, 2012 at 4:10 PM, JD <span dir="ltr"><<a href="mailto:jdp@algoloma.com" target="_blank">jdp@algoloma.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div><br></div></div>
* Eats RAM (much more that a C++ program would use)<br>
* Slow during runtime (old link <a href="http://sprout.stanford.edu/uli/java_cpp.html" target="_blank">http://sprout.stanford.edu/uli/java_cpp.html</a> )<br>
* Garbage collection runs at the wrong time<br>
* Extremely slow desktop program startup<br>
* Ugly GUI controls - opinion<br>
* Eclipse requires 16GB and a Core i7 to be usable; it is slow on a Core i5.<br>
* Java devs actually believe they don't need to understand the platform they are<br>
running on. I have stories of developers claiming that rewriting a C app running<br>
on Intel CPUs in Java running on a SPARC CPU would result in greater<br>
performance. Complete BS, except that their C app was total crap to start.<br></blockquote><div><br></div></div><div>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. </div>
<br></div></blockquote></div>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. <br>
<br>Wolf<br clear="all"><br>-- <br>This Apt Has Super Cow Powers - <a href="http://sourcefreedom.com" target="_blank">http://sourcefreedom.com</a><br>Advancing Libraries Together - <a href="http://LYRASIS.org" target="_blank">http://LYRASIS.org</a><br>
<br>