The reason that AppFuse developer has stalled is mainly because I haven't had (or made) the time to work on it. I often have it on my "todo" list, but it drops to the bottom often because of more important things. When it was under active development, I used to spend 20-30 hours a week working on it and while this was great for the community, it wasn't good for me personally.
I do plan on making a sincere effort to releasing AppFuse 2.1 this quarter and 3.0 next year, but I also said I'd get 2.1 out this summer and that never happened. As far as AppFuse vs. Grails, you might checkout the following blog post on this subject. http://raibledesigns.com/rd/entry/appfuse_vs_grails_vs_rails Hope this helps, Matt On Thu, Oct 15, 2009 at 2:38 AM, Gary White <gdw...@yahoo.com> wrote: > I unfortunately have been out of full-time development for a couple of > years. I am now leading a big high profile project that is finally reaching > a phase which involves significant software development and I'm really > stoked about getting back to what I love doing. In my previous stint doing > full-time development, I chose AppFuse as the framework (v1.8-1.9 I think > w/Spring MVC/Hibernate) and I was a big fan (thank you Matt). I'm now in the > position again of choosing a framework and, of course, AppFuse is on my > short list. I was somewhat surprised/concerned to see the lack of recent > activity (based upon some very quick browsing on my part) so I wanted to > touch base to get some idea of where the project stands, where it's going > and its long-term viability for the type of project described above. I'm > also curious as to the reason(s) for the seeming lack of activity/progress > (e.g. lack of committors, lack of or declining interest in the user > community, overtaken by other frameworks/solutions etc.). Also, please feel > free to severely chastise me (OK not really) if I've mischaracterized the > current state of AppFuse. My first cut at the framework short list actually > only has 2 contenders, each representing a general approach. One was Grails, > which represents a very productive approach that hides some of the > complexities of the underlying frameworks but also makes them available in > case you need a bit more flexibility (pros) but with the possible downside > of more overhead/lower performance/less scalability etc. The other option is > of course AppFuse, which exposes all of the raw power/performance of Java > and the underlying frameworks but is somewhat less productive and requires a > higher skill level than Grails. Would anyone like to comment on the above > synopsis and perhaps fill in some of the blanks left by my absence from > development as to what attractive options are available? I would greatly > appreciate any input, including pointers to other sites where I can do my > own research on the pros/cons of these and other options. Regardless, I like > to again express my appreciation to Matt (and any other committors) for the > contributions you've made and I hope all is well with you. Thanks, Gary P.S. > I saw somewhere (maybe it was the 2009 Summer of Code blurb) a couple of > requests for incorporating Groovy & GORM. Is that on anyone's radar at all? > ________________________________ > View this message in context: AppFuse project status? > Sent from the AppFuse - User mailing list archive at Nabble.com. > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net For additional commands, e-mail: users-h...@appfuse.dev.java.net
