A bunch of good things have already been said, so here's just some more quick comments from me.
I've used and studied a lot of web frameworks over many years. Weblocks is just the one toolbox that I happen to like best. Weblocks is not a continuation-based framework. You can program all your stuff using continuations, or none. What's more, most people seem to be confusing continuations (a general concept in programming) with actions (only in network programming; functions on the server side identified by a unique id. A kind of RPC.). I hardly use continuations. In this context it's interesting to see that Slava, the original author of Weblocks, heavily touted a continuation-based approach and now prefers other frameworks. Continuations have very specialized applications, but are confusing to new users and make debugging more complex because there's a lot of implicit state involved. I prefer explicit state, and so should newbies. Widgets, actions and the thin JS layer are the central concepts in Weblocks. Continuations and views are not. I cannot recommend using the current view system in new code. Thus, Slava's articles about Weblocks and what he thinks is so great about it are somewhat outdated. Documentation is spotty at best, so be prepared to ask questions and use the source. Be wary of people making blanket statements. Always evaluate yourself and try to judge how balanced someone else's view is. Leslie -- You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/weblocks?hl=en.
