@domenic @jaffathecake I feel you have discovered something new, and feel it has been wrongly used. But it’s actually quite pleasant
-
-
Replying to @stefanpenner
@stefanpenner@domenic it doesn't feel new, it feels old pointlessly dressed as new (see my getter comparison)1 reply 0 retweets 2 likes -
Replying to @jaffathecake
@jaffathecake@stefanpenner Yes. fn("css"), fn(`css`), fn('css') should all work. Saying "you must use fn`css`" is ridiculous.1 reply 0 retweets 3 likes -
Replying to @domenic
@jaffathecake@stefanpenner A tagged template string f`x` whose output is some function applied to `x` is a sign of abusing tags.1 reply 0 retweets 5 likes -
Replying to @domenic
@jaffathecake@stefanpenner The point of template string *TAGS* is to process the arguments piece-wise. If not doing that, just use a fn.1 reply 0 retweets 5 likes -
Replying to @domenic
@domenic@jaffathecake our hope is that tagged template strings. Will be a good way to also hint to editors for syntax/autocomplete etc2 replies 0 retweets 0 likes -
Replying to @stefanpenner
@stefanpenner@jaffathecake Why? They're just function calls. Editors should accept html('...') just as much as html(`...`).3 replies 0 retweets 1 like -
Replying to @domenic
@domenic@stefanpenner or even /**@highlight hbs */"etc etc"1 reply 0 retweets 0 likes -
Replying to @jaffathecake
@jaffathecake@domenic@stefanpenner your opinion is that /**@highlight hbs */`etc etc` (newlines need backticks) is superior to hbs`...`?1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@domenic@stefanpenner if it's a hint to the editor, something that doesn't impact runtime sounds better, yes.1 reply 0 retweets 0 likes
@jaffathecake @domenic @stefanpenner let's revisit this in a few months. It's clear that Twitter has gotten the best of this convo.
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.