Ha! Yes, my shorted argument of "optimizing for laziness" doesn't sit right, but the core of it how much your choices matter in what you are _not_ building.
- Cloud-based apps used to mean managing VMs, keeping kernels up to date, setting security settings on server configs. It doesn't have to[0]
- Mobile dev used to mean compiling platform-specific code and shipping it to app-store review. It doesn't have to[1]
- Storing state server-side used to mean running your own DBs and worrying about their persistence and multi-host-scaling. Don't even need a reference here since there a so many choices.
> Cloud-based apps used to mean managing VMs, keeping kernels up to date, setting security settings on server configs.
PaaS offerings where this kind of thing was not required were among the very early dynamically-scaled application platforms to get the "cloud" label. IaaS offerings where this is required and part of the price for greater control exist, to be sure, but have never been the only cloud platforms.
- Cloud-based apps used to mean managing VMs, keeping kernels up to date, setting security settings on server configs. It doesn't have to[0]
- Mobile dev used to mean compiling platform-specific code and shipping it to app-store review. It doesn't have to[1]
- Storing state server-side used to mean running your own DBs and worrying about their persistence and multi-host-scaling. Don't even need a reference here since there a so many choices.
[0] https://www.ibm.com/developerworks/cloud/library/cl-bluemixf...
[1] https://getexponent.com/