From: David Lang <david@lang.hm>
To: joe@hamelin.us
Cc: David Lang <david@lang.hm>,
Frantisek Borsik <frantisek.borsik@gmail.com>,
Hesham ElBakoury <helbakoury@gmail.com>,
5grm-satellite@ieee.org,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Re: Ambani Launches 15 Billion Dollars Space War Against Starlink
Date: Tue, 30 Jun 2026 00:51:39 -0700 (MST) [thread overview]
Message-ID: <2n1s314p-768o-q2n1-0nn9-7q1n37rr60r2@ynat.uz> (raw)
In-Reply-To: <CAO0-hXY=EZeCsOtKajUA5YRqNOTwcD8ujVonumRn2=AZ7jgovA@mail.gmail.com>
Joe Hamelin wrote:
> On Sun, Jun 21, 2026 at 12:55 PM David Lang via Starlink <
> starlink@lists.bufferbloat.net> wrote:
>
>>
>> I think it is going to depend a lot on who their launch provider is and who
>> their satellite manufacturer is.
>>
>
> Arianespace (a JV of my company and Airbus) just launched 36 Leo sats last
> week.
My point is that SpaceX competitors are paying 3-4x as much for launch services
(SpaceX list prices are noticably lower than any competitor, and their launch
costs are 1/4 to 1/3 their list prices)
And if the satellites are build the traditional way, they will cost many times
what starlink satellites do as well.
so if your costs to get into orbit are ~4x higher for a similar capacity
satellite, you are going to have a very hard time being competitive.
the satellite industry got into the habit of thinking "launch is expensive, the
cost of the satellite is trivial in comparison, so we can make the satellite
more expensive to try and add to the reliability" and "satellites are really
expensive, so the launch costs don't matter much". It took Elon firing the
Starlink satellite construction management to break the team out of that
mindset, have these other companies learned the lesson? or are they going to
continue the old ways?
I can say that the fact that they all are building traditionally shaped
satellites that are deployed one or two at a time from a central tower (wasted
mass and space) with each satellite needing it's own deployment mechanism (more
complexity and wasted mass) vs the starlink flat-pack/spin-and-release or
starship pez-dispensor approaches does not give me any reason to believe that
they have learned the 'cattle not pets' approach to satellite services.
It's possible that some have, but I don't see it yet.
David Lang
next prev parent reply other threads:[~2026-06-30 7:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-21 18:11 [Starlink] Ambani Launches 15 Billion Dollars Space War Against Starlink Hesham ElBakoury
2026-06-21 19:03 ` [Starlink] " Frantisek Borsik
2026-06-21 19:11 ` Inemesit Affia
2026-06-21 19:24 ` Frantisek Borsik
2026-06-21 19:55 ` David Lang
2026-06-22 0:01 ` Joe Hamelin
2026-06-30 7:51 ` David Lang [this message]
2026-06-30 8:07 ` Inemesit Affia
2026-06-30 10:35 ` David Lang
2026-06-22 1:28 ` David Collier-Brown
2026-06-30 6:01 ` [Starlink] Partial network outage. Seems like DNS. Any active probes see anything? Inemesit Affia
2026-06-30 6:02 ` [Starlink] " Inemesit Affia
2026-06-30 6:57 ` [Starlink] A new radome colour for Starlink Ground/Earth station Inemesit Affia
2026-06-30 16:47 ` [Starlink] " J Pan
2026-06-30 16:50 ` [Starlink] Re: Partial network outage. Seems like DNS. Any active probes see anything? J Pan
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=2n1s314p-768o-q2n1-0nn9-7q1n37rr60r2@ynat.uz \
--to=david@lang.hm \
--cc=5grm-satellite@ieee.org \
--cc=frantisek.borsik@gmail.com \
--cc=helbakoury@gmail.com \
--cc=joe@hamelin.us \
--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