Re: TC39 vs the community

2014-06-26 Thread Garrett Smith
Nice. I wonder what Horse would think of Vermin Supreme's pony identification program. But in all seriousness, Google, MSFT, are all pushing for IoT or wearables by putting on events featuring that, creating a buzz, and making press on the event. On 6/23/14, Brendan Eich bren...@mozilla.org

Re: TC39 vs the community

2014-06-26 Thread Jasper St. Pierre
On Thu, Jun 26, 2014 at 2:41 AM, Garrett Smith dhtmlkitc...@gmail.com wrote: Nice. I wonder what Horse would think of Vermin Supreme's pony identification program. But in all seriousness, Google, MSFT, are all pushing for IoT or wearables by putting on events featuring that, creating a

Re: TC39 vs the community

2014-06-24 Thread Garrett Smith
On 6/23/14, joe joe...@gmail.com wrote: And here I thought you were making an educated argument with your explanation of the history of propaganda and public relations. When I first read corporate propaganda, I thought you mean the propaganda of JS developers, not commercial corporations.

Re: TC39 vs the community

2014-06-23 Thread joe
And here I thought you were making an educated argument with your explanation of the history of propaganda and public relations. When I first read corporate propaganda, I thought you mean the propaganda of JS developers, not commercial corporations. Frankly, I find the idea that commercial

Re: TC39 vs the community

2014-06-23 Thread Brendan Eich
+1 But Garrett's post was helpful in its own way. @horse_esdiscuss agrees! /be joe wrote: And here I thought you were making an educated argument with your explanation of the history of propaganda and public relations. When I first read corporate propaganda, I thought you mean the

Re: TC39 vs the community

2014-06-22 Thread Garrett Smith
On 6/20/14, David Bruant bruan...@gmail.com wrote: Hi, I'm not quite sure what this is all about, so forking in hope for clarifications. I'm sorry to send a message that will probably be read as noise by a lot of people, but I'm also tired of some of these pointless and unconstructive, if

TC39 vs the community

2014-06-20 Thread David Bruant
Hi, I'm not quite sure what this is all about, so forking in hope for clarifications. I'm sorry to send a message that will probably be read as noise by a lot of people, but I'm also tired of some of these pointless and unconstructive, if not destructive, fights among people (in here, on

RE: TC39 vs the community

2014-06-20 Thread Domenic Denicola
Can you develop these particular accusations? Why would TC39 have priorities that don't align with the needs of developers? especially on modules which are clearly one of the most awaited feature as far as developers are concerned? TC39 has a lot of constituents who use their experience

Re: TC39 vs the community

2014-06-20 Thread John Barton
On Fri, Jun 20, 2014 at 6:42 AM, Domenic Denicola dome...@domenicdenicola.com wrote: Can you develop these particular accusations? Why would TC39 have priorities that don't align with the needs of developers? especially on modules which are clearly one of the most awaited feature as far as

Re: TC39 vs the community

2014-06-20 Thread Jeremy Martin
I'll make this point as concisely as possible, since this conversation is quite given to noise: While others may disagree, I feel the source of contention/disunity on modules is more fundamental than syntax or who's (not) listening to who. Specifically, ES6 modules are far less immune to

Re: TC39 vs the community

2014-06-20 Thread C. Scott Ananian
On Jun 20, 2014 11:39 AM, John Barton johnjbar...@google.com wrote: I started out with a similar opinion. Then I wrote some ES6 code. What we need now is experience from using ES6-modules. We have plenty of decent implementations. We've built nodejs and browser applications based on ES6

Re: TC39 vs the community

2014-06-20 Thread Jasper St. Pierre
On Fri, Jun 20, 2014 at 11:39 AM, John Barton johnjbar...@google.com wrote: I started out with a similar opinion. Then I wrote some ES6 code. What we need now is experience from using ES6-modules. We have plenty of decent implementations. We've built nodejs and browser applications based on

Re: TC39 vs the community

2014-06-20 Thread Axel Rauschmayer
A minimal, pragmatic and well integrated solution is the ES6 Module Transpiler: https://github.com/square/es6-module-transpiler Additionally, Addy Osmani maintains a comprehensive list of tools: https://github.com/addyosmani/es6-tools Axel On Jun 20, 2014, at 19:54 , Jasper St. Pierre

Re: TC39 vs the community

2014-06-20 Thread Andrea Giammarchi
I am trying to stay outside this discussion as much as I can but there is a specific sentence that I'd like to understand: On Fri, Jun 20, 2014 at 8:39 AM, John Barton johnjbar...@google.com wrote: The ES5-module using community tried, valiantly, to reach a compromise module solution. They

Re: TC39 vs the community

2014-06-20 Thread John Barton
On Fri, Jun 20, 2014 at 2:03 PM, Andrea Giammarchi andrea.giammar...@gmail.com wrote: I am trying to stay outside this discussion as much as I can but there is a specific sentence that I'd like to understand: On Fri, Jun 20, 2014 at 8:39 AM, John Barton johnjbar...@google.com wrote: The

Re: TC39 vs the community

2014-06-20 Thread Andrea Giammarchi
I think tools made `require` the winning choice but about having both I am not sure I've read about dynamic folder such: `import _ from loDashFolder` if that's a thing then ``` var require = function (fromWhere) { return import _ from loDashFolder }; ``` or whatever will be Best Regards

Re: TC39 vs the community

2014-06-20 Thread Andrea Giammarchi
typo ... ``` var require = function (fromWhere) { return import * from fromWhere }; ``` or something similar On Fri, Jun 20, 2014 at 3:14 PM, Andrea Giammarchi andrea.giammar...@gmail.com wrote: I think tools made `require` the winning choice but about having both I am not sure I've

Re: TC39 vs the community

2014-06-20 Thread Juan Ignacio Dopazo
On Friday, June 20, 2014 7:15 PM, Andrea Giammarchi andrea.giammar...@gmail.com wrote: typo ... ``` var require = function (fromWhere) {   return  import * from fromWhere }; ``` That's not valid ES6. It's specified that: - Import and export statements can only be top level statements -