> For industry, it probably means something similar. > > > I really hope people in industry won't act on this date, as it is not > nearly firm enough to bet a business on. We already have people writing > blog posts about how using Julia for their startup turned out to be a > mistake; we really don't need to encourage a new group of people to bet on > something that's not 100% guaranteed. >
This is indulging in a potential tangent, but I think the planned (non-binding) date conversation is often useful as a scope. FWIW, things are rapidly progressing on that front -- especially with what was on display at JuliaCon. It's clear Julia Computing is helping push a number of things now... I agree with John that it's not an SLA. And betting a complicated codebase on a rapidly evolving technology is a .. well .. significant risk. That said, there are lots of places Julia can still excel and be a great choice. If an industry application can just freeze out a version of julia for a specific task, it's not hard to keep it running using Julia v0.3 or whatever until it needs to be updated again. I don't think John meant anything against the last bit -- but for the silent readers, I wanted to throw in some of these thoughts. Cameron
