On Wed, Oct 12, 2011 at 8:32 AM, Allen Wirfs-Brock <al...@wirfs-brock.com>wrote:
> > On Oct 12, 2011, at 6:53 AM, Joe Developer wrote: > > > I think an important question here is: > Who are you actually trying to serve with your changes? > > > See the actual goals requirements and goals for ES Harmony at > http://wiki.ecmascript.org/doku.php?id=harmony:harmony > > Requirements > > 1. New features require concrete demonstrations. > 2. Keep the language pleasant for casual developers. > > This is a great response. All I was trying to say with the shorthand 'GrawlixScript' is that some of the concrete demonstrations fail the second test. Of course requirements and goals conflict, I was just trying to put a voice in on the side of #2. jjb > > 1. > 2. Preserve the “start small and iteratively prototype” nature of the > language. > > Goals > > 1. Be a better language for writing: > 1. complex applications; > 2. libraries (possibly including the DOM) shared by those > applications; > 3. code generators targeting the new edition. > 2. Switch to a testable specification, ideally a definitional > interpreter hosted mostly in ES5. > 3. Improve interoperation, adopting *de facto* standards where > possible. > 4. Keep versioning as simple and linear as possible. > 5. Support a statically verifiable, object-capability secure subset. > > > _______________________________________________ > es-discuss mailing list > es-discuss@mozilla.org > https://mail.mozilla.org/listinfo/es-discuss > >
_______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
