Did #julialang end up kinda stalling or at least plateau-ing lower than hoped?

I know it’s got its community and dedicated users and has continued development.

But without being in that space, and speculating now at a distance, it seems it might be an interesting case study in a tech/lang that just didn’t have landing spot it could arrive at in time as the tech-world & “data science” reshuffled while julia tried to grow … ?

Can a language ever solve a “two language” problem?

@programming

  • FizzyOrange@programming.dev
    1·
    4 months ago

    Anything that helps scientists and engineers move away from MATLAB is welcome.

    The MATLAB language may be pretty bad but IMO that’s not what makes MATLAB good. Rather it’s:

    1. Every signal processing / maths function is available and well documented. I don’t know how well Julia does on this but I know I wouldn’t want to use Python for the kinds of things I used MATLAB for (medical imaging). You don’t have to faff with pip to get a hilbert transform or whatever…

    2. The plotting functionality is top notch. You can easily plot millions of points and it’s fast and responsive. Loads of plotting options. I just haven’t found anything that comes close. Every other option I’ve tried (a lot) only works for small datasets.

    • Juan Luis@social.juanlu.space
      1·
      4 months ago

      @FizzyOrange The problem with Python for signal processing and stuff like that is not pip (I know it’s a meme by now, but it’s really not that bad) but rather, the fact that some SciPy subpackages are barely maintained