I think the web needs a bit of a redesign so that all of the responsibilities associated with hosting don't fall to a single entity. Responsibility and power go together, and power corrupts.
I ought to be able to choose a person that I trust to not lose or leak data, a different person to curate code for use on my device, and yet another person for being authoritative about the problem domain.
If I later decide that Jimbo has bad taste in client side code, I shouldn't have to also abandon Mary's excellent data handling track record. Yet somehow we've found our way to a corner of the design space where each entity that carries any of these burdens also carries the others.
How is this not already achievable today? You’re free to use Cloudflare to cache, AWS for your web servers and GCP for your DB. It’s just not as practical to do this from an IAM standpoint and cloud providers are offering incentives to get more of your hosting business.
Not really, I used ten or fifteen web apps today and I was totally at the mercy of whoever designed them re: who had access to the data I generated, re: which front end I used, etc.
It's the user's trust preference that I want to matter, not the app developer's.
My NAS appliance has plenty of storage available, I want to select it as my storage backend so that if the internet goes down everything that doesn't require collaboration still works for me. And not because I've been very choosy about what code I rely on, but because that degree of composability is built into the protocols.
I ought to be able to choose a person that I trust to not lose or leak data, a different person to curate code for use on my device, and yet another person for being authoritative about the problem domain.
If I later decide that Jimbo has bad taste in client side code, I shouldn't have to also abandon Mary's excellent data handling track record. Yet somehow we've found our way to a corner of the design space where each entity that carries any of these burdens also carries the others.