Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Inemesit Affia <inemesitaffia@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: [Starlink]  China launches satellites to start building the world’s first supercomputer in orbit
Date: Mon, 19 May 2025 17:44:04 +0100 (GMT+01:00)	[thread overview]
Message-ID: <b7f82fa1-81ea-4f36-9bf8-632280255a13@gmail.com> (raw)
In-Reply-To: <CAFvDQ9rN_DY886bsmqJ6a7bRuaGvSonCkqnmzUOzG6CdFoPjpA@mail.gmail.com>

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

Any talk about computing in space is a waste of space. I've always been sceptical

If you're in LEO sending the data to servers on the ground and back again doesn't add enough latency to matter. And if latency is an issue the end user devices now have enough compute.

Always think about where the heat goes.

[-- Attachment #2: Type: text/html, Size: 649 bytes --]

  reply	other threads:[~2025-05-19 16:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-19 16:04 Hesham ElBakoury
2025-05-19 16:44 ` Inemesit Affia [this message]
2025-05-19 16:52   ` Eric
2025-05-20  1:06     ` Michael Richardson

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

  List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b7f82fa1-81ea-4f36-9bf8-632280255a13@gmail.com \
    --to=inemesitaffia@gmail.com \
    --cc=starlink@lists.bufferbloat.net \
    /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