Spring Madness – .NET Calling
Today was one of those days when you regret ever venturing down the Java road due to the madness imposed on development from the infrastructure teams within an investment bank. Setting up my development environment with Eclipse, source control and Tomcat was a painful and brain numbing experience. At least by day end I had hopefully contributed to the bloat of Spring configuration. Tomorrow I’m hoping a colleague will show me the secret to getting IntelliJ setup with Tomcat – ever since I used IntelliJ at a recently merged European investment bank I’ve found it increasingly hard to return to Eclipse.
One thing that is clear from today is that C# is in my view a nicer language given the 3.0 feature set – LINQ etc.
If Spring config is getting out of hand, you are miss-using it!
Spring assembly can be done using Groovy if you prefer reading code and not xml.
With .Net your app will be missing out on operating systems like Solaris with unique features like ZFS and DTrace …