• 0 Posts
  • 54 Comments
Joined 2 years ago
cake
Cake day: June 20th, 2023

help-circle





  • Disclaimer: I could be wrong or not up to date, but this is my current understanding.

    On the small scale, forces like electromagnetism and gravity pull things together much much faster than the rate of cosmological expansion. That’s why “we” don’t expand, and neither does our frame of reference. There’s a potential end to the universe where the rate of cosmological expansion (which increases over time) finally exceeds gravity and electromagnetism and eventually even the strong force, causing everything to fly apart forever.

    Light waves propagate through spacetime itself, and basically it ends up being that there’s nothing pulling it back from expanding as the space it travels expands.








  • https://youtu.be/cw20VbX1XCc?si=OiZJV8VBsFjWQ4JC

    A lot of people here have the right idea, but are just more pessimistic than me about the industrial capabilities of our civilization if we survive long enough to achieve them. Star lifting is an idea with what I understand to be reasonably sound scientific principles. It’s just a matter of scaling our industry over the next millions or billions of years.

    I like this channel because he’s a fairly optimistic but very reality based futurist. He’ll tell you straight up if something is unlikely or impossible based on our current understanding of science, but he’s one of the few sources I’ve seen that acknowledges the immense scale that even an Earth or solar system bound civilization is capable of supporting with just modern technology.




  • If it’s a private repo I don’t worry too much about forking. Ideally branches should be getting cleaned up as they get merged anyway. I don’t see a great advantage in every developer having a fork rather than just having feature/bug branches that PR for merging to main, and honestly it makes it a bit painful to cherry-pick patches from other dev branches.





  • … You know not all development is Internet connected right? I’m in embedded, so maybe it’s a bit of a siloed perspective, but most of our programs aren’t exposed to any realistic attack surfaces. Even with IoT stuff, it’s not like you need to harden your motor drivers or sensor drivers. The parts that are exposed to the network or other surfaces do need to be hardened, but I’d say 90+% of the people I’ve worked with have never had to worry about that.

    Caveat on my own example, motor drivers should not allow self damaging behavior, but that’s more of setting API or internal limits as a normal part of software design to protect from mistakes, not attacks.