|
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 |
From: Jan Koprowski <jan.koprow...@gmail.com>
Date: Fri, 26 Jun 2009 23:01:52 -0700 (PDT)
Local: Sat, Jun 27 2009 2:01 am
Subject: Re: Translate HAML on client side
On 27 Cze, 07:38, Nathan Weizenbaum <nex...@gmail.com> wrote:
> It's almost definitely going to be faster to do it on the server. Not only
In the face of HTML 5 cache ability this probably wasn't a problem.
> are many servers going to have more computing power to devote to the task > than your average browser (and remember, in-browser Javascript runs slowly, > although it's getting faster), but Haml is much, much slower when it needs > to be parsed. On the server, Haml templates are cached; they only need to be > parsed and evaled once, and from then on it's no more expensive than calling > a Ruby function. Client-side, though, every browser would need to parse the > Haml every time it loads a page. Entirely HAML is better for whole Internet because HAML notice is the most brief notice i have ever seen. On the other hand client side HAML implementation could support caching interior. > Not to mention that a significant portion of what makes Haml nice is its
As I say: i look HAML notation as brief and legible at the same time.
> templating facilities - it allows you to embed Ruby code in a nice way. That > wouldn't work at all, and you'd probably need an additional templating > language just to insert server values into the templates. From this point of view HAML could drastically decrease data transfer between browser and web server. I don't know statically how much HAML is smaller then full XHTML site source but i think this is enough to think about sending HAML to web browser instead (X)HTML or anything else. This is cool and innovative technology :] and deserve for publicity.
Greetings from Poland !
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| |||||||||||||