News for hackers. Stuff that matters.
Re:GCC licence change by shmerl on Friday March 24, 2017 @12:59AM (#13946715)
> Everyone deserves access to C technology without restriction, especially as rust makes inroads.

What? Is this whole letter some form of sarcasm?

Re:GCC licence change by ecma on Friday March 24, 2017 @01:02AM (#13946729)
Yes, see https://marc.info/?t=149028609000002&r=1&w=2 for some context. One of the other comments summarised why this is funny.
Re:GCC licence change by rurban on Friday March 24, 2017 @08:42AM (#13948490)
Only very few find this funny. This is no joke. This is a serious death treat towards LibreSSL. Theo reacted with a satire. But not a funny one.
Re:GCC licence change by ecma on Friday March 24, 2017 @01:39PM (#13950680)
Pretty uncharitable read of what I meant by "funny" really. Satire can be amusing without invalidating the referenced issue. Don't get so hung up on the issue that you can't laugh about things too.
Re:GCC licence change by geofft on Friday March 24, 2017 @11:43AM (#13949661)
What prevents LibreSSL from being under an Apache 2.0-compatible license?

(Also, what prevents LibreSSL from replying with "This is great, but can we get dual MIT/Apache 2.0"?)

Re:GCC licence change by rurban on Saturday March 25, 2017 @05:54AM (#13954810)
Dual licensing seems to be the best solution, yes. The license specialists need to come up with a solution. I'm not one
Re:GCC licence change by geofft on Friday March 24, 2017 @01:02AM (#13946726)
Yes. See https://marc.info/?l=openbsd-tech&m=149028593819547&w=2 (and the HN discussion about the OpenSSL license change) for the context of the sarcasm.