The argument does not hold up for me. When I think of PaaS I think of Heroku which was a breath of fresh air at the time and is a model that still works well for the initial stage of a project. Fly.io and Kubernetes may fit in the same general circle but I don't believe are comparable to a Heroku.
Agree that Fly.io is pretty terrible experience as it markets an edge case that I don't believe the vast majority of systems need. The base PaaS case is pretty magical though and abstracts away a lot of the things I honestly don't care about for the first N thousand users.
Comments
The argument does not hold up for me. When I think of PaaS I think of Heroku which was a breath of fresh air at the time and is a model that still works well for the initial stage of a project. Fly.io and Kubernetes may fit in the same general circle but I don't believe are comparable to a Heroku.
Agree that Fly.io is pretty terrible experience as it markets an edge case that I don't believe the vast majority of systems need. The base PaaS case is pretty magical though and abstracts away a lot of the things I honestly don't care about for the first N thousand users.
What edge case does fly.io market to?
...deploying apps at the edge?
slaps forehead