• wewbull@feddit.uk
    link
    fedilink
    English
    arrow-up
    0
    ·
    6 months ago

    Those languages bring different things though:

    • Python is the language the tool is for

    • C is the implementation language of Python and is always going to be there.

    • Cython is a very similar language to Python and designed to be very familiar to Python writers.

    • Fortran is the language that BLAS and similar libraries were historically implemented in since the 70s. Nobody in the python community has to write Fortran today. Those libraries are wrapped.

    • Rust is none of the above. Bringing it into the mix adds a new barrier.

    • eraclito@feddit.it
      link
      fedilink
      arrow-up
      1
      ·
      6 months ago

      Or new possibilities… See: UV, pixi, hatch, ruff, polar, pyarrow, pydantic, data fusion, deltalake, fastuuid, granian, Robyn…

      I’m not a c expert and I’m not comfortable in writing python extensions in C…

      But with rust you have the compiler that, if you constraint yourself to the safe part of the rust language, is checking for you for several stupid issues. In rust, I can focus on fixing logical and other implementation errors. Coming from python I feel much more at home with rust (async, yield, iterator, generator, closure, match, walrus, etc) than with C.