144 karma · joined November 26, 2020
I see what you did there!
My answer would be -- it's important if we deem it important, whether that's rational or not. If we start from the premise that life is good, that humans in particular are the most interesting thing out there as far as we can see, then it isn't totally bizarre that we should wish for the show to continue, extend it as far as we can. In that view, being bound to the fate of our home planet seems like an arbitrary restriction.
Good idea, just needs a little more polish.
(Another thing on the TODO list is adding an optional priority score for each task, and sorting those on top of the list in all tree views.)
[x] Task
├──[x] Sub-task (1)
│ ├──[x] Sub-sub-task (2)
│ └──[x] Sub-sub-task
├──[x] Sub-task (3)
│ ├──[x] Sub-sub-task (2)
│ └──[x] Sub-sub-task
└──[x] Sub-task
by creating a link from (3) to (2). The tree command would actually omit the second occurrence of (2), since the algorithm visited each node just once.Pretty much this, unless I'm missing something. An earlier version of the program actually used DAGs, but I found it a little underconstrained. I got pretty excited when I discovered multitrees, as it seemed to be exactly what I needed the whole time.
As for the syncing, that would be really nice, but I haven't come up with an elegant way to do it yet. Suggestions welcome, if anyone has ideas!
There are tons of other people like me, and it makes me sad seeing such bitterness about a person who obviously brought a lot of good into the world.
{
paths: [
{
points: [
[10, 10], // 0
[90, 10], // 1
[90, 90], // 2
[10, 90] // 3
],
lines: [
[0, 1, 2, 3, 0] // connect point 0 to 1 to 2 to (...)
],
curves: {
0: [5, 15, 15, 5] // bezier control points for point 0 (x1, y1, x2, y2)
}
}
]
}
The downside (other than the bloat) would be when writing the code by hand, you'd have to keep track of the indices in the `points` array.SpaceX is currently developing Starship[1], which aims to increase the payload capacity to about 100,000 kg. The mass of a single Starlink v1.0 is 260 kg[2], which would be 384 sats per launch, although I've seen SpaceX talk about 400. If Starship was operational now, assuming the rate of 400 sats/launch, this would give us 103 more launches for the full constellation. For comparison, SpaceX launched 26 times in 2020, and is aiming for up to 54 launches in 2021[3].
[1] https://en.wikipedia.org/wiki/SpaceX_Starship
[2] https://en.wikipedia.org/wiki/Starlink
[3] https://en.wikipedia.org/wiki/List_of_Falcon_9_and_Falcon_He...