• 2 Posts
  • 139 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle









  • I suppose the regolith itself could be used as a heat sink. I don’t know what its thermal properties are like?

    But yeah, I imagine heat dissipation is a limiting factor. Everything I’ve read suggests the 1st gen reactors will put out something on the order of 10s of kilowatts, so rather modest by nuclear standards but still plenty for a nascent Moon base I imagine?


  • tunetardis@lemmy.catoWorld News@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    20 days ago

    The trouble with solar on the moon is that the day-night cycle is a month long. You have to figure out what to do during the 2 Earth weeks worth of night.

    I suppose with a polar base, you could have several solar farms strategically placed so that at least one of them is operational at any given time, but that’s a lot of infrastructure and this is early days.




  • You raise a good point that it would be nice to have more control over which group of communities you are drawing from at a given time. (Is there a way to group subscriptions and switch between them?) It’s a bit disconcerting to see 5 tech headlines and then suddenly something about the war in Ukraine or whatever. It jars my train of thought. With an RSS client, you can group feeds however you want.

    That said, my experience with RSS readers is not quite so idyllic. In the end, rather than having nicely partitioned feed groups by topic, I wind up having to separate the ones that produce content frequently but with a poor signal-to-noise from those that post once in awhile but are generally worth your time. With something like lemmy, people are helping you do the work of finding the more interesting content from that site that posts every 10 minutes.



  • Anyways, did I miss anything?

    I think the big problem in link aggregation is how to sort/prioritize content for the end user. RSS does not provide a way to do this, nor should it as far as I’m concerned. It should simply be about public content being tagged in a standardized way for any app to come along and organize it using whatever algorithm.

    A simple RSS reader has the problem that the more prolific sites will tend to flood your feed and make it tedious to scroll through miles of links. Commercial news portals try to learn your tastes through some sort of machine learning algorithm and direct content accordingly. This sounds like a good idea in theory, but tends to build echo chambers around people that reinforce their biases, and that hasn’t done a lot of good for the world to put it mildly.

    The lemmy approach is to use one of a number of sorting algorithms built atop a crowd-sourced voting model. It may not be perfect, but I prefer it to being psychoanalyzed by an AI.

    Btw there was a post from about a month ago where someone was offering to make any RSS feed into a community. I’ve subscribed to a few of them and it’s actually pretty awesome.



  • Oh, so you’re talking about text representation in an editor or something along those lines? That’s kind of a separate problem isn’t it?

    At the lowest level though, I suppose you still need to consider whether to use null-terminated segments. I think I’d still be going length + data, though I wouldn’t worry about packing down the length representation like with serialization formats. Your code will need to be highly cognizant of the length of strings and managing dynamic memory allocation all over the place, so it’s good to have those lengths quickly accessible at all times.


  • Better in what sense? I put some thought into this when designing an object serialization library modelled like a binary JSON.

    When it got to string-encoding, I had to decide whether to go null-terminated vs length + data? The former is very space-efficient, particularly when you have a huge number of short strings. And let’s face it, that’s a common enough scenario. But it’s nice to have the length beforehand when you are parsing the string out of a stream.

    What I did in the end was come up with a variable-length integer encoding that somewhat resembles what they do in UTF-8. It means for strings < 128 chrs, the length is a single byte. Longer than that and more bytes get used as necessary.