Half of the webapps maybe. Actual websites don't have a reason to use any of these features and most don't (except for fonts maybe, but removing those doesn't prevent the website from working).

And not giving IKEA access to cameras in your home won't let them improve the furniture.

But it might be accepted if the furniture cost $0.

Well websites and documents are not the same thing so it makes sense that a paradigm that works for one doesn't necessarily work for the other. I do find web-based document editors very annoying to use when they are in the same window as other tabs - at least web browser MDIs allow you do effortlessly separate tabs into a new window these days.

These days QWERTY keyboards are optimal because programs, programming languages and text formats are optimized for QWERTY keyboards.

I have a QWERTZ keyboard!

Is my digital life at a natural end now?

If you mean the default German keyboard layout then, yes, putting backslashes, braces and brackets behind AtlGr makes it sub-optimal in my book. Thankfully what's printed on the keys is not that important so you too can have a QWERRTY keyboard if you want.

That's a sure way to guarantee that I will never contribute anything to a project.

Outside contributors have never been valuable as pure code monkeys.

Every inside contributor (besides the original author) started as an outside contributor. If the solution to the problem of LLMs is a blanket ban on outside contributors, I fear for the future of open source.

I disagree, when code took hours to write, it was very useful to have someone drive by and fix a bug for you. Now, all that does is it saves you five minutes of LLM crunching.

Also turns out the mildly higher barrier to entry for mailing-based workflows is actually a feature.

Yeah I have always seen PRs from new contributors as having (on average) negative value but being an investment into a hopefully future positive contributor. I don't have that optimism for contributors that start out with AI slop.

I think gp means that when a customer wants to connect to the VM there needs to be hardware (CPU and RAM) available to run it. While this can be less than the total number of (suspended) VMs it has to have some buffer of "unused" hardware to account for usage spikes that still needs to be paid for.

Those can just be VMs on a computer you already have. What's the advantage on putting them into a not publicly accessible cloud VM?