2 ms·
Yup! A walled garden isn't just about developer lock-in driven by financial incentives. As far as the end-user goes, if the choices provided outside of the gar
by Dalewyn 4y ago
Yup!
A walled garden isn't just about developer lock-in driven by financial incentives. As far as the end-user goes, if the choices provided outside of the garden are wholly impractical it might as well be walled in practice even if it's not in theory/principle.
- imoverclocked 4y agoThis feels like a rabbit hole argument. So, down the rabbit hole we go! Let's imagine for a minute that using Open Source or FOSS also implies feeding back into the ecosystem. "Normal users" should be feeding back into the ecosystem somehow which then implies some form of understanding of that ecosystem. It can be bug reports (which requires understanding enough to post a coherent bug report), bug fixes (which requires knowing a little more), project leadership (which requires a different skillset and perhaps technical knowledge), monetary contributions (which makes the software less "free") My argument is, "Open Source doesn't get you past tanstaafl." The work to use it still needs to be done by someone. If you want to be a user of it and the thing you want to do isn't on the already-paved/easy-path then you need to get someone to pave that path for you or you need to understand how to do it yourself. That's the nature of the beast and has nothing to do with being a "walled garden."