From: David Lang <david@lang.hm>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] a bit more starship news (David Lang)
Date: Tue, 2 May 2023 11:10:51 -0700 (PDT) [thread overview]
Message-ID: <oo388714-q77o-33r2-32p8-q3029133p409@ynat.uz> (raw)
In-Reply-To: <1683044852.771727663@apps.rackspace.com>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
On Tue, 2 May 2023, David P. Reed via Starlink wrote:
> So, side note:
>
> Why does SpaceX "report a profitable quarter" and not release its full historical book of accounts? And why would someone on this list cite that number alone? (Any professional investor in Silicon Valley would be unimpressed - you can make a quarter look profitable by really simple games).
I mentioned it in response to the claim that Starlink was not viable, losing
money (or something to that effect)
There has been the suggestion that SpaceX could spin off the Starlink into a
separte business, that could then go public. SpaceX execs have said that would
not happen before it was profitable, so reporters have been hounding the execs.
As a result Gwen mentioned in an interview that they were at or near the point
that it is profitable.
There is no reason why they should have to release all their finances in such a
situation (much as we would love to see them)
David Lang
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2023-05-02 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5.1683043202.27535.starlink@lists.bufferbloat.net>
2023-05-02 16:27 ` David P. Reed
2023-05-02 17:17 ` Dave Taht
2023-05-02 18:10 ` David Lang [this message]
2023-05-02 19:53 ` 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=oo388714-q77o-33r2-32p8-q3029133p409@ynat.uz \
--to=david@lang.hm \
--cc=dpreed@deepplum.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