On 2/3/14, 6:16 PM, Jeff Walden wrote:
There's a bunch of tribal knowledge among JS hackers of where we want
the engine to go, but we just haven't quite yet taken it. Sometimes
that info's useful/relevant to design of present-day patches or
approaches. It would be useful to have that documented somewhere so
that people are more on the same page, and don't have to rely on what
luke or jorendorff or I say in passing about where things are headed.
Also sometimes embedders want to have ideas about this stuff (see the
js-engine thread I just sent mail to, for example). So here's the start
of such a document:
https://wiki.mozilla.org/JavaScript:SpiderMonkey:LongTermPlans
Jeff, regarding proxies and JSClass, can you elaborate on "the idea of
classes is in the middle of deprecation in ECMAScript"?
I added links to existing bugs for some of these issues:
• bug 586842 - Split property/element storage
• bug 650361 - rm JSContext
• bug 570568 - JSPropertyOps has bad human factors
• bug 842186 - Replace all use of jsval with JS::Value
There is also this older plan to reorganize the js/src source files:
https://wiki.mozilla.org/JS_engine_modularization
chris
_______________________________________________
dev-tech-js-engine-internals mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
