MS has a long history of taking something (a tech, a concept, etc), playing fair for years to attrack people, then add more and more little details that in the

MS has a long history of taking something (a tech, a concept, etc), playing fair for years to attrack people, then add more and more little details that in the end, lock you in into their ecosystem. In this particular instance, MS has been pushing the "dev env in the cloud" commercial strategy for some times, using the openess of the VSCode ecosystem as on of the bait. Don't get me wrong, I think VScode is a good product, and I can see the value of a dev env in the cloud that matches your local setup. But given MS track record, I expect this to be likely a way to take control of your dev env: once it mostly resides on their server, you are locked in. Parts of VSCode being not free are one of those little details I talked about. They hint at the direction MS is likely going to follow, as it used to do in the past.