From: "Andrés Muñiz Piniella" <a75576@alumni.tecnun.es>
To: libreplanet-discuss@libreplanet.org
Subject: Re: 7 Reasons to Avoid Open Source?
Date: Sun, 03 Dec 2017 08:05:05 +0000 [thread overview]
Message-ID: <0316E556-652B-4C09-BEA2-6172AA75F6DA@alumni.tecnun.es> (raw)
In-Reply-To: <174656503.565057.1512276313403@connect.xfinity.com>
El 3 de diciembre de 2017 04:45:12 GMT+00:00, Mary-Anne Wolf
>Actually, a first person already has, but maybe more than one person
>should.
>
>
Actually I would say less is more. The answer is short and to the point, if I answer I would probably sound like a troll. Plus, it will give it more web traffic than it deserves. I think. But thank you for sharing!
The absolute best solution would be to write another industry/trade article featuring a good quality faif project on the same magazine. Addressing point by point the "issues" mentioned on this article but without mentioning it. The magazine does ask for content.
I normally just read one or two comments anyway, if there is only one as reasonable and measured as this one, without a response from the original poster that speaks volumes to my ears.
Looking at the about page [1] it seems to me the problem is mainly with random scripts found on the internet focused on hobbies (e.g. arduino, python code on instructables or make: magazine). Professionals should exercise critical thinking when doing a cut and paste. Also, when professionals do use free (faif) software (not simply open source) AND free hardware, the industry, in my humble opinion, is be better off. Because best practice could be imitated.
The authour also mentions throughout some good points. The title is missleading, I would say using the word 'plague' is a way to bait for a click. It certainly worked for me. In the past, faif licences have also been refered to viral.
Thank you for your time!
[1] https://www.designnews.com/about
--
Richmond Makerlabs
Ham United Group
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2017-12-03 8:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 4:45 7 Reasons to Avoid Open Source? Mary-Anne Wolf
2017-12-03 8:05 ` Andrés Muñiz Piniella [this message]
2017-12-03 10:44 ` Thomas Harding
2017-12-03 12:32 ` N.Thomas
2017-12-03 15:29 ` C.W. Epema
2017-12-03 19:22 ` Michael Pagan
2017-12-04 2:12 ` Chad Larson
2017-12-04 14:51 ` Thomas Harding
2017-12-04 15:06 ` Caleb Herbert
2017-12-04 19:02 ` Chad Larson
2017-12-04 23:59 ` Thomas Harding
2017-12-04 16:20 ` Adonay Felipe Nogueira
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0316E556-652B-4C09-BEA2-6172AA75F6DA@alumni.tecnun.es \
--to=a75576@alumni.tecnun.es \
--cc=amunizp@member.fsf.org \
--cc=libreplanet-discuss@libreplanet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).