On Tue, Sep 28, 2010 at 10:08 PM, Bill Wohler <[email protected]> wrote:
> I programmed in C for 15 years, skipped C++, and have been programming > in Java for nearly 15 years. > > There are the myriads of libraries in Java that keeps you from > rebuilding the wheel. > > But the main productivity drain that you have in C and likely C++ is > the time spent debugging. It seemed that I spent 75% of my time > debugging C, mostly chasing down errant pointers and memory leaks. In > contrast, it feels like I hardly debug that much any more. While this > is anecdotal, and my habits have certainly improved (like using TDD, > and writing tests at all for that matter), I think that less time > debugging is certainly a universal win for Java. > > I think google is perhaps an errant data point here. They have myriads of libraries internally and debugging is not too difficult. Plus the style required to write production google code helps reduce the likelihood of memory leaks. I would think that your experience is probably the norm. I remember earlier in my career debugging C++ static initialization mysteries that wound up with my re-writing a huge portion of code and still not understanding what was going on (until much later in my career). -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
