Now, we all much admire the Richard Stallman mindset and the libre/commons ideals of GNU GPL folks, they are the ones who pioneered the open source foundations by giving us things like core utils, emacs, gcc, etc. at a time when proprietary solutions were having a field day with absolutely zero competition.

However, the GNU GPL software license has a few practical problems when it comes to development of web apps. I came across these while developing a PHP web framework recently. I had initially considered GPL v3 but I will have to go with a permissive license like MIT or Apache due to these issues:

1. The GPL applies to your entire software as a whole including derivative works. Now what constitutes a derivative work is often highly technical but not even an attempt has been made in GPL to clarify that. That question has been left vague for some reason which is never good from a legal perspective.
2. In my case, the two require files are in the core directory while a plain index.php lives in the root for the user to override. This index.php is included as a template or stencil which the framework's user is supposed to override with their own code. In GPL lingo, this might well cause it to be a derivative work and that will require them to "contribute" those changes back to me which doesn't make any sense at all! There needs to be an exception for included sample or example files for which the GPL shouldn't apply.
3. There is also a problem with GPL due to the nature of web or Internet. Another app I am developing is a bit heavy on JavaScript and contains static *.js and *.css files. The mere running of the app in a web browser will cause these files to be "distributed" through the <link> and <script> tags. From GPL perspective, this becomes a technical violation as no GPL license had accompanied this distribution. And in case you minify or compress your JavaScript or stylesheets for efficiency (which is a very common practice), this violation becomes even more grave as you're technically distributing GPLed source in an obfuscated form!

The GPL badly needs to be upgraded for these scenarios. Until then, it remains a good use case for desktop or console apps which run directly on your computer and usually have a clearer boundary of what constitutes a distribution and/or derived work.

I'm talking about those who host their blogs statically on Github Pages and elsewhere, the small peasants of the Interwebs who collectively make up the biggest portion of it and make its wheels churn with their content and toil.

All that negativity I'm seeing towards Disqus is baseless. They criticize it for showing ads and being less privacy friendly but then which technology today isn't? Name me one company from Big Tech or Silicon Valley which actually respects their user's privacy in practice, not just words. You'll be left scratching your heads for a long time but no name will come out.

And I also keep hearing about these "self hosted" alternatives like Commento but none of them have gained any traction. Building and implementing a commenting system isn't easy even though CMS like Wordpress try their best. Unless you implement social OAuth logins like Github or Google, not many folks will like to interact on your site by singing up for a whole new site account, especially true if you're a small blogger who has just started. And managing all the data communication between the frontend and backend isn't easy.

With Disqus, we get this whole setup and workflow readymade with nice looking dashboard and all, and that too for gratis, not a dime to pay! Then why shouldn't a blogger use it, I'm yet to hear any justifiable answer to this question.