by that logic, i own a farm.Ploki wrote: Wed Feb 02, 2022 2:38 pm they do work for users who use their plugins, i mean... if they want to sell them.
Why do some plugin devs not accept feature request?
-
- addled muppet weed
- 111328 posts since 26 Jan, 2003 from through the looking glass
-
- KVRAF
- 6780 posts since 17 Dec, 2009
Who said anything about owning?
Working for something / someone doesn't preclude ownership.
I just think it's delusional to think developers just work for "themselves" or whatever. You work for yourself when you cook yourself dinner. When you cook it for someone else, you work for them as well. That doesn't mean you own them. That also doesn't mean you owe them next meal.
What's with americans and colonialism, sheesh.
-
- addled muppet weed
- 111328 posts since 26 Jan, 2003 from through the looking glass
i wouldn't knowPloki wrote: Wed Feb 02, 2022 2:45 pmWho said anything about owning?
Working for something / someone doesn't preclude ownership.
I just think it's delusional to think developers just work for "themselves" or whatever. You work for yourself when you cook yourself dinner. When you cook it for someone else, you work for them as well. That doesn't mean you own them. That also doesn't mean you owe them next meal.
What's with americans and colonialism, sheesh.
-
- addled muppet weed
- 111328 posts since 26 Jan, 2003 from through the looking glass
i find that offensive!
i just live here
i was gonna pay my farmhands a good wage.
-
- KVRAF
- 19885 posts since 16 Sep, 2001 from Las Vegas,USA
They don't work for us as individuals but they do work for us as the collective "customers".bitman wrote: Wed Feb 02, 2022 2:07 pm Developers don't work for you.
They don't have to do what you say or suggest.
If any of them do, that's a win.
That's all.
They either work for their customers or they won't have any.....
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe
-
- Beware the Quoth
- 35518 posts since 4 Sep, 2001 from R'lyeh Oceanic Amusement Park and Funfair
Are you sure you meant 'preclude?' I may be wrong, but from the 'doesnt' and context, I think you may have meant 'mandate' or 'predicate'.Ploki wrote: Wed Feb 02, 2022 2:45 pm Who said anything about owning?
Working for something / someone doesn't preclude ownership.
Might be something to do with all those colonists in America. Just a thought, though.What's with americans and colonialism
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."
-
- KVRAF
- 1655 posts since 3 Mar, 2009 from Colorado Springs
Crowds don't really speak with one voice and while everyone knows what they want, it is much rarer that people have a good sense of what other people want, and how their counter-party might variously feel about some changes that they themselves view as definitely good and desirable. On some issues there's more unity - obviously all Mac users who keep up with the hardware are looking for M1 support right now, so that should be a priority for developers who sell to that market, but kind of "braindead obvious" isn't it? Think any dev really has to be told, "hey, M1 is getting bigger and it is going to be really important to support that if you want to sell to Mac users?" Even the ones mad behind on that, for various reasons (and similarly those who are looking at Steinberg discontinuing VST2 as a seismic shock to their development strategies) are probably very well aware that it should be a priority if they can do so.
Then once you get away from big obvious stuff that pretty much any user could agree on, feature requests can be like fighting a hydra and who knows if something that would work well in terms of one person's workflow, even if that person can make a good case for why it should be changed, would actually then go on to be preferred and desired by other users? When devs already have a market liking their product, it can be difficult to calibrate to the crowd's desires and still keep a sense of identity & the appropriate focus for the product itself. One person's feature might be another's bloat, so there's that balancing act. It takes a lot of discernment on the part of creators to try to respond smartly and precisely to such a relative din.
Then once you get away from big obvious stuff that pretty much any user could agree on, feature requests can be like fighting a hydra and who knows if something that would work well in terms of one person's workflow, even if that person can make a good case for why it should be changed, would actually then go on to be preferred and desired by other users? When devs already have a market liking their product, it can be difficult to calibrate to the crowd's desires and still keep a sense of identity & the appropriate focus for the product itself. One person's feature might be another's bloat, so there's that balancing act. It takes a lot of discernment on the part of creators to try to respond smartly and precisely to such a relative din.
-
- KVRAF
- 6780 posts since 17 Dec, 2009
Oopsy.whyterabbyt wrote: Wed Feb 02, 2022 3:14 pmAre you sure you meant 'preclude?' I may be wrong, but from the 'doesnt' and context, I think you may have meant 'mandate' or 'predicate'.Ploki wrote: Wed Feb 02, 2022 2:45 pm Who said anything about owning?
Working for something / someone doesn't preclude ownership.
Might be something to do with all those colonists in America. Just a thought, though.What's with americans and colonialism
I meant to say predispose but predicate works better