Theoretical engineer (aerospace and biomedical), associate professor of continuum mechanics, ex-petrolhead turned eco-warrior (worrier?), FOSS advocate, non-competitive cyclist, general outdoor enthusiast, renaissance man, beginner lutenist.

he/him

born@326ppm

All posts auto-delete after a while to reduce CO2 footprint.

  • 0 Posts
  • 1 Comment
Joined 2 years ago
Cake day: November 5th, 2022
  • tschenkel@mathstodon.xyztoProgramming@programming.dev•Did #julialang end up kinda stalling or at least plateau-ing lower than hoped?
    8·
    3 months ago

    @astrojuanlu @maegul @programming

    I think there’s two ways to think about the two-language problem (from my scientists view):

    1. from the developer side, when the target is a product/library it may indeed be better to develop in a typed, compiled labguage, and just have a wrapper in Python, or another high-level language that the users/scientists use.

    2. from the user/scientists side: start developing in Matlab/Python, build the proof of concept and demonstrate that the method works. But for the real case application, more performance is needed. So one needs to find a Rust/C++/Fortran developer to join the project. No funds for that, so code never gets developed.

    Julia solves the second kind nicely. If I had to rewrite everything in Rust/C(++)/Fortran, the last few years’ research would not have happened.

    #julialang