• 0 Posts
  • 69 Comments
Joined 6 months ago
cake
Cake day: June 6th, 2024

help-circle
  • You’ll feel right at home in the command line. Install Homebrew or MacPorts. These are command line package managers. Many if not most of the software tools you are used to on Linux likely have Mac versions as well and you can find them either online or via one of those package managers.

    If you are going to download software from Apple’s Apple Store, you will need to make an account. You can install software directly from the internet without needing an account. You might need to tweak some “security settings” in System Preferences to run software not from the App Store.

    Unfortunately Xcode is something you need an Apple account to install. However, the Xcode “command line tools”, which includes a lot of common tools like gcc, I believe you can install by running “xcode-select --install” from the command line even without an account. There might also be other ways to get those tools installed manually / not through Apple

    If you just want an IDE and really want to avoid making an account, just use VSCode or something. But if you will need to develop Mac apps using Apple’s APIs, it will likely be easier at the very least to work in Xcode. And if you are going to develop for any of Apple’s other operating systems (like iOS) you will need to make an account.












  • The reason you do stuff in a venv is to isolate that environment from other python projects on your system, so one Python project doesn’t break another. I use Docker for similar reasons for a lot of non-Python projects.

    A lot of Python projects involve specific versions of libraries, because things break. I’ve had similar issues with non-Python projects. I’m not sure I’d say Python is particularly worse about it.

    There are tools in place that can make the sharing of Python projects incredibly easy and portable and consistent, but I only ever see the best maintained projects using them unfortunately.








  • Because the math checks out.

    For a high level description, QEC works a bit like this:

    10 qubits with a 1% error rate become 1 EC qubit with a 0.01% error rate.

    You can scale this in two ways. First, you can simply have more and more EC qubits working together. Second, you can near the error correcting codes.

    10 EC qubits with a 0.01% error rate become one double-EC qubit with a 0.0001% error rate.

    You can repeat this indefinitely. The math works out.

    The remaining difficulty is mass producing qubits with a sufficiently low error rate to get the EC party started.

    Meanwhile research on error correcting codes continues to try to find more efficient codes.