5 ms·

People that dont like the cloud are generally engineers who were left behind by the paradigm shift. They want development to go back to what they spent a decade

People that dont like the cloud are generally engineers who were left behind by the paradigm shift. They want development to go back to what they spent a decade learning. And so they complain about complexity or out of control cost. The truth is, they arent effective engineers with the cloud because they havent learned it in depth. It is clearly 100x better than on premise, and the boom in tech is partially from productivity gains from cloud. Infrastructure as Code is a major technological improvement.

hotpotamus 3y ago
Infrastructure as code is indeed a major technological improvement, which is why I use it on-prem lol.
- optimalquiet 3y ago
  I’ll do you one better, I use IaC techniques to configure VMs at home, on an old workstation I’ve turned into a server. It’s great for hobbyists, too, and doesn’t require the cloud although I will admit it’s easier to go all the way when resources are totally spin-up-as-needed. But I don’t need to go all the way, I’m just a simple hobbyist.
  - thrixton 3y ago
    What flavour? I’d love to be able to configure a proxmox, linux vm through pulumi (or TF if that’s your thing), Ansible seems to be the best option but I’ve not had enough experience to be competent as yet.
paulclinger 3y ago
The article (and the local-first software) has nothing to do with cloud vs. on-prem. It's about the priorities in developing and running/using your applications: "The word “local” in the name refers to your personal computer. “First” means your computer is prioritized over “someone else’s.”". Local-first apps can still use cloud resources for synchronization or for simplifying their initial configuration, but it's not a focal and critical point of the design and only serves as one of the nodes and can be made optional. You can still get all the benefits of being cloud-enabled, but you're also getting all the benefits of working without any cloud involvement at the cost of adding synchronization and conflict-resolution mechanisms.

hotpotamus 3y ago

Infrastructure as code is indeed a major technological improvement, which is why I use it on-prem lol.

optimalquiet 3y ago
I’ll do you one better, I use IaC techniques to configure VMs at home, on an old workstation I’ve turned into a server. It’s great for hobbyists, too, and doesn’t require the cloud although I will admit it’s easier to go all the way when resources are totally spin-up-as-needed. But I don’t need to go all the way, I’m just a simple hobbyist.
- thrixton 3y ago
  What flavour? I’d love to be able to configure a proxmox, linux vm through pulumi (or TF if that’s your thing), Ansible seems to be the best option but I’ve not had enough experience to be competent as yet.

paulclinger 3y ago

The article (and the local-first software) has nothing to do with cloud vs. on-prem. It's about the priorities in developing and running/using your applications: "The word “local” in the name refers to your personal computer. “First” means your computer is prioritized over “someone else’s.”". Local-first apps can still use cloud resources for synchronization or for simplifying their initial configuration, but it's not a focal and critical point of the design and only serves as one of the nodes and can be made optional. You can still get all the benefits of being cloud-enabled, but you're also getting all the benefits of working without any cloud involvement at the cost of adding synchronization and conflict-resolution mechanisms.