From: Michael Raskin <7c6f434c@mail.ru>
To: alyssa.ross@unikie.com, vadim.likholetov@unikie.com
Cc: devel@spectrum-os.org
Subject: Developer-friendliness
Date: Tue, 06 Dec 2022 21:59:22 +0100 [thread overview]
Message-ID: <E1p2etr-008JBI-72.7c6f434c-mail-ru@smtp16.i.mail.ru> (raw)
In-Reply-To: <20221206203148.osqflgwjty2wmr5s@x220>
>> It may sound like religious point of view, but I strongly believe
>> that developers is the number one priority to support with Spectrum OS
>> now — as easier and friendlier the OS will be to the developer as
>> faster it will be delivered to the common users. It, from my point of
>> view, includes two main aspects — ease of development giving the
>> developer proper “bricks” (well encapsulated OS services) and
>> examples, that coveres main use cases/use patterns of the operating
>> system.
>
>Yes, that's a compelling argument. I wonder if it would make sense to
>add some special configuration option for development, that would enable
>extra development tools and other goodies? (I often find myself adding
>strace…)
>
>(I think they probably shouldn't be present by default, because then it
>could be difficult to be sure nothing was depending on them in future
>when it came time to remove them. But something that any given
>developer could set once and then always have developer stuff available,
>and toggle off when they wanted to test a production build, could make
>things a lot nicer.)
Well, one could have VM generator functions, so that you can easily
generate a development-like VM or a reasonable-setup like VM or minimal
VM (without D-Bus etc.), and so the developers can just use the dev
version and always get the good stuff included?
>And BTW, thanks so much for spending all this time engaging with this
>stuff! The project will be much better off for your efforts. :)
next prev parent reply other threads:[~2022-12-06 20:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 22:42 Firefox appVM patches and appVM refactoring Vadim Likholetov
2022-12-06 11:42 ` Alyssa Ross
2022-12-06 13:56 ` Vadim Likholetov
2022-12-06 15:18 ` Alyssa Ross
2022-12-06 15:20 ` Alyssa Ross
2022-12-06 15:57 ` Vadim Likholetov
2022-12-06 17:10 ` Alyssa Ross
2022-12-06 20:12 ` Vadim Likholetov
2022-12-06 20:25 ` Alyssa Ross
2022-12-07 7:41 ` vadik likholetov
2022-12-06 20:19 ` Vadim Likholetov
2022-12-06 20:31 ` Developer-friendliness Alyssa Ross
2022-12-07 7:46 ` Developer-friendliness vadik likholetov
2022-12-06 20:59 ` Michael Raskin [this message]
2022-12-06 21:14 ` Developer-friendliness Alyssa Ross
2022-12-06 22:05 ` Developer-friendliness Michael Raskin
2022-12-07 8:04 ` Firefox appVM patches and appVM refactoring Ville Ilvonen
2022-12-07 11:09 ` vadik likholetov
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=E1p2etr-008JBI-72.7c6f434c-mail-ru@smtp16.i.mail.ru \
--to=7c6f434c@mail.ru \
--cc=alyssa.ross@unikie.com \
--cc=devel@spectrum-os.org \
--cc=vadim.likholetov@unikie.com \
/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.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
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).