emilengler

> It is good to know that your base64 encoding function is tested for all corner cases, but integration and behaviour tests for the external interface/API are more important than exercising an internal implementation detail.

I think that this heavily depends upon the part that is tested or not tested. For certain parts in the kernel, such as the firewall, I truly believe, that such tests cases (including corner ones) shall be present.

> The writing is on the wall. You MUST host your own code on a stand-alone website.

Because this does not prevent having the code to land on GitHub at the of the day assuming it is published under a free license.

Now it depends on how you interpret the "MUST". My logic only makes sense if you consider it to a dogmatic-like prevention.

> The larger issue is that anyone using GitHub is donating their work for re-use without attribution through Copilot.

Wrong. Lets say a GPL project is not hosted on GitHub officially. I can easily setup a mirror for it though on GitHub as the GPL doesn't prevent me from doing it...

Point is that anyone can put my work on GitHub, even if I don't want to.Assuming the project is under a free license though.

A thing I really enjoy about this guide is that it’s close to common C paradigms and practices. Many guides lack this and only show outdated ones.

And another person with the Erdős-Number 1 passed away :(

I miss "Software as a service" as a term