jebej
Re:Julia's latency: Past, present and future
on Friday March 31, 2023 @06:36PM (#35394701)
Very interesting, thanks for the writeup and work on benchmarking all of this. I suspected package loading had gotten slower from 1.0 to ~1.7, but 1.9 will solve most concerns.
Re:On the Leaked Google/NASA Quantum Supremacy Paper
on Monday September 23, 2019 @10:37AM (#21049286)
They seem to know about decoherence, and in a later post associate interference with probabilities, so I don't think that was the issue. Maybe a typo?
Re:On the Leaked Google/NASA Quantum Supremacy Paper
on Monday September 23, 2019 @09:44AM (#21048847)
Quantum physicist here: just to correct the mistaken claims in this, interference is definitely a feature of quantum computing, and not a bug.
Interference is also NOT why there are are no error corrected quantum computers. The reason there are no error corrected quantum computers is because we need way (way way) many more physical qubits, and they would need to be of better quality (less decoherence).
Re:Statistics with Julia [pdf]
on Friday July 12, 2019 @08:14PM (#20425672)
The Plots package adds a significant overhead right now. Try using PyPlot (matplotlib) directly. These days you can use exactly the same syntax (dot-call) as in Python.
$ time julia -e "using PyPlot;x=1:10;y=rand(10);plot(x,y);"
real 0m5.676s
Re:IBM Q System One
on Tuesday January 08, 2019 @01:35PM (#18858082)
The latter.
More seriously though, there won't be a true error corrected quantum computer for a long time. People are hoping that there can be useful applications with imperfect physical qubits.
You can use whatever start index you like: https://docs.julialang.org/en/stable/devdocs/offset-arrays/#...
For a pre-baked solution: https://github.com/JuliaArrays/OffsetArrays.jl
Re:How Numba and Cython speed up Python code
on Friday August 03, 2018 @02:57PM (#17682598)
Just use julia instead!