[doktrin]

Very interesting. I've been playing around with Spark a little as of recently (Sinatra inspired minimalistic Java web framework). I think Mu may allow for some out-of-the-box functionality that Spark lacks.

At the end of the day, though, I'd be happy working in a Java framework wherein the experience didn't feel like I was forcing myself to write Java code. It's just such an uphill battle when the dev experience of (rails/node/django/webapp/web.py) is radically different from just about everything Java has to offer. The lack of a sane package manager, for one, is a major downer.

[florinpatrascu]

Further more, to a comment I made earlier: http://news.ycombinator.com/item?id=5196565 and regarding the package managers.

As a Ruby developer, my first impulse was to use Rake but I started with Maven, trying to follow the bigger players, and I found myself struggling with managing various Maven dependencies and settings instead of focusing on getting the things done. Then I switched to Ant when I discovered the difference it makes when deploying to Heroku. Mu's compiled slug size deployed with Maven was 57Mb while the same core deployed with Ant today is 11.7Mb, give or take.

I'll commit the Maven configuration files soon, it is not my intention not too, but I will still search for a better solution. Any suggestions? Thank you for your feedback!

[eropple]

You may not like it, and it has its warts, but I have trouble not calling Maven "sane".

[doktrin]

Perhaps I'm judging it according to an unfair standard, and I certainly don't have the intention of getting into a language war. However, I personally view Maven (including but not limited to its config files) as quite insane.

When compared to, for instance, NPM or Ruby Gems, I can't honestly say I've found much to like about the Java ecosystem. Part of the problem, of course, is that unlike in the case of the aforementioned two, build & dependency management in Java-land is quite fragmented (ant, maven, gradle, etc.).