The problems Wicket tries to solve (I've coded with Jon Locke who created Wicket on and off since we were in high-school, and was around for its creation) are really - Transparent management of server-side session state using Java serialization - Providing an abstraction for per-page and per-component data models - Providing a component model that allowed markup-generating "component"s to be delivered as JAR files
There's an assumption behind those problems which doesn't really hold up today: That you're generating HTML on the server-side, and that the server is where most work happens. I'm sure I'm not telling you anything you don't know, but browsers have gotten a lot more powerful since 2004/5 when Wicket was created. A lot of the stuff that used to only be possible on the server is routinely done on the client now. And Javascript client libraries have smoothed out most of the cross-browser hell that doing that sort of thing used to be. So I wouldn't expect there to be something terribly wicket-like for Node simply because nobody has quite the set of problems Wicket was designed to solve. For massive scale, generating markup on the server doesn't work out that well, and neither does server-side state; if you can do more work on the client, you get to make the server side dirt-simple (or at least only as complex as the actual problem it needs to solve); making simpler things scale is easier. You're on the right track with angular - that's the closest you're going to get (or, opinionatedly, the closest you ought to want to get) to Wicket's model for how things work, and is one of the saner client-side frameworks out there. Wicket was a fantastic framework in its day, especially compared with JSF and all of the XML madness that was going on in the early 2000's. While there is sort of room in the world for some sort of "component model" that would let "component"s generate JSON and inject it the way Wicket components did for HTML, in practice HTTP and URL paths and reverse proxies pretty much fill that need. Or, as I put it when I'm feeling uncharitable about my former employer (Sun), while Java was making things scale up to the size of all the employees of a big company, the rest of the world was making things scale out to the size of the planet. HTH, Tim -- http://timboudreau.com -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
