W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2013

Re: E4H and constructing DOMs

From: Ian Hickson <ian@hixie.ch>
Date: Thu, 7 Mar 2013 17:47:14 +0000 (UTC)
To: Rick Waldron <waldron.rick@gmail.com>
cc: Ojan Vafai <ojan@chromium.org>, Adam Barth <abarth@chromium.org>, "rafaelw@chromium.org" <rafaelw@chromium.org>, Adam Klein <adamk@chromium.org>, Anne van Kesteren <annevk@annevk.nl>, Alex Russell <slightlyoff@chromium.org>, "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-ID: <Pine.LNX.4.64.1303071744190.15713@ps20323.dreamhostps.com>
On Thu, 7 Mar 2013, Rick Waldron wrote:
> E4H is a language level syntax extension that appears to duplicate the 
> functionality provided by Template Strings, while restricting usage to a 
> web/DOM-centric concept (CORS same-origin or Worker context)—effectively 
> creating a "version". It also uses one of the remaining unambiguous 
> ascii characters "@". Granted, it's an interesting experiment, but 
> Template Strings are capable of "all this and more".

To be fair, unless they've changed quite substantially since the last time 
I saw them, quasis don't do the one thing that is E4H's whole point, 
namely compile-time syntax checking.

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 7 March 2013 17:47:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:08 UTC