The Java dilemma
May 9th, 2005
What would you prefer: to re-invent the wheel, or to add a "dependency" to your project? My choice is easily made...
Hint: I like code that is tested by more than one person.
About me
10to1, my company
del.icio.us
My tumblr
April 21st, 2008 at 10:18 PM Hmpf, testing or not, I've seen Apache code, which would have needed more testing. Why not using a clean reinvented wheel. And then "one dependancy"? Usually when you add one Apache jar you have to add a handful of other ones and then the versions collide with the version required of another third and forth party component, and ...
April 21st, 2008 at 10:18 PM Aha, ik zie dat ge ook de newsletter uit .za leest ;-)
April 21st, 2008 at 10:18 PM Ik dacht dat het van Erik Thauvin kwam, maar ik kan mij vergissen...
April 21st, 2008 at 10:18 PM How do you think about this bug? http://mail-archives.apache.org/mod_mbox/jakarta-commons-user/200503.mbox/%3c2B64219028BBFF48B3CC957EF10B58FE6C8EDF@ns1018.SSSI.seagull.nl%3e But even apache util contain bugs, I think it still more preferable than own implementation, as we should spend the programmer time more on business logic of the product rather than utilities or system level service. We can just search for another util package also.