public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: m.2 nvme stick not what I was expecting at all.
Date: Tue, 25 Feb 2025 14:07:35 -0000 (UTC)	[thread overview]
Message-ID: <vpkir7$si0$1@ciao.gmane.io> (raw)
In-Reply-To: f2be8928-fc09-471a-8d1a-e877bd290551@youngman.org.uk

On 2025-02-25, Wols Lists <antlists@youngman.org.uk> wrote:

> Champagne or Coca-Cola?
>
> New tech generally costs double the price for double the quantity, be it 
> hard drive capacity, chip speed, whatever.
>
> Older tech tends to be a similar price regardless of capacity, the bulk 
> of the cost is in the packaging and transport.
>
> Hence my name for the two price brackets :-)
>
> Like you, I tend to look for the cheapest Champagne-price stuff I can 
> find...

I tend to buy last year's Champagne (motherboards, CPUs, SSDs,
whatever). Sometimes even a bit older.

 1. Once there are one or two newer "Champagne" models out, the price
    of last year's tends to be pretty reasonable. And the performance
    difference is rarely significant.

 2. A year provides time for other people to find the bugs, for those
    bugs to get fixed, for howto documentation to get updated, and for
    hardware feature support to get finished up.

--
Grant





  reply	other threads:[~2025-02-25 14:08 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 18:58 [gentoo-user] m.2 nvme stick not what I was expecting at all Dale
2025-02-24 19:20 ` Jack
2025-02-24 19:49   ` Dale
2025-02-24 19:40 ` Mark Knecht
2025-02-24 19:41 ` Rich Freeman
2025-02-24 19:53   ` Dale
2025-02-24 20:00     ` Rich Freeman
2025-02-24 20:34       ` Dale
2025-02-24 20:02 ` eric
2025-02-24 20:11   ` Mark Knecht
2025-02-24 20:44     ` Dale
2025-02-24 22:48       ` Frank Steinmetzger
2025-02-25  3:56         ` Dale
2025-02-25 10:08           ` Michael
2025-02-25 11:00             ` Dale
2025-02-25 11:16               ` Michael
2025-02-25 15:57                 ` Dale
2025-02-25 17:05                   ` Rich Freeman
2025-02-25 19:00                     ` Michael
2025-02-25 19:18                       ` Rich Freeman
2025-02-25 20:39                         ` Michael
2025-02-25 22:16           ` Frank Steinmetzger
2025-02-25 14:48         ` Peter Humphrey
2025-02-25 17:00           ` Michael
2025-02-24 22:13   ` Frank Steinmetzger
2025-02-25  4:20     ` Dale
2025-02-25  8:18       ` Wols Lists
2025-02-25 14:07         ` Grant Edwards [this message]
2025-02-25  8:20 ` Wols Lists
2025-02-25 11:09   ` Dale
2025-02-25 12:26 ` Dale
2025-02-25 15:04   ` Rich Freeman
2025-02-25 15:32     ` Dale
2025-02-25 16:29       ` Rich Freeman
2025-02-25 17:26         ` Dale
2025-02-25 17:41           ` Rich Freeman
2025-02-26 14:43             ` Dale
2025-02-26 16:38               ` Michael
2025-02-26 20:34                 ` Dale
2025-02-26 20:48                   ` Mark Knecht
2025-02-25 20:19     ` Wol
2025-02-25 20:21       ` Michael
2025-02-25 21:34         ` Frank Steinmetzger
2025-02-26  7:52           ` Wols Lists
2025-02-26 16:44             ` Michael
2025-02-26 18:03               ` Wol
2025-02-26 18:05                 ` Rich Freeman
2025-02-26 18:42                   ` Wol
2025-02-26 19:26                     ` Rich Freeman
2025-02-26 19:47                       ` Wols Lists
2025-02-26 19:56                         ` Rich Freeman
2025-02-26 21:25                           ` Wol
2025-02-26 22:37                             ` Michael
2025-02-26 16:41           ` Michael
2025-02-28  5:43 ` Dale
2025-02-28 16:40   ` [gentoo-user] " Grant Edwards
2025-03-02 16:01     ` Dale
2025-03-02 22:06       ` Frank Steinmetzger
2025-03-02 22:39         ` Dale
2025-03-03  3:01         ` Grant Edwards

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='vpkir7$si0$1@ciao.gmane.io' \
    --to=grant.b.edwards@gmail.com \
    --cc=gentoo-user@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