- From: Marcos Caceres <marcos@marcosc.com>
- Date: Thu, 3 Jan 2013 11:56:25 +0000
- To: Marcos Caceres <w3c@marcosc.com>
- Cc: Brian Kardell <bkardell@gmail.com>, François REMY <francois.remy.dev@outlook.com>, "public-nextweb@w3.org" <public-nextweb@w3.org>
Anyway, before we start criticizing the output too much, etc. Lets just get started!
Step 1, someone please create the project on Github :)
https://github.com/extensibleweb
We can do some experimentation with typescript as we go and see if it fits well. But the important thing is just getting the Web IDL algorithms written.
--
Marcos Caceres
On Thursday, January 3, 2013 at 11:45 AM, Marcos Caceres wrote:
>
>
>
> On Thursday, January 3, 2013 at 11:34 AM, Brian Kardell wrote:
>
> > I am not an incredible fan of the idea of using typescript here, but I suppose I could get over it since the output should be valid vanilla js...
> Some minor problems I see from looking at the examples are things like
>
> class Foo{
> someFunction(){ … }
> }
>
> become:
>
> var Foo = (function(){
> this.prototype.someFunction = function(){...}
> }();
>
> IMHO, that seems kinda wrong to me? Every time the constructor is called the prototypes are rewritten?
>
> > More importantly though: I think we should focus on evergreen browsers... any attempt to do more I think is way harder, bad and inevitably involves polyfills and shims - even worse it propigates the problem by not providing incentives to get one. There is simply no rationale for not having one at this point - we should be encouraging the _next web_.
> Right.
Received on Thursday, 3 January 2013 11:56:54 UTC