From: "Michał \"rysiek\" Woźniak" <rysiek@hackerspace.pl>
To: discuss@spectrum-os.org
Subject: Re: Comparison to Qubes OS
Date: Sun, 14 Jun 2020 22:19:45 +0000 [thread overview]
Message-ID: <fd3d5a79-da3b-43a9-f6c7-c06a928afab5@hackerspace.pl> (raw)
In-Reply-To: <87h7vdqqw4.fsf@alyssa.is>
[-- Attachment #1.1: Type: text/plain, Size: 1562 bytes --]
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.
> 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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2020-06-14 22:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 11:06 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 [this message]
2020-06-15 1:59 ` infokiller
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=fd3d5a79-da3b-43a9-f6c7-c06a928afab5@hackerspace.pl \
--to=rysiek@hackerspace.pl \
--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).