4 ms·

Here's an overview: https://powerapps.microsoft.com/en-us/blog/what-is-microsoft-power-fx/ https://powerapps.microsoft.com/en-us/blog/what-is-microsoft.... I t

by Zanni 6y ago

Here's an overview: https://powerapps.microsoft.com/en-us/blog/what-is-microsoft-power-fx/ https://powerapps.microsoft.com/en-us/blog/what-is-microsoft.... I think more interesting than "low code" is the stated goal of enabling "the full spectrum of development from 'no code' to 'pro code' with no cliffs in between." "Pro code" means you can edit the source with Visual Studio and use source control.

nwah1 6y ago
This is indeed a killer feature. You would never be able to load a Microsoft Access ACCDB file into version control and extend it in any way beyond the limitations of the Access runtime. This provides a path to convert a rapid prototype into a real app.
- wokwokwok 6y ago
  Does it though? Got an example? I mean, yeah, great ideal, but that doesn’t appear (to my superficial look at it so far?) appear to be anything other than an ideal. I can also aspire to build a platform which enables everyone to prototype and then also run it in production with no performance issues, where “pro developers” can just pickup where “casual developers” left off on the prototype. ...but I’m not really interested until someone actually does it, rather than just talking about it. The power platform is a lot of PowerPoint and sales talk so far from what I’ve seen, but with what seems of actual implementation always rolling back to Q2 next year when you ask for the details... I mean maybe you got further than me down the rabbit hole than [1], but yeah... I can modify some of the display javascript as long as I use the API and do not interact with the DOM is 100% not a killer feature. [1] https://docs.microsoft.com/en-au/powerapps/developer/model-driven-apps/overview https://docs.microsoft.com/en-au/powerapps/developer/model-d...
  - nwah1 6y ago
    Microsoft has a lot of history building platforms for novices to produce functional systems. This one seems to be going in an open source direction, and building upon web standards. This gives it a much better chance of success. Obviously it requires investment, and there is no certainty of success. But even just a carbon copy of an existing project like Access 365, but an open source version that targets the web would be very useful. Especially if it could be extended with .NET and put into version control. Although there are competitors in that space. Reimagining the entire Rapid Application Development model is riskier for sure.

by Zanni 6y ago

nwah1 6y ago

This is indeed a killer feature. You would never be able to load a Microsoft Access ACCDB file into version control and extend it in any way beyond the limitations of the Access runtime. This provides a path to convert a rapid prototype into a real app.

wokwokwok 6y ago
Does it though? Got an example? I mean, yeah, great ideal, but that doesn’t appear (to my superficial look at it so far?) appear to be anything other than an ideal. I can also aspire to build a platform which enables everyone to prototype and then also run it in production with no performance issues, where “pro developers” can just pickup where “casual developers” left off on the prototype. ...but I’m not really interested until someone actually does it, rather than just talking about it. The power platform is a lot of PowerPoint and sales talk so far from what I’ve seen, but with what seems of actual implementation always rolling back to Q2 next year when you ask for the details... I mean maybe you got further than me down the rabbit hole than [1], but yeah... I can modify some of the display javascript as long as I use the API and do not interact with the DOM is 100% not a killer feature. [1] https://docs.microsoft.com/en-au/powerapps/developer/model-driven-apps/overview https://docs.microsoft.com/en-au/powerapps/developer/model-d...
- nwah1 6y ago
  Microsoft has a lot of history building platforms for novices to produce functional systems. This one seems to be going in an open source direction, and building upon web standards. This gives it a much better chance of success. Obviously it requires investment, and there is no certainty of success. But even just a carbon copy of an existing project like Access 365, but an open source version that targets the web would be very useful. Especially if it could be extended with .NET and put into version control. Although there are competitors in that space. Reimagining the entire Rapid Application Development model is riskier for sure.