On Jan 17, 2008 12:24 PM, David Mitchell <[EMAIL PROTECTED]> wrote: > > My 2c... > > One of the biggest attractions of ErlyWeb to me (and I suspect many > others) is that it gives a RAD environment, is MVC-based and ***runs > fast***. > > I know from my Zope days that introducing TAL (a tag mechanism for > views that was specifically designed to be friendly to both developers > and designers) in place of DTML (an ASP-like tag mechanism that was > ugly for designers) resulted in a fairly massive slowdown of Zope > apps. I can definitely see the attraction of making ErlyWeb tags more > designer-friendly, but I think that if it involves slowing down > ErlyWeb performance by any measurable amount, it probably should be > avoided.
Adding custom tags won't slow ErlTL down. Those tags would be compiled to Erlang beam code just like existing Erlang expressions in ErlTL templates. It's just syntactic suger, nothing more. > > Let's face it: if it wasn't for the speed of ErlyWeb, we may as well > use Rails. Both can scale by adding hardware, but it's the speed of > ErlyWeb that makes it shine. > > Any thoughts??? I think there many reasons to pick ErlyWeb over Rails besides speed: - Concurrency. There are many ways you can use concurrency in your webapp both to enable new features (e.g. comet, which you have to be insane to try with Rails) and to improve existing ones (do things in parallel or in the background to improve page load times). I think the area of concurrency in webapps is relatively unexplored because most web developers use languages that make using concurrency too hard/impractical/unscalable. With ErlyWeb you have a green field of exploration in front of you. (Here's something I ran into recently: in a Facebook app, instead of updating user's profile FBML or feed or sending notification in the same flow as the controller action, you can spawn those actions into different processes to get faster perceived response time. It's pretty cool I think. Don't try it with Rails.) - Elegance. ErlyWeb has a much nicer component system than Rails' soup of partials/layouts/components. Erlang code is also more readable than Rails code IMHO due to immutable variables and generally side-effects free programming. Plus, functional programming really is nicer than imperative/OO programming. It's admittedly subjective, but I've used plenty of imperative languages and I just like the functional style more. (Erlang can admittedly be awkward sometimes, but the benefits outweigh the awkwardness.) - Pushing the boundaries. Rails is only good for CRUD apps. With ErlyWeb, you can build CRUD apps just as easily as in Rails, but you can also build a backend that rivals Amazon/Ericsson/Yahoo/Google scale systems. Rails narrows your imagination -- ErlyWeb expands it. - Reliability. Compare Twitter to an Ericcson phone switch or Amazon SQS. - Community. Just ask Zed http://www.zedshaw.com/rants/rails_is_a_ghetto.html :) Yariv --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "erlyweb" 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/erlyweb?hl=en -~----------~----~----~----~------~----~------~--~---
