{"json_modified": "2016-03-28T08:24:28.988017", "uuid": "8b6945f4-39b2-460f-be72-23c6d1d3608d", "title": "Future directions", "url": "/en-US/docs/Mozilla/Projects/SpiderMonkey/Future_directions", "tags": ["Guide", "Mozilla", "SpiderMonkey"], "translations": [], "modified": "2015-08-21T05:24:05", "label": "Future directions", "localization_tags": [], "locale": "en-US", "id": 57379, "last_edit": "2015-08-21T05:22:04", "summary": "This article documents future directions in functionality, design, and coding practices for SpiderMonkey. It can be read as something like an \"ideal future state\" for the engine. That means the code as it is today won't match this document, and that's OK. Whenever practical, new code and changes should move code closer to the ideal future. And of course, the idea of the future is always evolving in time as things change and we learn more.", "sections": [{"id": "Quick_Links", "title": null}, {"id": "Generational_and_compacting_GC", "title": "Generational and compacting GC"}, {"id": "Parallelism", "title": "Parallelism"}, {"id": "River_Trail", "title": "River Trail"}, {"id": "The_API", "title": "The API"}, {"id": "Practical_coding_bits", "title": "Practical coding bits"}, {"id": "Experimental_language_features", "title": "Experimental language features"}, {"id": "NSPR", "title": "NSPR"}, {"id": "JS_THREADSAFE", "title": "JS_THREADSAFE"}, {"id": "Directories_and_filenames", "title": "Directories and filenames"}], "slug": "Mozilla/Projects/SpiderMonkey/Future_directions", "review_tags": ["technical"]}