3 ms·
> But so is anything relying on a CPU - we could just use ASICs for everything. But then every logical change requires weeks/months/years of development and man
by dahfizz 6y ago
> But so is anything relying on a CPU - we could just use ASICs for everything. But then every logical change requires weeks/months/years of development and manufacturing.
Right, except the asics already exist and you're actively choosing the less efficient, more expensive option.
> The goal of k8s, VMs, etc is flexibility.
I don't think this is necessarily bad, as long as you understand the tradeoff. You're choosing a fundamentally slower architecture to make management easier. It's a choice of prioritizing the developer experience over the user experience.
- oneplane 6y agoIn this case it's not even user experience vs. developer experience as you can have both; it's just the cost for performance gets higher as the efficiency decreases. On the other hand: the cost for development goes down if you don't need to pay for extra steps taken by an extra person. If you take a 10-step process that is run by 5 people and reduce it to a 5-step process run by 3, you have 2 more people to do other stuff, or roles that you don't have to create/fill in the first place.
- CountSessine 6y agoRight, except the asics already exist and you're actively choosing the less efficient, more expensive option. It’s hard to imagine any dev task being more expensive than organizing and programming tables into a trident or tomahawk chip using the broadcom’s SDK.