Thanks for the explanation, we always appreciate sensible feedback on our messaging and product. We are always looking for ways to get our projects more open and accepted by the traditional open-source community. Our default option when adding new products on the marketplace is GPL + a commercial license (which is the option you mention). Most developers still pick only our own proprietary licenses, since they are worried about people abusing it.

We are also in touch with the OSI for creating a 100% open-source compatible license of our own that could be officially sponsored by them. It's been a slow process, but we hope to get it done in the near future. Our own license was created with the help of copyright lawyer that has dedicated his professional life to supporting and advocating open-source. It is a compromise between closed-source / commercial and fully open-source (what we call "commercial open-source"). For many purposes, it is less restrictive than the GPL (no stipulation on releasing your source if you modify and distribute on other formats), which makes it more attractive to businesses building commercial products (for example, iOS application, which cannot use GPL).

Hope that makes sense!