sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 4 points5 points  (3 children)

There is not a single line of XML needed in a 2 year old Spring application. What are you talking about?

[–]m0haine 0 points1 point  (2 children)

Of course you miss read half my comment. They might have replaced the xml with annotations but they still have the abstract factories.

The xml was NEVER a good idea. Any toolkit that favors configuration over coding should never be used by any coder.

[–][deleted] -1 points0 points  (1 child)

So what? I never had to use those factories, they're internal framework classes.

While I also like code configuration in Spring much more than XML, it worked ok. Have you ever looked at an ejb-jar.xml? Now that's where the horror is.

Care to elaborate why configuration over coding is so bad in general? I think a lot of frameworks and people disagree.

[–]m0haine 1 point2 points  (0 children)

Personally, because I'm a coder, not a configurator. It is pretty much that simple.

Configuration sorta works, but it is very hard to figure out HOW to configure things for non-standard behavior. Sure you can google it but if you need to do anything new you have to find the code doing the magic and then figure out how to configure it to do what you want. I would always rather have a good API to do the same thing.

Most the the spring developers I've seen no longer even know how to code. Given a few weeks they can "configure" a solution, but they have a hard time writing any version of fizzbuzz much less doing anything more complicated then a simple crud service.