[cookieperson]

Neither Julia nor Matlab are great production languages. They are both fine if you just have some math you want to run to get some results. But... Julia changes and breaks core functionality regularly in pretty much everything from the language itself to the packages you use. Matlab although is more stable, has other detriments. It's closed source, it's not really designed to be a systems language, sometimes it's not fast enough, etc.

In my mind, fortran will always be hard to replace especially if there is sizeable legacy code. A lot of people don't realize it, but fortran is kind of like sql. It's old, backed by a lot of theory, and delivered on it's promises for years. That makes challengers job really really hard.

[adgjlsfhk1]

At this point, Julia is being used on ASML's lithography machines. it's pretty deployable.

I'm not sure where you are getting the idea of frequent breaking releases. the language has been pretty stable since 1.0 in 2018 (as in almost all code that worked on 1.0 still works now). (there are some very minor breaking changes in minor releases, but Julia breaks a lot less things per release than python or C).

[cookieperson]

Cool I am glad there are more people using it in production these days, it will help the language become more stable. I've deployed Julia to production a few times now. In almost every case it was rewritten in another language within a year for one reason or another... This is sad, but, for being a v1 language, it never lost it's "early adopter" experience for myself or my colleagues.

I've seen minor releases in Julia break essential packages. Not like it was one time either. So where did I get the idea, personal hands on experience.

Again it's great if you have a script and want to run it, anything beyond that, in my experience, results in a lot of turmoil and erosion. Almost wonder if it's a flaw in the language itself or, the maintenance model of the packages. Oh well not my problem

[sundarurfriend]

> I've seen minor releases in Julia break essential packages.

Any specific examples of this happening in Julia 1.0 or later?

[cookieperson]

Absolutely, a minor change to Julia base broke the CSV package for weeks. But that's like 1 of hundreds of examples. I don't think non package developers realize how much effort package maintainers and drive-by contributors do to keep that language alive.

[sundarurfriend]

Would you happen to remember the specific version, or links to any of the other examples? I ask because I've repeatedly heard that every release is tested against the entirety of the (public) package ecosystem, so I'm curious how these snuck through - whether it was before such a system was put in place (maybe because of these breakages), or whether things still sneak through the tests to such a degree.

[cookieperson]

I don't remember, maybe check closed issues in their repository. But I think we all know why you're really saying this. To cast doubt on what I'm saying. That's okay, gotta get that $$$ or something.