Tangentially related is NASA's open source GMAT[0] software which is more focused for calculating orbital transfers and the like. It's pretty fun to play around in.

[0] https://software.nasa.gov/software/GSC-18094-1

It's really not that simple. See this for a good explanation of why: https://taranis.ie/datacenters-in-space-are-a-terrible-horri...

It all basically boils down to: in order to dissipate heat, you need something to dissipate heat into, e.g. air, liquid, etc. Even if you liquid cool the GPUs, where is the heat going to go?

On Earth, you can vent the heat into the atmosphere no problem, but in space, there's no atmosphere to vent to, so dissipating heat becomes a very, very difficult problem to solve. You can use radiators to an extent, but again, because no atmosphere, they're orders of magnitude less effective in space. So any kind of cooling array would have to be huge, and you'd also have to find some way to shade them, because you still have to deal with heat and other kinds of radiation coming from the Sun.

It's easier to just keep them on Earth.

What you're describing is one of two mechanisms of shedding heat which is convection, heating up the environment. What the long comment above is describing is a _completely_ different mechanism, radiation, which is __more__ efficient in a vacuum. They are different things that you are mixing up.

for a square solar array of side length L, a pyramid height of 3*L would bring the temperature to below 300K, check my calculation above.

people heavily underestimate radiative cooling, probably because precisely our atmosphere hinders its effective utilization!

lesson: its not because radiative cooling is hard to exploit on earth at sea level, that its similarily ineffective in space!

that page has not a single calculation of radiative heat dissipation, seems like he pessimistically designed the satellite avoiding use of radiative cooling which forces him to employ a low operational duty cycle. Kind of a shame to be honest, given the high costs of launching satellites, his sat could have been on for a larger fraction of time...

Funny, I just started playing The Wise-Woman’s Dog yesterday—it really is excellent!

I’d also secondly endorse Dialog. It’s a really intuitive way to think about the game world as a whole without having to worry about Inform 7’s AppleScript-esque syntax. It’s also grown quite a bit since the community started their own fork: https://github.com/Dialog-IF/dialog

Even if the changes aren't "meaningful" (which it seems like they are), they still have an impact in how it makes the contributor more comfortable with working on the project. No new contributor is going to start with making massive patches without starting out with some smaller things to get a feel for working with the project.

Agreed, these seem like ideal patches to me for a first contribution. Solves a specific problem, doesn't require a lot of effort on maintainers side to review, and should give them a straightforward path to familiarise themselves with the process.

I think it's probably less frequent nowadays, but it very much does happen. This still-active lawsuit[0] was made in response to LLMs generating verbatim chunks of code that they were trained on.[1]

[0] https://githubcopilotlitigation.com [1] https://www.theverge.com/2022/11/8/23446821/microsoft-openai...

The issue is that you need an account to view the replies, not that there's a moral opposition to visiting the website (though it could be that too).

For what it’s worth, I’m definitely leaning “Apple fanboy” and have been amenable to their past UI redesigns. This is the first that I truly think is a regression, and I immediately turned on Reduce Transparency after updating.

> Not being able to hear sirens, or oncoming trucks, or cars honking their horns, or cyclists saying "on your left".

For what it's worth, it's generally thought that deaf drivers are safer drivers. See https://www.handspeak.com/learn/280/.

> fire alarms

ADA requires fire alarms to include visual alarms (as in flashing strobes) for this reason.

NoRedInk[0] also uses some Haskell in their backend, as well as Elm for most of their frontend. They've also worked some with Roc according to a blog post from a few years back; not sure if using it.

[0] https://blog.noredink.com

As someone who regularly flits between Google Sheets, LibreOffice Calc, and Numbers regularly (with my most time in Google Sheets and Numbers), and as someone who's made some extremely complicated spreadsheets in all three, I have to say I vastly prefer Numbers if I can get away with it. It has a lot of issues that can make some stuff hard fast (no array formulas is a big one), but I find it significantly easier and faster to prototype in Numbers regardless.

I think the main bit I love so much about it is having actual tables instead of the Infinite Grid that most spreadsheet software uses. You get named ranges for free, and it makes semantical sense too, among a good number of other benefits (sheet organization, refactoring, simpler styling...).

There are some really nice things that Google Sheets does, and I've done a few fancy things with App Script which isn't too bad, and I do really like QUERY though I wish it was a bit higher power. I just always find myself missing the UX of Numbers, though.