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

[alesj]

"david.lloyd at jboss.com" wrote : 
  | 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.  
  | 
A?
What's the point of frameworks then?

In my case all of the used libs were a perfect fit.
Dunno what kind of crap you use. ;-)

"david.lloyd at jboss.com" wrote : 
  | Many projects relied on VFS because it is written for a particular use case.  
  | 
What particular use case?

Current VFS does exactly what it was meant for or what you expect from vfs.
The API is simple and usable, features are pretty rich.

Where we might argue about impl details,
the overall goals were achieved:
* single point of controlling resources lookup
** handling file locking
** file vs. jar vs. dir abstraction
** visitor pattern
* extension points
** assembled
** in-memory
* ...

But well, now that I see your take on ext libs,
I'm no longer wondering why VFS3, vs. trying to fix existing impl.

"david.lloyd at jboss.com" wrote : 
  | However, it just happened to be completely wrong.  Now fixing it is a huge undertaking.
  | 
Wrong in what way?
Going back to AS4 behind an VFS api (aka VFS3) doesn't make it right. ;-)

"david.lloyd at jboss.com" wrote : 
  | Refactoring code is easy.  Refactoring semantics is really difficult (see VFS again).
  | 
Specially when you rename packages for no reason, right? ;-)

"david.lloyd at jboss.com" wrote : 
  | 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. 
  | 
Again, what kind of crap are you using?

I'm not saying you're completely wrong.
But in this case - as again my use-case proves it - 
I would never take that re-invented "reflection abstraction + resource lookup abstraction" over existing impls.

"david.lloyd at jboss.com" wrote : 
  | We're here to solve problems, not worship old ineffective solutions.
You don't sound convincing, specially with all the negative comments about ext code.
Looks like you're more into re-writing things than solving real problems.
The world is not perfect, the code is not perfect,
but at least the code is open sourced, hence you can fix it. ;-)


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

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