3 ms·
Meh... not too impressive. Parallel Rendering: why is this a big deal? Wiring is what ASP.NET has been doing for ages. I don't see the Wizard being more than a
by jcromartie 16y ago
Meh... not too impressive. Parallel Rendering: why is this a big deal? Wiring is what ASP.NET has been doing for ages. I don't see the Wizard being more than a few lines of Clojure, and Seaside just completely blows it away.
- arethuza 16y ago"Wiring is what ASP.NET has been doing for ages" - which is pretty much why I thought it looked horrible! [NB I rather like ASP.Net MVC but I use StringTemplate rather than ASPX pages for views].
- aaronblohowiak 16y agoParallel rendering matters because it increases page load speed. Let's say you have a page with 10 components that take an average of 100 ms to serve (including calls to db/soa, controller and view.) If loaded sequentially, your page will take 1 second. If loaded in parallel, it will only take 100ms (+ a little overhead.) You might think: "oh, but this is just rendering, but most of the time is in the models/db/soa". You'd be right in other frameworks. Lift is view-first, so it will figure out what components it needs to serve up based on the view and then parallelize all of the computation required to fulfill them.