News for hackers. Stuff that matters.
Re:JuliaCon2020: Julia Is Production Ready by andi999 on Saturday August 08, 2020 @12:00PM (#24092627)
I know there are workarounds, but when you do not have guarantees the phrase 'production ready'is not the first that comes to my mind. (Of course in the problem spaces of matlab and python, and probably R, Julia is probably on par)
Re:JuliaCon2020: Julia Is Production Ready by eigenspace on Saturday August 08, 2020 @03:32PM (#24094434)
I don't think the blog post above here is about using julia for ultra-low-latency systems to be pair. 'Production ready' is a pretty vague statement and certainly doesn't apply to every usecase.

I'd say that if people have other reasons to use julia in a realtime low-latency production system -- like needing it's scientific stack -- then you can certainly make it work, you just need to do some testing to make sure you're not hitting GC.

Re:JuliaCon2020: Julia Is Production Ready by DNF2 on Saturday August 08, 2020 @02:35PM (#24093975)
Well, how high is the bar for calling a language 'production ready' in that case? How many production ready languages are there?
Re:JuliaCon2020: Julia Is Production Ready by andi999 on Tuesday August 11, 2020 @10:40AM (#24120715)
What I meant: production ready depends on the feature. So for substituting Python (and beeing able to write fast in-language extensions), the language is most likely production ready; so in a sense it is a replacement for Python + C; but not a replacement for C. And this is a bit sad, because it could have been (building linked executables should be possible, since the language is compiled).

But I like your question, lets call it 'which languages are all purpose production ready'; probably only C, C++, Java (there is a real-time version), LabView.