The article ends with this nugget about C++ shared memory state management, but I don't have the background to know exactly what they're referring to. Does anyone recognize this pattern and feel able to explain it to mere mortals?<p>> “We also have different tools so that any state that is persisted through the application is managed in a very particular place in memory. This lets us know it is being properly shared between the computers. What you don’t want is a situation where one of the computers takes a radiation hit, a bit flips, and it’s not in a shared memory with the other computers, and it can kind of run off on its own.”
Starlink is super exciting from an emerging technologies perspective —— (relatively) cheap satellite production, commercialized laser links, commercialized phased-array tx/rs, among others. These open up very interesting possibilities down the road.<p>These posts always have a thread about people wanting to work for spacex, but because of my pseudo-anonymity, I don’t feel bad about starting it: Does anyone know if spacex does fall or spring embedded software internships?
Puff piece. Starlink is fundamentally not about providing broadband to anyone. It’s landgrabbing a finite resource - low-earth orbit space - before it’s worth is recognised by those who should be regulating it.<p>The broadband itself might be nice or it might be awful. It doesn’t actually matter because that was never the point.