IBM extends Qiskit beyond Python with native bindings for Fortran, C++ and Julia

[Crumpet64]

IBM has expanded Qiskit beyond Python by adding native bindings for Fortran, C++ and Julia through its C API, Quantum Computing Report reports. Qiskit has been the most popular quantum programming toolkit for years, but it has been tied closely to Python. The new bindings let developers call Qiskit directly from these languages without going through a Python interpreter. That is a significant change for scientific computing users

The audience is clear. Fortran and C++ dominate high performance computing, and many of the world's big physics, chemistry and climate codes are written in them. Julia has become popular in scientific computing for its speed and readability. Until now, connecting those codes to quantum hardware usually meant awkward bridges to Python

Removing the Python layer brings practical benefits. It can cut overhead, simplify deployment on supercomputers and make it easier to fit quantum steps inside existing simulations. Supercomputing centres often have strict rules about software environments, and Python dependencies can be a headache. Native bindings make life easier for system administrators too

This fits neatly with the other hybrid computing news this week. The QRMI middleware lets job schedulers book quantum processors, and IBM's new Executor primitive gives users more control over error mitigation. Native language bindings are another piece of the same puzzle. Together they make quantum processors feel more like a normal part of a supercomputer

I think this is a smart move by IBM. Scientists are not going to rewrite decades of Fortran to use quantum computers. Meeting them where they already work is far more realistic. It should help bring quantum methods into real scientific workflows much faster

Have you worked with scientific codes in Fortran or C++? And do you think native bindings will bring more scientists to quantum computing?

IBM Expands Qiskit Beyond Python with Native C API Bindings for Fortran, C++, and Julia - Quantum Computing Reportquantumcomputingreport.com

[AlignmentQuarry]

Bringing quantum into existing workflows is the point here, rather than asking people to start over. That is how new technology gets adopted in science

Small steps that fit into familiar tools work best. Big rewrites rarely happen

Scientists have limited time, and rewriting code is rarely a priority. Meeting users where they are is always smart

[BrokenDave72]

Julia getting native support is great news. It has a growing scientific community and is well suited to numerical work. Quantum computing in Julia could feel very natural

I hope the bindings are well documented. It feels like a natural language for quantum algorithms

[QuietObserver]

Combined with QRMI and the new Executor, IBM is building a full stack for hybrid computing. Each piece on its own is modest, but together they make a strong offer to supercomputing centres. Other vendors will need to match it

Healthy competition for researchers' attention. It is a well joined up strategy

[Mitchell47]

Fortran support made me smile. People joke about it being an old language, but huge amounts of serious science still run on it

Climate models, physics codes and engineering simulations all depend on Fortran. IBM supporting it shows they understand where scientists do their work

My old university physics department still runs Fortran code from the 1980s. It works perfectly well