Yep. Imagining nontechnical users would endure paths of greater resistance to avoid shady privacy and openness practices is magical thinking. Privacy and openne

Yep. Imagining nontechnical users would endure paths of greater resistance to avoid shady privacy and openness practices is magical thinking. Privacy and openness are important, but having tools designed to maximally reduce the overhead of solving your problems is more important. I know I get on people's nerves on HN by harping on user needs and FOSS usability and interface design and such, but I think we as a group need to start taking user needs much more seriously. Open-source alternatives will always be alternatives until without taking usability and the overall experience seriously. Many, if not most FOSS software developers choose some commercial tools— count how many MacOS and Windows laptops you see at OSCON or FOSDEM. Consider how different the cost/benefit analysis would be for people without the most basic requisite knowledge to reason about software problems, let alone troubleshoot, or throw in a PR to address them directly. Commercial companies don't get these seamless experiences by magic— it involves research, design, development and testing to deliberately remove friction and stumbling blocks rather than assuming your use case is universal, or that docs are a suitable replacement for fixing usability problems. There's nothing stopping any open source project from doing any of it. Volunteering isn't unique to coding— people volunteer to cook and build houses and clean up trash, too. But developers run FOSS and developers need to deliberately incorporate those other perspectives into their projects to get the benefit.