|
|
|
|
|
|
by sshine
833 days ago
|
|
|
> If they wanted it in the community edition, they'd simply copy the implementation from the paid version. […] Not sure why you're so up in arms about this. Because they don’t want the feature in the free version even if someone gave it to them. So when you invest in open-core, you don’t get incremental improvements as people collectively make an effort, like open-source. You get incremental improvements by eventually switching to the paid version. |
|
|
Gave it to them? They already have an implementation of this.
How is it a "gift" to spend unpaid time reviewing and merging a duplicate implementation, and then maintaining it forever, even though it likely has different dependencies and configuration option names than their existing implementation? And then after all that effort, all the maintainers get in return is a pay cut, if some paid users downgrade back to the free edition because they were only paying in order to use that feature?