I hope it works out for the author. If not, maybe there are other revenue generation options that could be paired with a less restrictive license.
It will be OK if the commercial option only applied to large organizations. But with the current setup, it just makes Dramatiq unreachable for the small players.
And we already have pricing models for small/medium sized businesses vs large ones. OSS could easily have similar models.
The way I think about it is what if the only database solution was Oracle. I'm sure many would have wrote their own limited buggy DBMS or used flat files instead. It will certainly be more expensive to write your own Oracle RDBMS from scratch instead of paying for the licence. But you don't need most of the features and for the ones you need, the price point does not make sense for all projects. For some projects, flat files or JSON files saved somewhere on the disk wouldn't sound so bad.
That said, I do give out commercial licenses for free for companies that are just starting out. My goal with this is not to get rich, it's just to get people to contribute something back in whatever way they can.
Due to the viral nature of AGPL, they have hard time trying your code to decide if it is worth using. Due to copyright assignment and patent clauses, they have very hard time contributing anything back.
What more or less works is GPL + commercial license, the freemium model. You need to get enough free users on your bandwagon to show corporate users that the code is worth trying, and maybe paying for. You need to get corporations hire you to provide support and develop special features they need in the paid tier.
Not that this problem is completely solved, but likely you heard about e.g. MySQL or Nginx who use the freemium model.
As a separate point, it's odd that anyone would use a license that they "don't fully understand," when (presumably) they would hold themselves to a higher standard of understanding the behavior of libraries they uses in their software itself. Is it irrational to consider this, at the very least, an indication of lack of attention to detail, and a tremendous red flag?
Oh.
> I’ve done a ton of open source work over the course of my career. Companies have used that work to generate income for themselves. Inevitably, I’ve ended up supporting that software on those companies’ behalf for free and that is not sustainable long term.
This is totally 100% true and understandable. Unfortunately, a lot of devs are going to go "hmm, I could battle to convince someone that can approve purchases that it's worth forking out $2k/year for this, or I could just use Celery".