general high-level discussion about spectrum
 help / color / mirror / Atom feed
From: "infokiller ​" <joweill@icloud.com>
To: discuss@spectrum-os.org
Subject: Re: Comparison to Qubes OS
Date: Mon, 15 Jun 2020 01:59:57 -0000	[thread overview]
Message-ID: <159218639703.15924.2210454595783448015@localhost> (raw)
In-Reply-To: <fd3d5a79-da3b-43a9-f6c7-c06a928afab5@hackerspace.pl>

Michał "rysiek" Woźniak wrote:
> On 6/14/20 9:27 PM, Alyssa Ross wrote:
> >    So, why not
> > start a public discussion in Qubes' mailing list on issue
> >  tracker to figure out what is needed to accomplish Spectrum's goals?
> > 
> >  It will probably turn out that you made the right decision by starting
> >  a separate project, but at the very least:
> >  - You'll may get attention from people who can contribute to Spectrum
> >  - The issues involved with be publicly documented and searchable for
> >    future generations  
> >  I think you maybe don't appreciate just how huge an undertaking this
> >  would be.  There is so much that would have to change about how Qubes
> >  works that I think you'd end up having to reimplement most of it
> >  anyway, but you'd be doing it bit by bit, never having the opportunity
> >  to consider the system as a whole. 
> Plus, SpectrumOS does not have to deal with backwards compatibility. If QubesOS
> developers were to start implementing these changes, they would constantly have
> to deal with trade-offs between ease of implementing them and the cost of
> breaking backwards compatibility.
Well, that's what major version changes are for. Qubes 5 could change to a Nix model if they wanted without worrying much about backwards compatibility. I assume that won't happen for other reasons, like having higher priority work, and lack of experience with Nix.

> 
> >   At the end of the day I just don't believe that
> > trying to shoehorn these
> >  changes into Qubes is the best way to make progress.  It might well be
> >  valuable to try that, but even so it would make much more sense for
> >  somebody who believes in that approach to dedicate the huge amount of
> >  effort required to attempt it, rather than me.  This could be another
> >  effort that could be pursued in parallel to my work on Spectrum. 
> Very much this.
> 
> --
> Best,
> r

  reply	other threads:[~2020-06-15  2:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-12 11:06 Comparison to Qubes OS joweill
2020-06-12 11:28 ` Michał "rysiek" Woźniak
2020-06-12 11:54   ` infokiller ​
2020-06-12 12:02     ` Michał "rysiek" Woźniak
2020-06-13 11:19       ` Alyssa Ross
2020-06-13 11:38 ` Alyssa Ross
2020-06-14 20:19   ` infokiller ​
2020-06-14 21:27     ` Alyssa Ross
2020-06-14 22:19       ` Michał "rysiek" Woźniak
2020-06-15  1:59         ` infokiller ​ [this message]
2020-06-15  1:54       ` infokiller ​
2020-06-14 21:13   ` Michael Raskin
2020-06-15  1:33     ` infokiller ​
2020-06-15 11:38     ` Michael Raskin
2020-06-15 13:44       ` infokiller ​
2020-06-15 14:06         ` Michał "rysiek" Woźniak
2020-06-15 15:07           ` infokiller ​
2020-06-15 14:42       ` Michael Raskin
2020-06-15 15:29         ` infokiller ​

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=159218639703.15924.2210454595783448015@localhost \
    --to=joweill@icloud.com \
    --cc=discuss@spectrum-os.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 NNTP newsgroup(s).