I’ll note, since it is supremely interesting to me, that Starship is able to communicate with the ground during its whole reentry due to its sheer size and ability to connect with Starlink satellites. I assumed loss of signal due to reentry was a given for any spaceship!
Shuttle in its last days had antennas that protruded outside the plasma just enough for telemetry. Apollo and Artemis reentry are also direct entry from Lunar-Earth transfer orbit using ablative heat shields, so the plasma would be hotter and thicker than suborbital Starship shots with Shuttle style ceramic tiles.
I'm pretty sure it did not stick anything through the plasma sheet- that is impossible. You would eithe melt the thing or just shift the plasma sheet a bit. It forms as air is compressed on contact, simple as that.
What IIRC was actually done was that some antennas were placed on the back of the shuttle & its size was big enough that the plasma bubble would not fully envelope it - it would be open up to space. And that antenna on the back would communicate with TDRS satellites through this gap, enabling contact through the whole re-entry.
Starship does basically the same, just with Starlink satellites instead of TDRS.
Would this capsule had been been able to communicate if it was integrated with starlink or is the size more important? I'd imagine if they could have achieved communication via Starlink they would have done it, but just curious.
It's a function of the shape. On a capsule-sized spacecraft, the ionized plasma completely surrounds the craft, so no radio communications can get in or out. For an oblong-shaped spacecraft, like the Space Shuttle or Starship, the descent tends to be angled such that you have a "hole" in the plasma you can get a signal through.
No, the plasma forms a teardrop shape around small craft like Orion, completely cutting off radio comms. Larger craft like starship or the shuttle which have a roughly cylindrical shape (vs Orion’s circular cross section) aren’t fully enclosed by the plasma. The shuttle had a transmitter attached to its tail for later flights, which could send back telemetry during re-entry.
"Sprint accelerated at 100 g, reaching a speed of Mach 10 (12,000 km/h; 7,600 mph) in 5 seconds. Such a high velocity at relatively low altitudes created skin temperatures up to 6,200 °F (3,400 °C), requiring an ablative shield to dissipate the heat. The high temperature caused a plasma to form around the missile, requiring extremely powerful radio signals to reach it for guidance. The missile glowed bright white as it flew."
Awesome, thank you! I wonder if some kind of very long-tethered deployed antenna could enable this for the capsule or if the ratio of long-enough-to-work vs thick-enough-to-not-burn-off-completely just doesn't work. Time to read about the shuttle.
Also Orion and other capsules fall like a rock (steep reentry profile ) compared to shuttle/starship, which intentionally slow down the reentry and kinda glide (ballpark 10min with capsules compared to 30min with shuttle/starship).
tl;dr: capsules get fully enveloped in plasma due to their shape, size and reentry profile
The space shuttle, too, was able to communicate. I imagine the smaller the craft the smaller the angle you can "speak" out of and, below a certain size, it just doesn't work.
This is one of the biggest issues with DnD in general. It's also one of the reasons behind the simplicity of the Shadowdark[1] RPG.
Shadowdark does not only have much simpler (and fewer) rules, there's also a lot less world building. This encourages the DM and the players to create their own fantasies, rather than adhering to the races described in the (MASSIVE) DnD manual.
The old stalker games run on the X-Ray engine (the mods on a modified OSS version of it). In my experience they've always worked pretty well, though the games are quirky in general.
Putting it in the hands on the GNOME foundation will just result in a lot of new soon-to-be-mandatory APIs and numerous configuration variables with only one allowed value.
Yeah it's all a bit complex (just like the US tax code, I suppose). MZLA (which makes Thunderbird) is a subsidiary of the Mozilla Foundation. The Mozilla Corporation (which makes Firefox) is also a subsidiary of the Mozilla Foundation. In practice, this means that the people running Firefox day-to-day aren't the people running Thunderbird day-to-day, although of course they do talk, and technology choices made in Firefox can and do effect Thunderbird, just like they effect e.g. Zen Browser or Tor Browser.
(Also, someone help a non-native speaker: I think the "effect"s above should be "affect", but for some reason that looked wrong here. Why is that?)
For their more common meanings, like in your paragraph, as a verb you want affect, and as a noun, effect. So, when in doubt, use that as a rule of thumb.
However, both have alternative meanings as the other part of speech.
Affect as a noun means emotion or disposition, and is mostly used in psychology. Your psychologist may say you have a depressed affect.
Effect as a verb means to bring about. You might say that a successful protest effected change in society.
As a verb, in addition to “have an impact on,” affect can also mean “to pretend to have,” like “she affected an air of mystery,” although this is less common.
"Effect" and "affect" are hilariously messed-up. They have subtly overlapping definitions sometimes but other times mean totally different things. They look almost the same in writing. They can sound almost the same. In spoken English, for some senses of each word we denote what we mean by changing the sound ("affect" may be pronounced almost like "effect", or, for one of its noun definitions and a related verb definition, very differently) or stress (for "effect", in some cases we hit the second syllable a little harder than other times).
The way you used "effect" here, its verb sense of "to bring about or cause" is the one that suggests itself, which isn't what you meant.
The simple way to keep the words' overlapping meanings straight, is that it's "effect" when it's a noun, "affect" when it's a verb. "Effect" can also be a verb, and "affect" can be a noun, but those definitions don't overlap.
Your post did indeed call for "affect", as you suspected.
Right, I kinda get the definitions, but usually I have no problem with them, i.e. the correct one also "sounds right" to me. I wonder why it didn't in this case?
Edit: hmm, re-reading it now, affect does look right. Weird.
I agree that it should be "affect". Affect doesn't look wrong to me:
and technology choices made in Firefox can and do affect Thunderbird, just like they effect e.g. Zen Browser or Tor Browser.
I'm no expert on the rules of english, but I think maybe it would be slightly more gramatically correct to say that "choices made in Firefox can and do have an effect on Thunderbird". I would probably have phrased it like that. Maybe that's why it looks wrong to you?
English is a bit of a bastard language IIUC, and so we accept the way you've phrased it too, but in that case it should be "affect".
I hope this helps rather than making things more confusing! ;)
Companies will often state a subsidiary is wholly owned by the ultimate parent regardless of which tier the subsidiary is at. The Thunderbird subsidiary could be under the Firefox subsidiary and the statement would still be true.
The way Vello/Masonry/Xilem are split projects is partially what got me interested in it (and in turn caused me to post it to HN), as well as the reactive architecture of Xilem.
I do believe a garbage collected interpreted language would work best for UIs.
Something like Vala (for gtk) but with a runtime/vm.
python-qt has shown to be a very strong combination. My issue with such solutions is that packaging a python application to the end-user can bloat binary size.
I also think GTK should get some credit in that space, because due to GObject introspection it's easy to interface with GTK with any language.
"causing a fire to an exterior gate" doesn't lead me to believe there was any chance of real harm.
reply