• 0 Posts
  • 352 Comments
Joined 1 year ago
cake
Cake day: June 6th, 2024

help-circle


  • I went ahead and read the article. I know a bit about quantum computing. Here’s my summary of it:

    Entanglement is a useful resource for quantum networking, enabling things like quantum-secure communication and distributed quantum computing.

    TLDR The paper describes algorithms to more efficiently create a form of entanglement that’s useful from the error-prone “dirty” entanglement you get from entanglement-generating hardware.

    When you make entanglement, it often doesn’t come out perfect, and you need a technique to “distill” “good” entangled states out of a collection of “dirty” entangled states.

    The typical “rules” for this involve two parties that create dirty shared entanglement (shared entanglement means a pair of entangled qubits, but each party has one of the qubits). They can then do whatever they like with their qubits individually and can communicate (over classical channels e.g. the internet) but they can’t do anything “quantum” between the two of them.

    This paper analyzes the case where there is a 3rd party that follows these same rules but has been previously set up as an “entanglement battery”, which means preparing it in a special state from which entanglement can be “borrowed” or “returned” to the battery using only local operations and classical communication.

    In particular it’s looking for “reversible” (meaning no loss in total entanglement over the process) “entanglement manipulation” (changing the entanglement from one form into another, presumably more useful form). It goes into a lot of analysis as to what the limits on this process are, and makes analogies to how engines work in thermodynamics.







  • Supporters seem to be under the impression that companies have a “sever.exe” file they purposefully don’t provide players because they’re evil and hate you.

    There is some truth to this

    They could also be contracting out matchmaking services to a third party and don’t actually do it in-house. Software development is complex and building something that will be used by 100,000 people simultaneously isn’t easy.

    There is some truth to this too.

    Making an MMO maintainable by the userbase might be complicated. But way more common are games that could easily have LAN based multiplayer but the company decides not to add it, or even singleplayer games that require an internet connection, just so the company can put limits on how and when the game is played.





  • Windows is designed to work on a very wide range of specs, so older devices as well as low-end newer devices should be able to run it.

    That’s even more true about Linux. Many popular distros can be run on a raspberry pi, a 20 year old MacBook, or a state-of-the-art gaming desktop.

    It’s less true about macOS because Apple has more control over the hardware so they can be pickier. Mobile developers also have more control over the hardware and can be pickier, although that’s less true about Android than iPhone.



  • Honestly services like Blue Apron help with this. It’s more expensive than buying your own groceries, but still cheaper than eating out. It also helps you learn meal planning to eventually be able to buy the right amount of food on your own.

    (It is easier to do if you have more people to feed though, like ideally at least one friend/partner/roommate to share the subscription with you. You can do a 2-3x a week meals for 2 subscription for one person, but it’s a bit much.)





  • No.

    The “all browsers are iOS reskin” thing is browsers must use WebKit for JavaScript and rendering, which are the two biggest parts of a browser. WebKit is a library of code distributed as part of the iOS SDK. However, Safari adds more on top of WebKit, including its plugin API. Installing plugins into iOS Safari wont affect anything just using WebKit because they aren’t using the Safari plugins code.

    In theory Firefox could implement its own plugins system for iOS, but it would more limited than the normal Firefox plugin system for other devices, and also they might run into policy issues with Apple (this policy about 3rd party browsers is part of a broader policy against side loading, which has in the past prevented things like emulators and programming apps into the App Store. They have recently started loosening up on their anti-side loading policies, however).