Create startup performance strategic initiative #682
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Trott
approved these changes
Mar 31, 2019
targos
approved these changes
Mar 31, 2019
gireeshpunathil
approved these changes
Mar 31, 2019
addaleax
approved these changes
Mar 31, 2019
gabrielschulhof
approved these changes
Mar 31, 2019
apapirovski
approved these changes
Apr 1, 2019
danbev
approved these changes
Apr 1, 2019
ofrobots
approved these changes
Apr 1, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've been spending the past few months on refactoring the bootstrap to pave the way for shipping snapshot (probably created a lot of conflicts for whoever rebases against our master branch but I believe once the refactor reaches a stable state it would be easier to rebase from now on since it'll be less spaghetti-like). Prior to that, I had been working on code cache integration though I am still stuck with build issues, which I plan to solve together with the snapshot integration given how similar the requirements are.
Considering that there is a pretty clear plan for this effort, I think it is worthy of being a strategic initiative of its own. This makes Node.js more viable for tooling, mobile and serverless use cases. (It also does not hurt that this helps us spend less time on waiting for the tests to complete ;) ) .
Other than builtin snapshot integration I am also looking into implementing snapshot builders for users (either in core or as a separate module, but I suspect we'll end up reusing most of the code in core so we may consider just exposing the functionality to users) - this has been a common request when I chat about what I've been working on lately with other people.