News for hackers. Stuff that matters.
Re:Before the iPhone, I worked on a few games for what were ... by kelnos on Thursday May 20, 2021 @03:09PM (#27225681)
The problem is that it then gives the developer weird incentives. If someone in the community decides to build the same feature that the main developer kept as a paid feature, then the main developer won't want to merge it into their version.

Then you're stuck: the community member could certainly fork the project with their new feature, or maintain a patchset and forward-port to each new version of the original software, but both of those things are a ton of work.

Meanwhile, users are the ones who lose out; someone decided to build the feature and give it away for free, but users have to jump through hoops to use it.

As someone who has done a lot of open source work over the past ~20 years, I don't think anyone is entitled to find a business model in there. Sure, if you can find a way to work on your project full time but still support yourself, that's great. But often the ways people do so make for some (IMO) bad trade offs and perverse incentives.

I like the dual-licensing approach, where commercial users need to pay, but that's not workable for all projects.

Re:Before the iPhone, I worked on a few games for what were ... by soylentgraham on Thursday May 20, 2021 @04:21PM (#27226666)
Or once the new feature is paid for... then release it. Someone has paid for your time (to develop the feature). They get their feature, (which they need enough to part with money), the community gets it too (whether they need it or not)

It doesnt benefit from the massive scale revenue, but if it's paid for your time...

Re:Before the iPhone, I worked on a few games for what were ... by oooooooooooow on Thursday May 20, 2021 @07:18PM (#27228669)
I imagine the logic here would be developing a passive income to compensate for the free labor you put in in the first place, and cover whatever future free labor you might want to do.
Re:Before the iPhone, I worked on a few games for what were ... by selfhoster11 on Thursday May 20, 2021 @03:59PM (#27226357)
> The problem is that it then gives the developer weird incentives. If someone in the community decides to build the same feature that the main developer kept as a paid feature, then the main developer won't want to merge it into their version.

See VirtualBox, and to some extent Chrome. For VirtualBox, I'm sure that the Extension Pack could be covered with an open-source effort by the community, and in the case of Chrome, their refusal to accept *BSD patches.

Re:Before the iPhone, I worked on a few games for what were ... by renox on Thursday May 20, 2021 @06:11PM (#27228059)
I remember reading recently about a "Firefox bug" caused by a buggy "portability" patch of one of their dependencies.

Accepting 'portability patch' isn't free..