Author seems to ignore that FOSS projects tend to be much smaller teams without budget to create the user experience that private VC funded projects can.
Ths whole accountability argument seems to be pretty disingenuous, allowing anyone who wants to evaluate the source code is about as accountable as it gets.
The not-so-subtle “you will be lazy about what your doing if someone is not paying you not to be” vibe throughout this article is off putting to say the least.
I also find prioritizing user experience over the sharing of source code to be misguided. Allowing folks to gate keep knowledge and hide what they are doing is a big price just for a better user experience.
The real issue with FOSS is the same as with P2P networks. Most people are leechers whose only contribution is lip service.
I… these are all good points, but… did we read the same article?
Article seems to ignore that FOSS projects tend not to have the budget to create the UX that VC-funded projects can. … I find prioritizing UX over sharing of source code to be misguided.
The author specifically calls attention to this exact point:
If a weirdo guy moved into your kitchen and blocked you from grabbing a spoon whenever you wanted and instead rented them out to you provided you only ate the gruel he provided, the people who would be most able to see the absurdity in that would be be the people who remember what it was like before. Those who grew up with that system would be “whaddayamean? This is super convienient. I just stick my hand in the kitchen and a spoonful of gruel is shoved into it. Like it, love it, want more of it”. They’d be like “people who don’t have a spoon guy are so gross and so dumb. What the heck are they even? Doing rifling through their own cutlery drawer like some sorta eggheads”.
Honestly i found that whole excerpt to be pretty nonsensical.
Don’t see how that relates to what i said and then you quoted but reworded (why?). Plus it all just circles back into “its bad cause the UX is slightly more inconvenient”.
If the author had any substance to his argument it wouldn’t require laying out a ridiculous scenario just to get the reader to understand what in hell he is trying to say.
He basically tldrs the whole article a few sentences later with " I want it to be easy to use." The author never seriously considers if that’s worth the cost.
I think they addressed that point pretty clearly. The author says that just because the user experience of sticking your hand into your kitchen and instantly receiving food is fantastic, doesn’t mean that letting someone you don’t know live in your kitchen and only eating what they decide to make you is a good solution, especially since it means you couldn’t use your kitchen (which I believe is a metaphor for your smartphone) for anything else even if you wanted to. Further, those who believe it’s a good solution because it is free and its user experience is good only believe this because they have never known anything else. The author also explicitly states
So that’s the dialectic here. I want people to not have to know about tech stuff. I’m not into the tech-for-tech’s-sake lifestyle. I want it to be easy to use. You just tell the computer what you want and it happens, no need to point and click, let alone configure and make. That’d be great. And hackers and modders could add features and share them and everyone would benefit.
But it’sgotto be free, free for reals. Open source, and either decentralized or democratically governed.
The author, I think, is saying that while user experience is a nice goal to pursue, it means nothing if it isn’t open source, and you can’t go around the carefully-crafted VC-funded fancy-but-restrictive UX if you have the skills to do so. Perhaps it is a reach to say that the author prioritizes open source over good user experience, but I don’t think so, and even from the most pessimistic reading of those two paragraphs the author views them as at least equal.
you quoted but reworded (why?).
I quoted and reworded it because I was on mobile and couldn’t copy paste from your comment without a lot of hassle, and didn’t want to retype everything you had typed word for word. Didn’t mean anything by it.
I find this take fascinating…the only thing I would add is that if you have something else more important to do than grabbing a spoon…then the spoon guy could be a godsend…
…so you’re perfectly happy being prevented from eating anything other than what the guy renting your own kitchen out to you cooks, so long as most of the time, he makes something you like eating?
In this metaphor, if he decides to change his recipe and you don’t like the new food, you can’t just ask him to make something else. He owns your kitchen.
Author seems to ignore that FOSS projects tend to be much smaller teams without budget to create the user experience that private VC funded projects can.
Ths whole accountability argument seems to be pretty disingenuous, allowing anyone who wants to evaluate the source code is about as accountable as it gets.
The not-so-subtle “you will be lazy about what your doing if someone is not paying you not to be” vibe throughout this article is off putting to say the least.
I also find prioritizing user experience over the sharing of source code to be misguided. Allowing folks to gate keep knowledge and hide what they are doing is a big price just for a better user experience.
The real issue with FOSS is the same as with P2P networks. Most people are leechers whose only contribution is lip service.
I… these are all good points, but… did we read the same article?
The author specifically calls attention to this exact point:
Honestly i found that whole excerpt to be pretty nonsensical.
Don’t see how that relates to what i said and then you quoted but reworded (why?). Plus it all just circles back into “its bad cause the UX is slightly more inconvenient”.
If the author had any substance to his argument it wouldn’t require laying out a ridiculous scenario just to get the reader to understand what in hell he is trying to say.
He basically tldrs the whole article a few sentences later with " I want it to be easy to use." The author never seriously considers if that’s worth the cost.
I think they addressed that point pretty clearly. The author says that just because the user experience of sticking your hand into your kitchen and instantly receiving food is fantastic, doesn’t mean that letting someone you don’t know live in your kitchen and only eating what they decide to make you is a good solution, especially since it means you couldn’t use your kitchen (which I believe is a metaphor for your smartphone) for anything else even if you wanted to. Further, those who believe it’s a good solution because it is free and its user experience is good only believe this because they have never known anything else. The author also explicitly states
The author, I think, is saying that while user experience is a nice goal to pursue, it means nothing if it isn’t open source, and you can’t go around the carefully-crafted VC-funded fancy-but-restrictive UX if you have the skills to do so. Perhaps it is a reach to say that the author prioritizes open source over good user experience, but I don’t think so, and even from the most pessimistic reading of those two paragraphs the author views them as at least equal.
I quoted and reworded it because I was on mobile and couldn’t copy paste from your comment without a lot of hassle, and didn’t want to retype everything you had typed word for word. Didn’t mean anything by it.
@AVincentInSpace @Imprint9816
I find this take fascinating…the only thing I would add is that if you have something else more important to do than grabbing a spoon…then the spoon guy could be a godsend…
???
Tell me you are not arguing in favor of only being able to eat gruel for the rest of your life simply because it is convenient?
Even if you did want that, you’d have a MUCH better time setting up the gruel station yourself, so that you could bypass it if you wanted to.
@AVincentInSpace
Well not gruel…I would hate that obviously 😅
…so you’re perfectly happy being prevented from eating anything other than what the guy renting your own kitchen out to you cooks, so long as most of the time, he makes something you like eating?
In this metaphor, if he decides to change his recipe and you don’t like the new food, you can’t just ask him to make something else. He owns your kitchen.