Thanks for everyone who came to the meeting; the discussion was a lot
of fun.
I'd mentioned I'd post some links to Joist on the list:
* Joist, the Java ORM for Me [1] is the blog post that I used as talking
points for the OJUG presentation. It covers the "why" of Joist's
implementation decisions.
* joist.ws [2] has some basic docs and a screencast of the workflow,
which is basically what I did at OJUG as well.
* And all the source code is on github [3], also with joist-util,
which has the sourcegen package that Joist uses to do no-templates,
sane code generation.
Also, someone had mentioned that Joist's non-EJB, non-Spring, non-JTA
approach means you can't exactly sneak it in unnoticed into your
enterprise environments. Which is true.
But Joist is different for a reason. I think a lot of Java devs are
tired of the typical enterprise complexity; witness the exodus of Java
devs to Rails, Ruby, JavaScript, etc. Ironically, I generally agree
with their sentiment, I just think Java-the-language itself isn't the
whole problem, and that you can still accomplish productive things in
Java with a simple tool set. Which is what Joist, in some small way,
tries to do.
Closures would be really freaking nice though (go Scala).
Anyway, </soapbox>.
- Stephen
[1]: http://draconianoverlord.com/2012/03/21/joist-orm.html
[2]: http://joist.ws/
[3]: https://github.com/stephenh/joist