From: "C.W. Epema" <keesepema@linuxmail.org>
To: libreplanet-discuss@libreplanet.org
Subject: Re: 7 Reasons to Avoid Open Source?
Date: Sun, 3 Dec 2017 15:29:16 +0000 [thread overview]
Message-ID: <20171203152916.c758df02740a857ab20bc7ca@linuxmail.org> (raw)
In-Reply-To: <B8144FCF-7ACB-48D3-A323-ED6EA5C926BA@thomas-harding.name>
I tried to post a comment, however a spam filter blocked my response.
My reaction was:
"
So, if Open Source or Free Software does not comply quality standards, according to your 'investigation', what will?
Closed Software?
Anyone is able to verify quality and integrity of Open/Free software. In contrast to closed software.
My suggestion is that you should take part in open projects, to suggest quality improvements, in stead of posting fake and possibly paid comments about one of the finest things humankind has come with: sharing knowledge
"
Regards,
Kees Epema
On Sun, 03 Dec 2017 11:44:43 +0100
Thomas Harding <tom@thomas-harding.name> wrote:
> Le 3 décembre 2017 05:45:12 GMT+01:00, Mary-Anne Wolf <mgwmgw@comcast.net> a écrit :
> >This
> >https://www.designnews.com/content/7-reasons-open-source-software-should-be-avoided/100858102757881
> >says, "As much potential as open source software can provide, there are
> >several reasons why embedded software developers should avoid it like
> >the plague."
> >
> >
> >You would not be surprised that the reasons generally do not impress
> >me. Somebody who can express it better than I do needs to respond.
> >Actually, a first person already has, but maybe more than one person
> >should.
> >
> 8 - The software is not mathematically proven.
>
> 9 - Software would likely never pass the tests in order to qualify as EAL 7+++, which is mandatory for a domestic grade standalone heating radiator thermostat (with display *and* clock!). Moreover youl'll had to afford the lab.
>
> >"Help! Somebody on the internet is wrong!" :-)
>
>
> --
> Je suis née pour partager, non la haine, mais l'amour.
> Sophocle, Antigone, 442 av. J.C.
>
> _______________________________________________
> libreplanet-discuss mailing list
> libreplanet-discuss@libreplanet.org
> https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
--
Groet,
Kees Epema
Rosa Spierweg 20
9408EV Assen
T: 06 100 66 878
M: keesepema@linuxmail.org
Protect your privacy and encrypt your messages.
Add my key to your keyring:
PGP key: http://osmigratie.nl/keesepema.asc
_______________________________________________
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 14:29 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
2017-12-03 10:44 ` Thomas Harding
2017-12-03 12:32 ` N.Thomas
2017-12-03 15:29 ` C.W. Epema [this message]
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=20171203152916.c758df02740a857ab20bc7ca@linuxmail.org \
--to=keesepema@linuxmail.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).