You can rent it, but it's basically worthless at this stage.

there's still a long road to commercial applications but today's hardware is simulating quantum systems beyond the scale of classical methods, for example [1]; an interesting line of work opposite to this can be found in those who improve classical methods towards such examples [2], but these are only developed because of the existing quantum hardware

Really though, today's IBM hardware is good fun to play with, eg for generating moderately large GHZ states

[1] https://arxiv.org/abs/2510.26845 [2]https://arxiv.org/abs/2306.14887

Is there anything you can do on a rented QC that you can't do cheaper on a simulated QC on a "classical" CPU/GPU today?

hello,

yes ... especially if you want to execute quantum-circuits which use a lot of qubits.

why!? one approach of the simulation of quantum-computers rely on the so called "state vector" of the machine, and its memory-usage grows exponentially.

for example qiskit AER

* https://qiskit.github.io/qiskit-aer/stubs/qiskit_aer.Stateve...

just as an example:

for 32 qubits, the simulator needs 64 GB RAM

=?> double the RAM for each additional qubit

so: for 36 qubits, the simulator needs 1 TB RAM

:)

so it gets pretty "costly" to do simulations rather quickly ...

just my 0.02€

No. They're a decent playground for prototyping hybrid algorithms but even that is limited. No one has yet published a hybrid algorithm on a rentable QC provider that has better benchmark performance than a modern CPU/GPU implementation.

> due to the way round-tripping tool-calls work, splitting code up into multiple files is counter-productive.

Can you expand on that?

Even complete legal novices like me know about the Sony/Betamax case, FWIW. It would shock me if a judge ruling on copyright implications of a technology didn't know about it.

They’re talking about the judges on the Sony/Betamax case, not the new one.

> There's only one highly monetizable use for AI video generation

Yeah, marketing. Which is a huge market...

Supply-chain attacks long pre-date effective AI agentic coding, FWIW.

It's very straightforward to instrument CC under tmux with send-keys and capturep. You could easily use that for distillation, IMO. There are also detailed I/O logs.

FWIW, I read it before I learned that it was AI-generated, and I enjoyed it and thought it's possibly insightful.

Wow, Gemini suggested a very similar experiment to me yesterday. Guess I know where it got the idea from, now. :-)

That happens often enough that it might have its own token, if you BPE-encoded specifically for golang.

IMO, you should do both. The cost of intellectual effort is dropping to zero, and getting an AI to scan through a transcript for relevant details is not going to cost much at all.