I think it's a very nicely designed minimal framework, and I think it's great that it has a focus on failing as early as possible. I'm considering using it for a site that is halfway the transition of going from Struts 2 to mostly Ajax (extjs). That site currently uses JSPs for templating, which should be pretty minimal since Ajax takes over after the first render, but unfortunately isn't. Sitebricks would be a great replacement for those JSPs, especially because we're also refactoring that site to use Guice for DI (which totally rocks btw).
As for yet-another-framework-vs-framework discussion... I would just use it for different purposes. Wicket is great for complex projects that aren't Ajax-mostly, where you want to create many abstractions and reusable components, etc. I would consider (do consider in fact) Sitebricks when you go all ajax-y, e.g. together with YUI or ExtJs directly. It would compete with GWT in that case, since I haven't made up my mind whether I like that approach (great tooling support, static typing and being able to have programmers of various levels of competence working on it), or whether I prefer the approach to use something like Sitebricks and/ or JAX-RS with a good JS/ Ajax lib directly (small, elegant, flexible and no magic to fight, but needs disciplined coders and project standards to avoid ending up in maintenance hell). In my experience, It'll be hard to beat Wicket's productivity though. :-) Eelco On Sat, Sep 26, 2009 at 2:20 PM, Objelean Alex <[email protected]> wrote: > It seems that google created a yet-another-web-framework (as it used to be > called). It is called google-sitebricks. Below is a link on infoq. > http://www.infoq.com/news/2009/09/google-sitebricks > What do you think about it? > > Regards, > Alex Objelean > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
