You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey @stevefan1999-personal thanks for raising your feature request. Personally I am not really a fan of this tbh, we've been trying hard to reduce the overall time it takes to start a devpod and waiting for all extensions to download could really delay the time vscode first opens. Codespaces and native vscode also does this when it opens, it will still be downloading extensions etc in the background.
I will keep this ticket open though as this is just my opinion and to track if there is more interest from the community for it.
Hey @stevefan1999-personal thanks for raising your feature request. Personally I am not really a fan of this tbh, we've been trying hard to reduce the overall time it takes to start a devpod and waiting for all extensions to download could really delay the time vscode first opens. Codespaces and native vscode also does this when it opens, it will still be downloading extensions etc in the background.
I will keep this ticket open though as this is just my opinion and to track if there is more interest from the community for it.
Well, I think Coder waits for the extensions to be downloaded, but I do understand minimizing the time-to-IDE might also be an important metric...
But at least for me, I'd rather wait for a full, stable environment more than having it as quickly as possible, as that might also mean things like code index won't just work out of the box when I touch it, and might cause further chaos, so I think we could make this an option which is not enabled be default.
So yeah, it's a trade-off for stability/readiness and latency/speed
I have configured the devcontainer to use a dark theme, but it takes some time to download. Maybe we should wait until it fully works
The text was updated successfully, but these errors were encountered: