Re:WiringPi – deprecated
by stjohnswarts on Saturday August 24, 2019 @12:39AM
(#20785257)
Yeah but this guy handled it respectfully. He's even releasing a final version. So people can fork it and do what they will. You can't really blame him. 10 years is a long time to maintain something anyway.
Re:WiringPi – deprecated
by dogecoinbase on Friday August 23, 2019 @07:30PM
(#20783830)
I can't help but be reminded of the feud between xscreensaver's author and Debian maintainers.
For the curious, the post: https://www.jwz.org/blog/2016/04/i-would-like-debian-to-stop...
And the instigatory thread: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819703
Because jwz appears to have a very short fuse and at one point in time one or a group of users on HN didn't agree with him (as best as I can remember), referrals from HN are redirected to an image of a testicle.
Here is a wayback machine link to avoid the image:
http://web.archive.org/web/20190810115358/https://www.jwz.or...
JWZ has always been opinionated. I remember his epic rants on email client backends and other technical details.
lol he's escalated; before he just had text complaining about brogrammers at HN. I've wondered for years what the original beef was.
This is great.
[dead]
Re:WiringPi – deprecated
by IntelMiner on Friday August 23, 2019 @11:34PM
(#20785046)
The intent is pretty blatant
Wow, if you pull shit like that that immediately is 1 point for the other team in whatever beef he had
Links on HN were generating huge amounts of negative traffic.
I don't blame him for having a redirect.
OK, a redirect, but to a pornographic image?
Re:WiringPi – deprecated
by lallysingh on Saturday August 24, 2019 @09:55AM
(#20787137)
It's a testicle. Not people having graphic sex.
Careful, that first link redirects you to a NSFW image coming from HN
Party-pooper.
If it's not safe for your work, you need a different job.
It may surprise some people on HN, but for most people in the world, changing jobs is a hard thing to do. And yes middle managers can be that petty.
If it's safe for your work, you're probably the intended audience.
I never understood what the big deal is about the warning on the lockscreen. I've seen that before and it didn't bother me.
The FSF might also be able and willing to assist with LGPL violations. Unfortunately though this may be a case with circumstantial evidence but no proof. It also often seems that the people who most willing to disregard the (L)GPL are the ones most militantly protective of their proprietary code. It's quite sad that many developers seem to think that way.
Adding an extension like that to the GPL may be problematic because it has a clause that allows users to ignore restrictive extensions (as opposed to permissive extensions).
I can't help but think maybe:
When I read his blog post on his reasoning, I can't help but be reminded of the feud between xscreensaver's author and Debian maintainers. Debian maintainers refused to upgrade the app's version and refused to remove the 'For support contact the author's email' notice. The author's fed up with all the support emails he gets from Debian (outdated) installations' users and put in a message prompt blasting Debian. It was very ugly for both sides.
I think that there can be an extension on GPL that says, if you bundle this library and is not using the latest official version from the author, you are not allowed to include the author's contact information. If you insist on bundling the author's email with your outdated software, then you are in violation of GPL.
As for people stealing his code. Sorry to hear this. I got nothing except to try to contact EFF.