2 ms·
The bit that matters: > Due to the specific source code used for App Maker, you can’t directly migrate your apps to another platform. We recommend that you exp
by afandian 7y ago
The bit that matters:
> Due to the specific source code used for App Maker, you can’t directly migrate your apps to another platform. We recommend that you explore these options
There must be some kind of demand curve model whose independent variable is the ability to move to another service. A highly specialised PAAS might solve all your problems but be so unique that it's too risky to spend too much money on.
- derefr 7y agoYeah, that sounds right; Docker’s probably right at the optimum point there. Though I think such a demand curve would imply that highly-specialized environments can still be useful for cases where you don’t need to spend much money on them, because you only put tiny bits of functionality in there. Lambda, Cloudflare Workers, SQL stored procedures, etc.
- spankalee 7y agoHad I started App Maker with the web platform and Node of today, I would have definitely designed things to use standard web APIs, Node on the server, and common tools for things like IO and data. Apps would have mostly a set of JS modules talking to generic enough backends to be portable. Ideally there would just be an eject button that would give you either a npm-ready project, or a Docker container. Then you could run it anywhere. The problem is that App Maker was built in GWT (basically what made sense in 2009), and because we didn't have a JS server runtime, ran JS script in Rhino on Java servers. Rhino was great at the time, but didn't evolve, and offered super-powers (like custom Java host objects that can observe mutations, even on arrays) that made JS written to our environment difficult to port. Also, all of the server and data interactions were via APIs that are strange by today's standards because of the layering on Java.