From: "Michał \"rysiek\" Woźniak" <rysiek@hackerspace.pl>
To: discuss@spectrum-os.org
Subject: Re: Comparison to Qubes OS
Date: Mon, 15 Jun 2020 14:06:15 +0000 [thread overview]
Message-ID: <3f3cd409-2501-2718-1198-25f2e8c79c83@hackerspace.pl> (raw)
In-Reply-To: <159222865448.15924.2059679729330578851@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 2223 bytes --]
Hey,
On 6/15/20 1:44 PM, infokiller wrote:
> Michael Raskin wrote:
>>> resources than Qubes'. I mean, if the Qubes folks
>>> could fix these issues without a
>>> huge effort, even if it
>>> meant rewriting all the inter-VM communication tools, they probably would. If they
>>> didn't, I assume this is because this is just a huge undertaking (as is the whole
>>> project), and they're busy with other work which has higher priority. I would assume
>>> that you will end up in exactly the same situation. Note that SpectrumOS is going
>>> to make tradeoffs that are complete non-starters for Qubes.
>>> True, but I'm not sure this applies to making GUI tools less buggy, or having better
>>> documentation for CLI tools.
>> Yes, it does apply. SpectrumOS is willing to accept quite a bit more of external code with
>> good in-the-wild track record inside the trusted code base,
>> at least for _most_ tasks. So where Qubes needs to reimplement something with a completely
>> different design (allowing minimisation of TCB), Spectrum
>> can (at least in the beginning, sometimes grudgingly) take the closest thing in existence
>> and add only critically missing parts.
> I disagree.
And you have all the right to.
However, it seems to me that the reasons behind SpectrumOS being done the way
it's done have been pretty extensively explained and documented in this thread.
At this point the discussion seems to focus on back-of-a-napkin estimates
regarding what is a more effective way of implementing certain things.
Clearly your estimates are different than those of others responding in this
thread. You might be right and we might be wrong, but the only way to test that
is to start implementing things one way or the other.
SpectrumOS made their estimations and arrived at a decision to do things one
particular way. You may disagree this is the best way to do things, but I feel
at this point a better way of making your point would be for you to start
implementing things the way you believe is more effective.
SpectrumOS is basically a one-person team. If you're right, you should be able
to overtake SpectrumOS development pretty quickly.
--
Best,
r
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2020-06-15 14:06 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
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 [this message]
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=3f3cd409-2501-2718-1198-25f2e8c79c83@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).