Open
Conversation
Signed-off-by: Timo Reichl <thetredev@gmail.com>
|
But... why? Retype is just one install and one command. Why add containers into the mix, let alone an editor-specific container? |
Author
|
Because that's how many people including me are developing nowadays without installing stuff to their host system. But if you don't want it you can close it of course. |
|
I think this makes sense as it simplifies collaboration |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 thought it might be a good idea to provide a VS Code devcontainer environment to make it easier to develop. Only works on Linux (and probably macOS) right now. On Windows, Linux containers have to be used.
Some defaults might not be "the right choice", like
vim. Those are up for discussion as well :)