[jboss-dev-forums] [JBoss Microcontainer Development POJO Server] - Re: integration with the Papaki annotation indexer/repositor

david.lloyd@jboss.com do-not-reply at jboss.com
Tue Oct 20 11:24:41 EDT 2009


"alesj" wrote : "david.lloyd at jboss.com" wrote : So - we are taking a small project, adding dependencies and making it more complex?
  |   | 
  | Why is adding dependecies making it more complex?
  | It's exactly the opposite - less code to maintain.
  | 

Wrong.  Because you end up contorting your code to match the use-case of the dependency, rather than the use case you're trying to achieve, causing ineffective code to become further entrenched, and making it even harder to fix later.  VFS being one great example.  Many projects relied on VFS because it is written for a particular use case.  However, it just happened to be completely wrong.  Now fixing it is a huge undertaking.

"alesj" wrote : "david.lloyd at jboss.com" wrote : 
  |   | Adding dependencies is a bad idea.  Projects should as a rule have the minimum number of runtime dependencies possible.  Having lots of dependencies just makes it harder to refactor later.  If you have a large web of dependencies between a set of projects, that's a big indicator that they ought to be one big project anyway, or at least split up differently.
  |   | 
  | Again nonsense.
  | Refactoring is extremely easy if you have an external thing that does things for you.
  | 

Refactoring code is easy.  Refactoring semantics is really difficult (see VFS again).

"alesj" wrote : In most cases those ext libs have stand the test of time,
  | so they are much better then the crap you quickly code yourself.
  | And the nicest things about all the pieces in my version of Papaki is that we control them all,
  | meaning it's easy to create any missing feature or fix/extend an existing one.
  | 

Standing the test of time is no test at all!  What kind of argument is that.  Just because someone didn't rewrite something for 4 years doesn't mean it's not crap.  And there are many coders here whose "quickly coded crap" I would take over any multi-year-old library in a heartbeat.  We're here to solve problems, not worship old ineffective solutions.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261304#4261304

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261304



More information about the jboss-dev-forums mailing list