🇨🇦 tunetardis

  • 1 Post
  • 69 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle

  • About a year ago, there was a boycott on the Loblaws supermarket chain in protest of their boasting record profits at a time when grocery inflation was out of control. It lasted about a month before kind of fizzling out.

    But I think by comparison, this buy Canadian movement has legs. It’s a major nationwide shift in people’s spending habits. And the key word here may be habits. Let’s say for argument’s sake that after 4 years of Trump, a new administration comes in and repeals all the tariffs. By that time, people will have settled into alternate brands across a wide range of consumer goods, and it may be difficult to convince them to switch back again. There’s a certain inertia in human behaviour. So the effects of this could potentially go on quite a bit longer than the tariff war.




  • Digital services tend to be an area where the US enjoys huge trade surpluses. If that pandora’s box is opened, it’s going to be really bad for the tech giants when retaliatory steps are inevitably taken. I thought this was why Trump was trying to keep the tariff war focused on material goods?

    I know in Canada, FB stopped serving news when they refused to contribute to a government fund to help the struggling domestic journalism industry which they were scraping content from with reckless abandon. Personally, I’m happy to see one less stifling algorithm-fed echo chamber. It’s like a breath of fresh air.



  • Yeah I agree. I came across the article as I like to read up on what’s going on with BRICS countries as that seems like something worth keeping an eye on. But the lack of confirmation is troublesome. Even something like a giant trade deal with China that would give them some standing to call Trump’s bluff would lend some credibility. It could be that this was threatened during negotiations and someone jumped the gun to say it’s now policy? If I see any more about it one way or another, I will update the post.









  • 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
    ·
    10 months 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.



  • This reminds me of when I had to roll my own dynamic memory allocator for an obscure platform. (Something I never want to do again!) I stuck metadata in the negative space just before the returned pointer like you say. In my case, it was complicated by the fact that you had to worry about the memory alignment of the returned pointer to make sure it works with SIMD and all that. Ugh. But I guess with strings (or at least 8-bit-encoded strings), alignment should not be an issue.


  • 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.