public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Hoël Bézier" <hoelbezier@riseup.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] mirror storage growth rate
Date: Fri, 15 Mar 2024 16:40:59 +0100	[thread overview]
Message-ID: <ZfRsDFfwzbCbZ32_@sparta> (raw)
In-Reply-To: <a3de2829a0abe5ded3d5b57e4ad2f2af346eb0fc.camel@gentoo.org>

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

>I guess the simplest explanation is that software is growing larger,
>and in the end we should be expecting to adding new packages faster than
>removing dead ones.  Add to that the grotesque inefficiency of modern
>programming languages such as Go and Rust.

Wouldn’t initiatives like rust-dev[0] help with that? I know that Debian is 
also packaging Rust this way[1].

[0]: https://wiki.gentoo.org/wiki/Project:Rust/rust-dev
[1]: https://wiki.debian.org/Rust

Hoël

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

  reply	other threads:[~2024-03-15 15:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15  8:06 [gentoo-dev] mirror storage growth rate Jaco Kroon
2024-03-15 12:05 ` Michał Górny
2024-03-15 15:40   ` Hoël Bézier [this message]
2024-03-15 16:15     ` Maciej Barć
2024-03-15 18:21 ` Andreas K. Huettel

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=ZfRsDFfwzbCbZ32_@sparta \
    --to=hoelbezier@riseup.net \
    --cc=gentoo-dev@lists.gentoo.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