Matt Raible ha scritto: > AppFuse 3 will consist of services and UI, as separate modules. Services > will be RESTful and will likely consist of Rails, Grails and Java (CXF > or Jersey). The UI options will be GWT and Flex. It's quite a departure > from previous versions, but I think SOFEA is here to stay and I'd like > AppFuse to be the kickstart for it.
I read your "letter to the appfuse users" as well (http://raibledesigns.com/rd/entry/a_letter_to_the_appfuse) and I was quite impressed by a couple of your statements. In your letter, you say: "I realize there's many full-stack frameworks that do the same thing as AppFuse with less code. Examples include Ruby on Rails, Grails, Seam, Spring Roo and the Play framework. However, there seems to be quite a few folks that continue to use AppFuse and it stills serves the community as a nice example of how to integrate frameworks. Furthermore, it helps me keep up with the latest framework releases, their quirks and issues that happen when you try to integrate them." And now, in this interview, you confirm that the next generation of AppFuse will be completely different from the existing one, based of SOA/SOFEA concepts and tools. It looks like you consider the current design of AppFuse as obsolete and deemed to give way to others, more modern, SOFEA-based, solutions. That sound as bad news for us: if even you, who are the creator of AppFuse, are convinced that RoR or Grails are the "right tools for the task", why anybody else should ever use AppFuse (or Tapestry or any other old-fashioned tool, for that matter) in a real-world project? Would not be much more sensible to use those best-of-the-breed tools (RoR or Grails) and forget about AppFuse since now? Even worse: what will happen to the guys that are using the current generation of AppFuse for real-world applications? Will they lose any support in the near future? All of these dubts sums up to a simple question: can we (end-users and programmers) be confident in the fact that the current generation of AppFuse will be developed and supported in the next two-four years? Should you get full-time busy on AppFuse 3.0, will someone else work on AppFuse 2.X? I apologize for raising such a sensitive questions but I'm starting a new project based on AppFuse 2.1 and I have to know how far is my technological horizon. CU PS: That said, let me say also that I completely agree with you on the fact that SOFEA is here to stay. The best thing that can happen to AppFuse is to adopt/integrate/support a few SOFEA concepts and tools, in a way or another. -- Alessandro Bottoni Website: http://www.alessandrobottoni.it/ "Things should be as simple as possible, but not simpler." -- Albert Einstein
<<attachment: alexbottoni.vcf>>
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net For additional commands, e-mail: users-h...@appfuse.dev.java.net
