Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] video about open source & endurance
Date: Mon, 16 Mar 2020 09:10:08 +0000
Message-ID: <CAPweEDwwty3tfRk-ZWeruTRE7TiQ6j4FybQct5RXeN=t1=2y5g@mail.gmail.com> (raw)
In-Reply-To: <CAC2bXD5N2wmmunUF38Dj4goMdN7O72wJhOXz_eR1h98FBiYL4w@mail.gmail.com>

On Mon, Mar 16, 2020 at 1:30 AM Jacob Lifshay <programmerjake@gmail.com> wrote:

> no, that's correct. it's talking about how things from back then were
> designed to last a long time and how modern proprietary computing stuff is
> not and how open source software is more likely to last a long time.

i know someone who does long-term support on hardware designs.   20
years and above.

he *only* uses software libre PCB CAD packages.

why?

because he takes the *entire* source code - of the entire operating
system - not just the PCB CAD packages (KiCAD usually) - the entire
*operating system* - snapshotting absolutely everything.

why?

because in 15 years time, the way that modern computing is going, the
possibility of being able to successfully run that PCB CAD software,
developed 15 years ago, and fix any PCB issues for the customer, is
extremely remote bordering on negligeable.

and that's even in the open source community.

you will also be keenly aware that the open source community
completely fails to respect and honour "version compatibility and
upgradeability".

so do not buy the kool-aid that open source is and will be
"compatible".  yes it will be around, however the chances of being
able to successfully run even a version of a tool from 6 months ago
let alone 15 years is extremely borderline.

l.

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

      reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-15 23:05 Jacob Lifshay
2020-03-16  1:24 ` Immanuel, Yehowshua U
2020-03-16  1:29   ` Immanuel, Yehowshua U
2020-03-16  1:30   ` Jacob Lifshay
2020-03-16  9:10     ` Luke Kenneth Casson Leighton [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPweEDwwty3tfRk-ZWeruTRE7TiQ6j4FybQct5RXeN=t1=2y5g@mail.gmail.com' \
    --to=lkcl@lkcl.net \
    --cc=libre-riscv-dev@lists.libre-riscv.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

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git