-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Summit topic: Bootstrap of Node.js Core #147
Comments
just documenting that this has been added to the working agenda, thank you! |
Time: CEST Fri 31-May-2019 16:00 (04:00 PM) |
I've uploaded the slides in here (there may still be changes before I actually give the talk tomorrow) |
@joyeecheung very good session and slides! It was an interesting and succinct overview. |
@joyeecheung thank you for posting the slides here -- gives me a nice high-level overview of what the effort/blockers are :) |
The bootstrap of Node.js had grown organically over the past few years, interleaving setup of globals, processing of CLI options and environment variables, and selection of execution mode across multiple files, both in JavaScript and in C++. This introduces difficulties for several efforts, e.g. V8 snapshot integration, better embedder API.
We recently started to refactor the bootstrap process with at least two goals in mind:
_third_party_main
(Deprecating _third_party_main nodejs/node#24017).In this session we will look into the general ideas behind the recent refactor, the current state of the bootstrap process, and discuss about work that needs to be done to achieve the goals mentioned above (or, if they are done by the time of the summit, just give an introduction about the internals and the principles that need to be followed when growing the bootstrap process).
The text was updated successfully, but these errors were encountered: