• 0 Posts
  • 8 Comments
Joined 1 month ago
cake
Cake day: September 27th, 2025

help-circle
  • I think if we’re ever going to find an answer to “Why does the universe exist?” I think one of the steps along the way will be providing a concrete answer to the simulation hypothesis. Obviously if the answer is “yes, it’s a simulation and we can demonstrate as much” then the next question becomes “OK so who or what is running the simulation and why does that exist?” which, great, now we know a little bit more about the multiverse and can keep on learning new stuff about it.

    Alternatively, if the answer is “no, this universe and the rules that govern it are the foundational elements of reality” then… well, why this? why did the big bang happen? why does it keep expanding like that? Maybe we will find explanations for all of that that preclude a higher-level simulation, and if we do, great, now we know a little bit more about the universe and can keep on learning new stuff about it.


  • Yes, kind of, but I don’t think that’s necessarily a point against it. “Why are we here? / Why is the universe here?” is one of the big interesting questions that still doesn’t have a good answer, and I think thinking about possible answers to the big questions is one of the ways we push the envelope of what we do know. This particular paper seems like a not-that-interesting result using our current known-to-be-incomplete understanding of quantum gravity, and the claim that it somehow “disproves” the simulation hypothesis is some rank unscientific nonsense that IMO really shouldn’t have been accepted by a scientific journal, but I think the question it poorly attempts to answer is an interesting one.


  • A poor architect blames their tools. Serverless is an option among many, and it’s good for occasional atomic workloads. And, like many hot new things, it’s built with huge customers in mind and sold to everyone else who wants to be the next huge customer. It’s the architect’s job to determine whether functions are fit for their purposes. Also,

    Here’s the fundamental problem with serverless: it forces you into a request-response model that most real applications outgrew years ago.

    IDK what they consider a “real” application but plenty of software still operates this way and it works just fine. If you need a lot of background work, or low latency responses, or scheduled tasks or whatever then use something else that suits your needs, it doesn’t all have to be functions all the time.

    And if you have a higher-up that got stars in their eyes and mandated a switch to serverless, you have my pity. But if you run a dairy and you switch from cows to horses, don’t blame the horses when you can’t get milk.



  • It’s an old joke from back when IBM was the dominant player in IT infrastructure. The idea was that IBM was such a known quantity that even non-technical executives knew what it was and knew that other companies also used IBM equipment. If you decide to buy from a lesser known vendor and something breaks, you might be blamed for going off the beaten track and fired (regardless of where the fault actually lay), whereas if you bought IBM gear and it broke, it was simply considered the cost of doing business, so buying IBM became a CYA tactic for sysadmins even if it went against their better technical judgement. AWS is the modern IBM.