Improve startup performance & status #6210
Open
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.
This change improves the startup experience in the Positron Console and also contains performance improvements that significantly decrease startup time (especially in dev builds)
Before the change, the console would say "Starting..." / "Starting up..." for several seconds before a console opened.
positron-before.mov
After it, in most Positron sessions no noticeable time will be spent in either state; instead, Positron will show you the interpreter it's working on starting.
positron-after.mov
Still more we could do to make this better, such as improving the styling and coordinating better with console startups, but want to minimize overlap with multi-console work.
Addresses #3566.
Release Notes
New Features
Bug Fixes
QA Notes
You will see the new experience when Positron knows what runtime to start, but mostly the old one when Positron has to discover all interpreters (though even discovery will be a little faster now since it starts earlier). Specifically, you should see it:
recommendedWorkspaceRuntime()
#6208.Test tags:
@:console