If Microsoft can do things now with Electron that it couldn't before, there's arguably something wrong with the project.
If Microsoft can do things now with Electron that it couldn't before, there's arguably something wrong with the project.
It's not the license at issue, it's the copyright which allows MS to change the license.
Yes, developers could fork the project, but that seems premature at this point.
What will probably is that MS will make optimizations for VS Code to run even better and then make those optimizations open for everyone.
They already could of with the MIT licensed Electron... Literally nothing stopped them from doing this prior, unless the project as said has a bad structure but I find it hard to believe.
This would mean that you'd have to spend work re-merging your changes back with the main branch when a new version of Electron came out.
Now there's just one version, and it looks like MS controls the copyright to it. And that means their patches could come first before others.
I'm not sure what you're trying to say here, but I thought I'd clarify.
The owner of the copyright can relicense. Third parties can use the code to the license, but cannot relicense the code itself.
While MIT is very permissive, it doesn't give you permission to change the license, nor does it grant you the copyright to the underlying code.