If the future is made up of tools so complicated that only giant corporations are able to provide them, I hope we'll also see a strong counter-movement of simple tools for independent developers.
I think the future is made up of powerful tools so simple that only great resources can build them. Simple tools that hide the magic are harder to build.
The fix is in because vscode itself will be forkable at any time. It will just be that _services_ from microsoft and other companies will be designed for the tool.
For example, this AI code completion behavior. I can say right now that if tabnine had a version working in Pycharm that did not break autoimports, I would already be paying a monthly subscription for it. Jetbrains should be offering something similar ASAP.
Another example would be PaaS for frameworks using Azure. Start a project, choose a domain name, instant staging and production deployments.
Anyone could build these kinds of plugins to sell in services. It will really be about who does it best. Though, I think Microsoft is specifically positioning itself for a long term play here and I think much of it centers around vscode.
I was thinking simple in the sense of less hidden magic.
Deployment can easily be done with a script from the terminal, which doesn't need special IDE integration. "Starting a project" doesn't need any tools at all in simple cases - one could try to keep cases simple.
Python usually has less need for auto-imports than Java does because APIs are simpler, names shorter and modules more coarse-grained.
You might not need an IDE and an AI with simple tools. Of course, some problems require or benefit from complicated magic tools, but perhaps not all problems do.
I see. Some folks may want simple, no magic stuff. My last product I had a one line terminal deploy for staging and one for production.
But setting that up securely in of itself was a lot of work.
On my new project I deploy by pushing to staging or master. These deploys are blocked if the commit under inspection does not pass tests.
That all happens because of docker containers and GitHub actions and secrets. There is an enormous amount of magic behind this stuff but I would not go back to provisioning and maintaining my own boxes.
I do think there is a lot of benefit to gain from having services built directly into the IDE.
For small projects, a text editor will do. Though linting and code formatting helps beginners and pros alike.
The fix is in because vscode itself will be forkable at any time. It will just be that _services_ from microsoft and other companies will be designed for the tool.
For example, this AI code completion behavior. I can say right now that if tabnine had a version working in Pycharm that did not break autoimports, I would already be paying a monthly subscription for it. Jetbrains should be offering something similar ASAP.
Another example would be PaaS for frameworks using Azure. Start a project, choose a domain name, instant staging and production deployments.
Anyone could build these kinds of plugins to sell in services. It will really be about who does it best. Though, I think Microsoft is specifically positioning itself for a long term play here and I think much of it centers around vscode.