[KenoFischer]

Nothing complicated.

Stream 1: Build amazing products for particular domains, charge license fees

Stream 2: Build a great SaaS platform for running Julia, charge for compute

Since all of our domain products are built in Julia and often involve significant compute cost for their intended application, hopefully both at the same time :).

[slownews45]

My own view is that Julia Computing is distinguished a bit by a more product focus.

It's a bit less of a pure language / infra play and more a product play. Ie, docker / containers was almost a pure infra play in the end. These guys make actual things you can use.

The later sells better into business I think and is less likely to be competed against. Google / AWS et al are generally pretty quick to compete on the infra play level.

[hawk_]

thanks for the answer Keno. i guess an example Stream 1 product is Pumas. i didn't realize it's a separate product from Julia. my background is in finance and i am curious if you have any plans to break into that domain (examples on your website include julia language use)

[KenoFischer]

Finance was a focus area early on and we have a fair number of consulting clients there and JuliaHub is available of course, but we were never able to figure out a dedicated domain-specific, non-niche product to sell into the space. Maybe in the future.

[snicker7]

Lots of finance companies shell out a lot of money for KDB+, a fast real-time database. Other than performance, the main selling point is that it comes with its own imperative language (K/Q). You can build entire API's and trading systems in Q: persistence, load balancing, streaming analytics, &tc. In that way, Q solves a different "two-language problem". There are not many serious competitors.

If Julia had its own lean realtime database implementation, then I can see it becomming a killer language for finance. JuliaDB/OnlineStats is probably 60% of the way there.

[hpcjoe]

FWIW: I am using it as a general purpose language at the intersection of large data sets, analytics, and related bits. At a prop shop.

YMMV, but I find it is fantastic in this use case. And I don't have to worry about semantic space.

[anon_tor_12345]

lol doesn't this create perverse incentives - i.e. you're incentivized to actually make Julia slower sine it'll lead to being able to charge more for compute :p