(March 14, 2015 at 7:40 pm)Cthulhu Dreaming Wrote: I do find some disagreement with your position on IOC, though. It's useful for injecting runtime dependencies at appserver startup, and failing early if a resource is not available, rather than at runtime.
Fair enough. I suppose a lot of it comes down to it being Java. The amount of Jar files and resources that need to be managed can be quite burdensome in Java compared to other languages. I suppose this is the nature of developing a system that can be written once and run everywhere. And then more so when you get into web development which essentially creates systems working across many different platforms (client, server, databases etc).
(March 14, 2015 at 7:40 pm)Cthulhu Dreaming Wrote: In addition, instantiating expensive singletons early is preferable in my view. From a performance standpoint, it's useful, but not a panacea.
I don't disagree. My experience seems to have been writing boiler plate XML (instead of boiler plate Java code) that hard codes values that never change. And now four years later I am working at another company taking out values hard coded in the XML and putting them back into the Java code.
Still, not as bad as finding that links between JSPs being stored in the database rather than code. The original developers thought that it would be nice to be able to configure the menus in the web portal. And of course it never actually got configured in practice.
C to Java & Spring? Did it make you feel dirty?
