Consider adding optimization

[wmertens]

In https://github.com/gradus/coffeecup/blob/master/src/compiler.coffee there's an implementation of how to walk the ([ck]offee|tea)[ck]up templates and optimize the function calls into plain HTML. Anything that's static is converted to strings and only the parameters remain, greatly improving the time needed to run the template.

This is useful when you're using client-side re-rendering, like React does.

(Incidentally, it's not a great leap from teacup to generating React.JS code)

[hurrymaplelad]

Thanks for the heads up! Do you have any numbers handy to motivate this sort of optimization?

On Feb 14, 2015, at 3:01 AM, Wout Mertens notifications@github.com wrote:

In https://github.com/gradus/coffeecup/blob/master/src/compiler.coffee there's an implementation of how to walk the ([ck]offee|tea)[ck]up templates and optimize the function calls into plain HTML. Anything that's static is converted to strings and only the parameters remain, greatly improving the time needed to run the template.

This is useful when you're using client-side re-rendering, like React does.

(Incidentally, it's not a great leap from teacup to generating React.JS code)

—
Reply to this email directly or view it on GitHub.

[wmertens]

@hurrymaplelad see
gradus/coffeecup@81bda8d,
the benchmark goes from 7.7s to 0.28s...

On Mon, Feb 16, 2015, 6:15 PM Adam Hull notifications@github.com wrote:

Thanks for the heads up! Do you have any numbers handy to motivate this
sort of optimization?

On Feb 14, 2015, at 3:01 AM, Wout Mertens notifications@github.com
wrote:

In https://github.com/gradus/coffeecup/blob/master/src/compiler.coffee
there's an implementation of how to walk the ([ck]offee|tea)[ck]up
templates and optimize the function calls into plain HTML. Anything that's
static is converted to strings and only the parameters remain, greatly
improving the time needed to run the template.

This is useful when you're using client-side re-rendering, like React
does.

(Incidentally, it's not a great leap from teacup to generating React.JS
code)

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#48 (comment).

[hurrymaplelad]

Roughly 7.5s / 100,000 elements, or 75ms for a typical 1000 element page.
Definitely seems worthwhile. PR welcome!

On Mon, Feb 16, 2015 at 10:47 AM, Wout Mertens notifications@github.com
wrote:

@hurrymaplelad see

gradus/coffeecup@81bda8d
,
the benchmark goes from 7.7s to 0.28s...

On Mon, Feb 16, 2015, 6:15 PM Adam Hull notifications@github.com wrote:

Thanks for the heads up! Do you have any numbers handy to motivate this
sort of optimization?

On Feb 14, 2015, at 3:01 AM, Wout Mertens notifications@github.com
wrote:

In https://github.com/gradus/coffeecup/blob/master/src/compiler.coffee
there's an implementation of how to walk the ([ck]offee|tea)[ck]up
templates and optimize the function calls into plain HTML. Anything
that's
static is converted to strings and only the parameters remain, greatly
improving the time needed to run the template.

This is useful when you're using client-side re-rendering, like React
does.

(Incidentally, it's not a great leap from teacup to generating React.JS
code)

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#48 (comment).

—
Reply to this email directly or view it on GitHub
#48 (comment).