3 ms·
Yea I spend 99% of time actually working on the product, but I have been also thinking about this recently as once you choose a license it has long lasting cons
by dsanchez97 5y ago
Yea I spend 99% of time actually working on the product, but I have been also thinking about this recently as once you choose a license it has long lasting consequences and is hard to change (i.e. Elasticsearch). Figured this thread would be a good place to have a discussion though.
- bawolff 5y agoThat's really only because elastic was opensource, benefited greatly from that, and then changed their mind when it was no longer convinent. I assume you are not making it open source if you are considering patenting it. Much of the complications of the elastic search case wouldn't arise in the proprietary software case.
- breck 5y agoI’d say go public domain. SQLite did. Eats more and more of the DB world every year. The web is public domain. Don’t need to explain that. So is tcp/ip. the great ones are public domain. GPL et al are a clever hack to weaponize copyright laws against themselves, but at the end of the day the solution we need is an amendment repealing Article I, Section 8 clause 8.
- abhinav22 5y agoBut isn’t PostgreSQL and (sorry if I got the name wrong) MariaDB also open source? I think the success of SQLite is the small size / no installation, but I agree it could only become as popular as it currently is due to its open source nature.
- zhouyisu 5y agoSQLite is good and open source. I've tried MariaDB on a Python project. The connector has bugs very hard to debug. I tried to download the python source, C++ source and failed to locate the bug. I tried to add issue but find nowhere to report. Finally I give up and use MySQL instead. It works like a charm. Open source adds value, but IMHO being good is first priority.