by Matthias WulffCommunityCheck quantum computing claims against sourced hardware data: whether a computation runs on today's hardware, what it would take, and how fast records are improving.
See for yourself what today's quantum computers can actually do, and how far they are from the applications in the headlines. You do not need to be a physicist. Ask AgentOne in plain language, and it runs the numbers on real hardware records, each one taken from a published source.
Is it realistic yet? Paste a paper, a press release, a roadmap or a headline to compare its claims with today's hardware. Or describe a computation, or pick one of the example algorithms, and see how likely today's best hardware is to get it right, with and without error correction.
What would it take? See how much better the hardware would have to get, and how many physical qubits and how much run time a well-known goal, such as breaking RSA-2048, needs once error correction is included.
How fast is progress? Compare trapped-ion, superconducting and neutral-atom hardware side by side. Follow the record error rates and qubit counts over the years, and see when the trend would reach a target if it held. This is an extrapolation, not a forecast.
The answers to the first two questions show their assumptions and caveats. Every hardware record links to the paper or vendor publication it comes from. The tools give numbers, not verdicts. What they mean for quantum computing is up to your judgement.
For experts, the same tools take exact inputs: qubit count, circuit depth, per-gate error rate, surface-code distance, qLDPC codes, and logical qubits with T count for full fault-tolerant footprints (surface code on the Litinski cost model, qLDPC on the published bicycle architecture).
Limitations: this is a deliberately simplified model. It treats noise with the standard surface-code approximation and a routing allowance for hardware with fixed connections. It leaves out effects such as leakage, crosstalk, measurement errors, single-qubit gate errors and idling. Where a measured benchmark score and the model disagree, the measurement wins. All tools are read-only and take no personal data.