* A lot of packages are incompatible with the latest versions of Julia. Though because it has stabilized, this is likely to stop being an issue soon.
* There isn’t any major organization that has adopted it yet, which may impact its long term success in contrast to other new languages like go swift rust etc that have a major sponsor.
Garbage collector makes it unsuitable for certain real time uses, which is unfortunate given its otherwise predictable performance characteristics.
* Although there are web frameworks for it, I’m not sure whether they are mature enough for production use.
* Personal pet peeve: no infix operator for integer division. I haven’t looked recently whether there is a package for this. I should probably make my own if not.
The FAA is collaborating with Lincoln Labs to develop a new collision avoidance system using Julia¹. I don't know if that's the kind of thing you had in mind, but it's being used by many companies and universities on various projects, and is the language vehicle in a lot of courses on numerical analysis and related topics.
Well, I was thinking more of an organization using it across the board, preferably one that is prominent enough to result in other copycat users.
(To be clear, I really love the Julia language, and use it quite a bit in personal projects - I'm just hoping that it gets strong adoption, since adoption is what drives the development of miscellaneous libraries and packages).
The transition to v1.0 for packages is taking some time. The core language is so extensible and allows performant packages such that much of what people expect to be core (an FFT) is in an external package which has not yet been updated for 1.0.
* A lot of packages are incompatible with the latest versions of Julia. Though because it has stabilized, this is likely to stop being an issue soon.
* There isn’t any major organization that has adopted it yet, which may impact its long term success in contrast to other new languages like go swift rust etc that have a major sponsor. Garbage collector makes it unsuitable for certain real time uses, which is unfortunate given its otherwise predictable performance characteristics.
* Although there are web frameworks for it, I’m not sure whether they are mature enough for production use.
* Personal pet peeve: no infix operator for integer division. I haven’t looked recently whether there is a package for this. I should probably make my own if not.