I'd say it works such that any mildly technically competent person can use it.

The problem is that I know The absolute surface level nature of most people's technical ability.

The dual file system nature of winboat would probably cause you issues. All you have to do is save your work to the folder that you have shared between both os's, but equally, I know full well the majority of computer users don't know what a file or directory structure is.

I have been managing with winboat for my office requirements.

I did try the 'ouch' feature and that was fun for all of 10 minutes and then it moved very quickly into annoying so that feature got disabled.

https://arner.github.io/posts/#make-glados-clean-your-floor

Can confirm it works and is great. I'm even running a Glados voice pack on it that insults me while it cleans.

Only issue I've had the whole time was actually this week when I finally updated the valetudo re version to support the new home assistant MQTT format and the update got stuck but that was an easy fix once I worked out what it was.

I mean they've tried and recently, but there are actually a lot of additional problems that kick in as soon as you try it e.g. you can't just use the air for fuel for oxidiser once you are going at the sorts of speeds you need to achieve.

Skylon (spacecraft) - Wikipedia https://en.wikipedia.org/wiki/Skylon_(spacecraft)

My biggest issue with the vote was that Brexit didn't win.

48% votes to remain and 52% percent votes for 6 different and often mutually exclusive relationships. Which was proven as soon as negotiations began and why there should have been a vote on the final deal which would have certainly failed. But instead people voting for a Norway model or a Swiss model all got counted alongside the lunatics that would have physically dragged the UK further into the Atlantic to get away from Europe given the chance.

It wasn't 48% Vs 52%, it was 48% vs 8% and 8% and 8% .......

Other good options

"Is it a boy or a girl"

"Yes" / "One of those" / "Almost certainly" etc

What if your compiler is compromised? https://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_ReflectionsonTrustingTrust.pdf

It depends on the level of mistrust you're willing to entertain but the short version is; no, you cannot be sure.

Ken Thompson's 1983 talk, Reflections on trusting trust is the classic talk on just why you cannot be sure.

The point, is that people don't like thinking about this subject, as evidenced by the fact that half of people don't put plans in place even when it's something as comparatively simple as a will unless they get more imminent prior warning. This is not a Linux kernel specific issue, Bram and vim being an obvious example. Something as potentially complicated as the Linux kernel succession? I can see why it wouldn't be a subject the community was keen to tackle.

Have you got a will?
Estimated 50% of adults don't. There's always a more pleasant task on the to-do list to be getting on with.

There is a continuity process at least https://github.com/torvalds/linux/commit/102606402f4f5943266160e263c450fdfe4dd981 Although it is mainly, here is the process to figure out the plan.