On Fri, May 16, 2014 at 10:18 PM, C. Scott Ananian ecmascr...@cscott.netwrote:
On Fri, May 16, 2014 at 12:49 PM, Mameri, Fred (HBO)
fred.mam...@hbo.comwrote:
maintaining performance and debuggability would be nice. But for me,
the main benefit of the bytecode is having my engineering team
On Mon, May 19, 2014 at 3:32 PM, Florian Bösch pya...@gmail.com wrote
Far as I see it, the discussion isn't really about bytecode. It's about
that you can't quickly/easily tack onto JS everything that's required to
make it a good virtual machine you can target from another language. asm.js
is
Well, if you're simply going to come up with a bytecode to match JS, then
you're gonna have the same kinds of issues that typescript, asm.js, dart,
etc. have to target it as a compile target. So if you want to make a VM
that's a good compile target, ye're gonna have to eventually discuss what
that
On Mon, May 19, 2014 at 3:46 PM, Florian Bösch pya...@gmail.com wrote:
Well, if you're simply going to come up with a bytecode to match JS, then
you're gonna have the same kinds of issues that typescript, asm.js, dart,
etc. have to target it as a compile target. So if you want to make a VM
So just so I get this straight. You're talking about a bytecode format,
which implies some kind of revamped features/VM to run it, but you won't be
discussing anything other than ECMAScript as the targeting semantic. Sorry
to say, but then that's a pretty useless discussion entirely.
On Mon, May
On Mon, May 19, 2014 at 3:55 PM, Florian Bösch pya...@gmail.com wrote:
So just so I get this straight. You're talking about a bytecode format,
which implies some kind of revamped features/VM to run it, but you won't be
discussing anything other than ECMAScript as the targeting semantic. Sorry
Well, it is a thread on bytecode, that had a discussion on bytecode, but
sure, whatever.
On Mon, May 19, 2014 at 4:07 PM, Till Schneidereit
t...@tillschneidereit.net wrote:
On Mon, May 19, 2014 at 3:55 PM, Florian Bösch pya...@gmail.com wrote:
So just so I get this straight. You're talking
I take a more expansive view, because of evolution. JS and languages
that currently target it, and also languages that might in the future
target it, are co-evolving. They influence one another.
JS is growing SIMD and other lower-level APIs (perhaps even
ARB_compute_shader in a future WebGL
On 1/19/14, Norbert Lindenberg ecmascr...@lindenbergsoftware.com wrote:
On Jan 19, 2014, at 10:01 , Jasper St. Pierre jstpie...@mecheye.net
wrote:
On Sunday, January 19, 2014, Garrett Smith dhtmlkitc...@gmail.com
wrote:
What considerations are there for codifying the behavior for
On 5/19/14, Garrett Smith dhtmlkitc...@gmail.com wrote:
On 1/19/14, Norbert Lindenberg ecmascr...@lindenbergsoftware.com wrote:
On Jan 19, 2014, at 10:01 , Jasper St. Pierre jstpie...@mecheye.net
wrote:
On Sunday, January 19, 2014, Garrett Smith dhtmlkitc...@gmail.com
wrote:
What
Le 14/05/2014 19:13, Axel Rauschmayer a écrit :
What is the best “bytecode isn’t everything” article that exists? The
“the web needs bytecode” meme comes up incredibly often, I’d like to
have something good to point to, as an answer.
This one looks good:
Hi,
(I remember, I mentioned this couple of years ago, but not sure about
whether it was considered, etc)
Will the Existential Operator for properly accessors be something
interesting to consider for ES7 spec? Currently CoffeeScript uses it well.
```js
var street = user.address?.street;
```
12 matches
Mail list logo
