Programming

423 readers

6 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Did #julialang end up kinda stalling or at least plateau-ing lower than hoped? (hachyderm.io)

submitted 4 months ago by maegul@hachyderm.io to c/programming@programming.dev

21 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] maegul@hachyderm.io 2 points 4 months ago (4 children)

@tschenkel @astrojuanlu @programming

I'd suppose part of the problem might be that there's a somewhat hidden 3rd category of user that "feels" whatever added complexity there is in a two-language lang like julialang and has no real need for performant "product" code.

And that lack of adoption amongst this cohort and your first enforces lang separation.

I may be off base with whether there's a usability trade off, but I'd bet there's at least the perception of one.

[–] hrefna@hachyderm.io 3 points 4 months ago (3 children)

@maegul

Considering, it may be worth highlighting that tools like Jax exist as well (https://github.com/google/jax). These have even become an expected integration in some toolkits (e.g., numpyro)

It may not be the most elegant approach, but there's a lot of power in something that "mostly just works and then we can optimize narrowly once we find a problem"

It doesn't make a solution that solves this mess bad, but I do wonder about it being a narrow niche

@tschenkel @astrojuanlu @programming

[–] maegul@hachyderm.io 1 points 4 months ago

@hrefna @tschenkel @astrojuanlu @programming

Yea ... it seems that things like this are part of Julia's problem ...

that for many the "two language problem" is actually the "two language solution" that's working just fine and as intended, or as you say, well enough to make an ecosystem jump seem too costly.

load more comments (2 replies)

load more comments (3 replies)