I’ve been there, but over the years I’ve gotten better at avoiding being in this situation.
If you are implementing something for yourself, and merging it back upstream is just a bonus, then by all means jump straight to implementing.
However, it’s emotionally draining to implement something and arrive at something you’re proud of only to have it ignored. So do that legwork upfront. File a feature request, open a discussion, join their dev chat - whatever it is, make sure what you want to do is valued and will be welcomed into the project before you start on it. They might even nudge you in a direction that you hadn’t considered before you started.
Be a responsible dev and communicate before you do the work.
Thanks for sharing! Really interesting history in this article. It’s scary to think what a world would look like if Sun didn’t sue Microsoft into oblivion and put an end to this strategy.
We could be living in a world where Windows is the dominant desktop OS instead of our beloved Solaris.
To be serious, though, being sued/forced to settle isn’t an indicator that the strategy hasn’t worked. In fact, as is evident by the continued doubling down on the strategy by Microsoft and the unfettered execution of this strategy with Chrome, it’s clear that the value far outweighs the cost of the occasional settlement. The only real deterrent is antitrust regulation and that has been just about entirely defanged. These concerns are especially pertinent for something like Lemmy where there’s no central entity to soak the legal fees to go to court.
A few animal-inspired names that I think have a nice ring to them
You can substitute “at least 10 years ahead” as stated in the second sentence of the article quoting US senators.
The community-based project of passion to enhance lemmy is already here... it's lemmy.
This isn't reddit. There isn't a big black box and company around the service that is preventing the community from making it what they want it to be.
Sure there can be flavors, but I'd guess if there's the type of consensus around the usefulness as there is with RES, then why wait for a separate project to shoehorn features on top of lemmy when the folks behind lemmy seem quite receptive to contributions?
@dgkf
@lemmy.ml