• 0 Posts
  • 39 Comments
Joined 1 year ago
cake
Cake day: July 27th, 2023

help-circle





  • Honestly, I don’t think this could have gone any other way. As the article says, this is the so-called “Lane 1” missions which, while they’re less important and less heavy than “Lane 2” missions, are perfectly suited to the Falcon 9, or heavy if needed. There’s no need to get a heavy rocket like Vulcan involved, especially since it’s not proven yet, so the only reason I could think of for someone else winning would essentially be as a subsidy to help SpaceX’s competition. Once Vulcan has a couple dozen successful missions under its belt I’ll expect it to be more competitive.





  • I’d be interested in setting up the highest quality models to run locally, and I don’t have the budget for a GPU with anywhere near enough VRAM, but my main server PC has a 7900x and I could afford to upgrade its RAM - is it possible, and if so how difficult, to get this stuff running on CPU? Inference speed isn’t a sticking point as long as it’s not unusably slow, but I do have access to an OpenAI subscription so there just wouldn’t be much point with lower quality models except as a toy.




  • Kessler syndrome isn’t really that much of a risk specifically with Starlink (for now at least), as SpaceX seems to be doing things right despite Musk. They’re in such low orbits that even with a catastrophic loss of control, they’ll deorbit very quickly. The real risk comes as more companies and countries try to get a piece of the megaconstellation pie. Starlink in its own seems to be fairly safe and sustainable on its own, but that may quickly change when communication for collision avoidance maneuvers needs to be international.

    Despite Musk’s well-earned reputation for being a shithead, SpaceX has this far been doing the right thing far more often than most other space companies, and while it’s certainly possible that will change, the Starlink constellation will entirely disappear very quickly without constant replenishment, so it’s not as if we’d have no chance to act if they begin to show signs of concerning behavior. What’s far more worrying to me in terms of Kessler syndrome is the recent escalation around space warfare, as tensions between Russia, China, and the US continue to boil and nobody seems willing to really commit to making space a neutral zone. Even with space historically being an area of strong international cooperation despite politics (just look at the ISS), that unfortunately seems to be rapidly changing.


  • Well they said .NET Framework, and I also wouldn’t be surprised if they more or less wrapped that up - .NET Framework specifically means the old implementation of the CLR, and it’s been pretty much superseded by an implementation just called .NET, formerly known as .NET Core (definitely not confusing at all, thanks Microsoft). .NET Framework was only written for Windows, hence the need for Mono/Xamarin on other platforms. In contrast, .NET is cross-platform by default.





  • This is a use-after-free, which should be impossible in safe Rust due to the borrow checker. The only way for this to happen would be incorrect unsafe code (still possible, but dramatically reduced code surface to worry about) or a compiler bug. To allocate heap space in safe Rust, you have to use types provided by the language like Box, Rc, Vec, etc. To free that space (in Rust terminology, dropping it by using drop() or letting it go out of scope) you must be the owner of it and there may be current borrows (i.e. no references may exist). Once the variable is droped, the variable is dead so accessing it is a compiler error, and the compiler/std handles freeing the memory.

    There’s some extra semantics to some of that but that’s pretty much it. These kind of memory bugs are basically Rust’s raison d’etre - it’s been carefully designed to make most memory bugs impossible without using unsafe. If you’d like more information I’d be happy to provide!



  • He was in his apartment. There was a call to the police about an argument in the building. The officer went to an apartment that is said the be the wrong one, banged on the door and shouted to open up. Fortston answered the door with a piston in his hand, pointing at the floor. The officer shot him.

    According to the media, Forston was on the phone with his girlfriend for a while by the time the police were called. It seems to me that, as far as the officer was aware, the only “crime” that occured was “an argument”, and it sounds like the officer also had the wrong apartment. Unless I can view the bodycam footage it’s hard to be certain but this definitely sounds like he was killed because he was black and had a gun.