4 ms·
I don't know if they're pursuing this, but Microsoft also has the opportunity to create low-code solutions that more gracefully transition into conventional sol
by jerf 5y ago
I don't know if they're pursuing this, but Microsoft also has the opportunity to create low-code solutions that more gracefully transition into conventional solutions, because unlike a pure-low-code play, that doesn't have to mean they are losing a customer. They aren't incentivized to lock you in to low code as long as one way or another you pay Microsoft on the way out, too, via either being in the conventional Microsoft developer ecosystem or being on Azure.
Given that they seems to be acquiring they way into this market, I'm sure it's nowhere near this integrated yet, but could you imagine being able to take any individual component of the system, or the system as a whole, and getting a "Click Here to create a Visual Studio Project" that completely replicates the low-code solution into Visual Studio, ready and waiting for you to start modifying it? Probably with some sort of automatic "Click Here to Deploy Your Changes Into Azure"?
- WorldMaker 5y agoThat's very much Microsoft's goal here. It's a lot of why they started pushing everyone to stop calling it "No Code" and moved to the name "Low Code". At BUILD they released some of the first big VS Code plugins for some of the Low Code systems. (Power Apps is represented mostly as a lot of YAML files, if you were curious.) Most of the Low Code systems already use Azure CI/CD and git under the hood and editing Low Code projects in VS Code and VS seems easy enough for "conventional" developers.