If folks were really committed to improving the developer experience, then instead of what we do now and instead of what services like GitPod and Codespaces propose that we do, development would work like this:
1. Download the project source tree
2. Open README.html
3. Drag and drop the project source _onto_ README.html, which doesn't contain half explanations about setting up the appropriate development environment, so much as it contains an exact description (i.e. in executable code) of the build process—for the benefit of the machine that will perform it (along with these three steps—for the benefit of the human/prospective contributor)
† See <https://www.colbyrussell.com/2019/03/06/how-to-displace-java...>
Pull up a chair for a moment and consider that in this moment of time you are an open-source maintainer or a team-lead who has to review the pull-requests in the video below. Each browser tab is a brand new development environment, the git branch is automatically cloned, all dependencies are restored and your software has already been compiled.
Good? Now you understand what Gitpod is all about.
The same could be said about codespaces. In fact, more people getting into codespaces is great for platforms like gitpod that can fight and offer solid alternative experiences.
The issue I believe for platforms like gitpod is to shift the mindset of many devs and companies that developing in a browser isn't merely a possibility but sometimes preferable.