patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Alyssa Ross <alyssa.ross@unikie.com>
To: Vadim Likholetov <vadim.likholetov@unikie.com>
Cc: devel@spectrum-os.org
Subject: Developer-friendliness
Date: Tue, 6 Dec 2022 20:31:48 +0000	[thread overview]
Message-ID: <20221206203148.osqflgwjty2wmr5s@x220> (raw)
In-Reply-To: <DDE55C43-B3E3-44B6-8BDD-C282FACD7EE5@unikie.com>

[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]

On Tue, Dec 06, 2022 at 10:19:58PM +0200, Vadim Likholetov wrote:
>
>
> > On 6 Dec 2022, at 19:10, Alyssa Ross <alyssa.ross@unikie.com> wrote:
> >
> > (Adding tmux to the VM in development to be able to hop between multiple
> > shell sessions would be a reasonable thing to do, of course.)
>
> 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.)

And BTW, thanks so much for spending all this time engaging with this
stuff!  The project will be much better off for your efforts. :)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-12-06 20:31 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         ` Alyssa Ross [this message]
2022-12-07  7:46           ` Developer-friendliness vadik likholetov
2022-12-06 20:59         ` Developer-friendliness Michael Raskin
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=20221206203148.osqflgwjty2wmr5s@x220 \
    --to=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).