@domenic @stefanpenner @jaffathecake it compiles the template, ahead of time if possible.
-
-
Replying to @wycats
@wycats@stefanpenner@jaffathecake can you just compile normal strings, without component-wise processing? Then use a string-taking func.2 replies 0 retweets 0 likes -
Replying to @domenic
@wycats@stefanpenner As@jaffathecake said, the impulse "I have a function with a single string argument! Let's use tagged templates!" >1 reply 0 retweets 1 like -
Replying to @domenic
@wycats@stefanpenner@jaffathecake > is similar to the "I have a method that takes no arguments! Let's use a getter!" misguided path.1 reply 0 retweets 0 likes -
Replying to @domenic
@wycats@stefanpenner@jaffathecake The "logic" in both cases is very similar, e.g. "easier to scan" and so on.1 reply 0 retweets 0 likes -
Replying to @domenic
@domenic@stefanpenner@jaffathecake I think I'm just missing what you believe is the platonic essence of template literals.2 replies 0 retweets 0 likes -
Replying to @wycats
@domenic@stefanpenner@jaffathecake getters are also "feel like properties, memoize if appropriate".1 reply 0 retweets 0 likes -
Replying to @wycats
@domenic@stefanpenner@jaffathecake and "I commit to continuing to make them feel like properties"1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@stefanpenner@jaffathecake Yes. And *TAGGED* template literals are "I intend to process every interpolated value piecewise."1 reply 0 retweets 0 likes -
Replying to @domenic
@wycats@stefanpenner@jaffathecake plus "This is not a normal template literal. Every time you see ${} something special is happening."1 reply 0 retweets 1 like
@domenic @stefanpenner @jaffathecake "no interpolation allowed" is a valid processing and an improvement over hbs(`...`)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.