Interesting. Will check it out.
How is this different from the recently released Play framework. And can you give us more details as to why it should be used over SpringMVC or frameworks like Play?
How is this different from the recently released Play framework. And can you give us more details as to why it should be used over SpringMVC or frameworks like Play?
Working with Designers for so many years, I was trying to build something that a Designer can use in minutes and use it for publishing his work with the littlest effort possible; all these without writing a single line of Java code. I am sure Play/SpringMVC can do that too?!
For Micro, the separation of roles and concerns is adamant. Micro (like jpublish.org) is about helping the publishers taking their dynamic content to the web as easy as possible, while allowing the Developers to bring in as much business logic power as possible but without interfering with the content publishing concern; the true separation of roles and concerns. Please have a look at Micro's documentation web site: http://micro-docs.simplegames.ca/ (source on Github too); hosted at Heroku, it is a Micro web app and its entire content is written in Markdown. This is an example of what most of the web Designers and the small publishers will like to have, I think/hope?! Speaking about the Heroku, the compiled slug size, for a standard web app using Micro, is 11.7Mb. Micro is micro :)
Forking Play 1.2.x could be a solution (and maybe remove the python console. After all that's a java framework)
Or.
Or one may use the extensibility of Play 2.x to remove the scala parts javaists don't want. It shouldn't too hard.
Here's a thread on the official forum about it : https://groups.google.com/forum/?fromgroups=#!topic/play-fra...
Just a nitpick: Play was initially released in 2007, so I wouldn't call it a "recent" framework :-)
I believe a web Designer will be less intimidated by Micro.