# Julia's business model

**URL:** <https://discourse.julialang.org/t/julias-business-model/70328>\
**Category:** Community\
**Tags:** question, licenses, legal\
**Created:** [October 25, 2021, 11:31am UTC](https://discourse.julialang.org/t/julias-business-model/70328 "2021-10-25T11:31:37Z")\
**Posts on this page:** 20\
**Page:** 5

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [November 5, 2021, 1:43pm UTC](https://discourse.julialang.org/t/julias-business-model/70328/82 "2021-11-05T13:43:29Z")

</div>

> [@lobingera](#):
>
> Did you edit this (because i remember to read a version number here)?

Yes, I did because someone DMed me that MathWorks does allow downloads of old versions of Matlab, so I edited it to change the incorrect claim.

---

<div class="post-metadata">

**Author:** ![cormullion](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/cormullion/32/49131_2.png) [@cormullion](https://discourse.julialang.org/u/cormullion)\
**Post date:** [November 5, 2021, 2:11pm UTC](https://discourse.julialang.org/t/julias-business-model/70328/83 "2021-11-05T14:11:08Z")

</div>

I wonder whether that old license file works, though.

I have a fair few Mathematica notebooks created in versions 7, 8, and 9 that are sitting on my hard drive waiting for me to buy a new license so that I can open them again. Fortunately nothing of value, in my case.

---

<div class="post-metadata">

**Author:** ![lobingera](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lobingera/32/211_2.png) [@lobingera](https://discourse.julialang.org/u/lobingera)\
**Post date:** [November 5, 2021, 2:28pm UTC](https://discourse.julialang.org/t/julias-business-model/70328/84 "2021-11-05T14:28:23Z")

</div>

I’m using matlab (at work) with a network license and sometimes run old versions (2015 etc.) of matlabs on VMs (getting old OS/linux versions is actually more tricky than matlab itself) and this just works.

---

<div class="post-metadata">

**Author:** ![bilderbuchi](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bilderbuchi/32/13562_2.png) [@bilderbuchi](https://discourse.julialang.org/u/bilderbuchi)\
**Post date:** [November 6, 2021, 10:53am UTC](https://discourse.julialang.org/t/julias-business-model/70328/85 "2021-11-06T10:53:10Z")

</div>

> [@StefanKarpinski](#):
>
> Wholly agree that Romer’s swipe at Julia is unwarranted

Is it, though? I think the concerns around “Julia+” have been discussed enough already, but what if he actually meant something else?

What happens when (not if) JuliaComputing’s venture capital investors expect to receive a big(ger, if not necessarily unicorn-level) return on their substantial investment?  
One monetisation pathway could be to start pushing more and more useful/important features into JuliaComputing’s proprietary/cloud offerings (i.e., _external_ to the Julia itself), maybe somewhat like Mathworks’ Matlab Toolboxes [1].

JuliaComputing rightly prides itself of having all creators of the language as their founders (as opposed to, say, Anaconda Inc. for Python), so they can control a lot of Julia mindshare and development direction. I think this makes it less likely that useful but proprietary features get an alternative open implementation by the motivated community.

That way, the language keeps all the openness features emphasized above, and people are not required to “pay for using the Julia language”, but the Julia ecosystem can still be nicely leveraged into ROI.

_[1] possibly we’re already seeing the beginnings of this, as judging from remarks I’ve seen/heard, a standard component library for MTK seems to be destined to end up as a JuliaComputing offering instead of open-source, like e.g. [Modelica’s MSL](https://github.com/modelica/ModelicaStandardLibrary)._

fwiw, I hope I’m wrong and just too jaded by seeing how VC influence plays out! 😄

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [November 6, 2021, 3:15pm UTC](https://discourse.julialang.org/t/julias-business-model/70328/86 "2021-11-06T15:15:14Z")

</div>

How is this different from Guido van Rossum working at Google, Dropbox and now Microsoft? Or Go being de facto controlled by Google? Or Swift by Apple? Or Rust by Mozilla? Everyone gets paid somehow. Do you trust megacorps more for some reason? I doubt it. Instead, I suspect it’s because you trust the individuals in charge of those projects to not be unduly influenced, regardless of their employer.

---

<div class="post-metadata">

**Author:** ![baggepinnen](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/baggepinnen/32/693_2.png) [@baggepinnen](https://discourse.julialang.org/u/baggepinnen)\
**Post date:** [November 6, 2021, 6:14pm UTC](https://discourse.julialang.org/t/julias-business-model/70328/87 "2021-11-06T18:14:36Z")

</div>

> [@bilderbuchi](#):
>
> 1] possibly we’re already seeing the beginnings of this, as judging from remarks I’ve seen/heard, a standard component library for MTK seems to be destined to end up as a JuliaComputing offering instead of open-source, like e.g. [Modelica’s MSL](https://github.com/modelica/ModelicaStandardLibrary).

> <https://github.com/SciML/ModelingToolkitStandardLibrary.jl/blob/main/LICENSE>

Looks open source to me

---

<div class="post-metadata">

**Author:** ![jzr](https://avatars.discourse-cdn.com/v4/letter/j/eb9ed0/32.png) [@jzr](https://discourse.julialang.org/u/jzr)\
**Post date:** [November 6, 2021, 7:33pm UTC](https://discourse.julialang.org/t/julias-business-model/70328/88 "2021-11-06T19:33:45Z")

</div>

> [@StefanKarpinski](#):
>
> Do you trust megacorps more for some reason? I doubt it. Instead, I suspect it’s because you trust the individuals in charge of those projects to not be unduly influenced, regardless of their employer.

Everybody wants Julia to be successful and for its developers to be successful, and I’m sure the JC team are well-intended and capable technologists. But for me, my concerns are mainly not a matter of trusting those individuals. When investing in a foundational technology, I don’t want to rely on a single company. Incentives stemming from Julia Computing’s [$28.6M](https://www.crunchbase.com/organization/julia-computing) investor obligations are only a small part of the risk—any single company would have some incentive structure that is not perfectly aligned with the broader community’s.

It is useful to consider two kinds of projects: those that are principally controlled by a single company, and those with distributed control.

**Python** is managed by the Python Steering Council, chosen by election from the core developers, and the nonprofit Python Software Foundation (PSF). It has been led by a distributed group of core contributors including van Rossum for a long time. “Python” and “PyCon” are [trademarks](https://www.python.org/psf/trademarks/) of the PSF.

**PostgreSQL** [has](https://momjian.us/main/blogs/pgblog/2020.html#October_7_2020) an “unwritten rule that the Postgres core team should not have over half of its members from a single company” and quickly [expanded](https://www.postgresql.org/about/news/new-postgresql-core-team-members-2103/) the Core Team after an acquisition merged large employers in order to resolve the issue.

**Rust** Core Team member Steve Klabnik wrote recently in a thread beginning [“I refuse to let Amazon define Rust”](https://twitter.com/steveklabnik/status/1437441118745071617):

> In the beginning, Rust did have one sole patron: Mozilla. Everyone was uncomfortable with that arrangement, including Mozilla.
> 
> We spent years trying to get away from this situation. It had tons of negative effects.

**Go** and **Swift** each are essentially controlled by a single company. The company’s incentives drive the direction of the language and its ecosystem. Swift is regarded as an excellent language but has little adoption outside Apple-product developers.

* * *

Looking at **Julia** ’s GitHub [contributors](https://github.com/JuliaLang/julia/graphs/contributors?from=2019-12-08&to=2021-11-06&type=c) of the last two years, I count 6 of the top 10 are employees of Julia Computing. The ecosystem packages are also largely supported by Julia Computing. The “Julia” name and logo are [owned](https://trademarks.justia.com/882/45/julia-88245811.html) by Julia Computing and Stefan, respectively. In 2017, there was [discussion](https://discourse.julialang.org/t/trademark-guidelines-fair-use-policy-for-julia-name-logo/3404/4) about transferring the IP to a foundation but I haven’t seen movement on that. On the other hand, the JuliaCon [proceedings committee](https://juliacon.org/2021/committee/) isn’t a Julia Computing team.

I know Julia Computing’s contributions to the language and its ecosystem are massive, and the largest contributors perhaps unavoidably have the largest influence on the language. I don’t know in what ways the concentration of control and funding risk harming the language ecosystem as a whole, or how these risks can be avoided. But it’s worth looking for ways to mitigate such problems before they arise. I hope these discussions continue until that risk fades away.

---

<div class="post-metadata">

**Author:** ![johnmyleswhite](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/johnmyleswhite/32/31_2.png) [@johnmyleswhite](https://discourse.julialang.org/u/johnmyleswhite)\
**Post date:** [November 6, 2021, 7:48pm UTC](https://discourse.julialang.org/t/julias-business-model/70328/89 "2021-11-06T19:48:07Z")

</div>

I think if people are worried that too many of the Julia contributors work at Julia Computing, it’s worth thinking through the universe of potential fixes:

1. You remove some of the current Julia Computing people from the main contributor group.
2. You add more non-Julia Computing people to the main contributor group.

I’d even say that the single best group of people to provide the staffing for (2) are the people worried about the current setup since they have a clear incentive to fix something that matters to them. 🙂

---

<div class="post-metadata">

**Author:** ![jzr](https://avatars.discourse-cdn.com/v4/letter/j/eb9ed0/32.png) [@jzr](https://discourse.julialang.org/u/jzr)\
**Post date:** [November 6, 2021, 8:32pm UTC](https://discourse.julialang.org/t/julias-business-model/70328/90 "2021-11-06T20:32:55Z")

</div>

The remedies to concentration may include other options – for example, one not listed was “remove some Julia contributors from Julia Computing” (joke).

Part of the motivation for my comment is to suggest that this is an issue that affects the community as a whole. Julia Computing employees themselves, having so much at stake in the future of the language, might be well placed to work on solutions, as did major-contributor employees in some of my examples.

There are other ways of diffusing influence, such as defining a Core Team of decision-makers who might influence the direction of the language; funding a foundation to choose and provide [development grants](https://www.python.org/psf/grants/) to [independent developers](https://isocpp.org/about/financial-assistance-policy), and so on. I encourage people to think broadly about how the language community can ensure its user base is represented in its contributor base and leadership.

---

<div class="post-metadata">

**Author:** ![jling](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jling/32/212909_2.png) [@jling](https://discourse.julialang.org/u/jling)\
**Post date:** [November 6, 2021, 8:54pm UTC](https://discourse.julialang.org/t/julias-business-model/70328/91 "2021-11-06T20:54:46Z")

</div>

> [@jzr](#):
>
> I encourage people to think broadly about how the language community can ensure its user base is represented in its contributor base and leadership.

this is vacuous, in the end, language design/direction is a technical challenge, it’s about who has the ability and does what. On one extreme, let’s say outside of JuliaComputing there are only novice users (this is not the reality btw, many top contributors are not JC), do you expect if somehow the community elect some “users” to a committee will solve the issue, if these users don’t know the details?

In the end the only “solution” (I don’t even see a problem tbh, it’s just a reality that is common in numerous FOSS projects’ life cycle)

> [@johnmyleswhite](#):
>
> You add more non-Julia Computing people to the main contributor group.

and you can be assured that this will happen if Julia becomes successful, after all, if Julia doesn’t get used by enough people, the world couldn’t care less what we do with “yet another programming language”. This process takes time but I really don’t see there’s any “problem”, if you go back to 2014 would you say Julia was in a horrible condition because basically all top contributors are JC?

---

<div class="post-metadata">

**Author:** ![bilderbuchi](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bilderbuchi/32/13562_2.png) [@bilderbuchi](https://discourse.julialang.org/u/bilderbuchi)\
**Post date:** [November 6, 2021, 9:24pm UTC](https://discourse.julialang.org/t/julias-business-model/70328/92 "2021-11-06T21:24:16Z")

</div>

> [@baggepinnen](#):
>
> Looks open source to me

Thanks, I was not aware of this yet (only “announcements” to expect, or pointers toward JuliaSim)! Happy about this brand-new development (and to be proven wrong), it makes MTK’s case much stronger imo! 🤩

---

<div class="post-metadata">

**Author:** ![lmiq](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lmiq/32/18314_2.png) [@lmiq](https://discourse.julialang.org/u/lmiq)\
**Post date:** [November 6, 2021, 10:03pm UTC](https://discourse.julialang.org/t/julias-business-model/70328/93 "2021-11-06T22:03:08Z")

</div>

As of today, one great incentive to youngsters contributing to the core Julia is the possibility of becoming a JC employee, which is probably one of the coolest places to work in computer science now.

One curiosity is how this mechanism of 1) new independent contributors appearing 2) they being incorporated to JC is taking place. Is that common?

---

<div class="post-metadata">

**Author:** ![oxinabox](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oxinabox/32/206603_2.png) [@oxinabox](https://discourse.julialang.org/u/oxinabox)\
**Post date:** [November 9, 2021, 3:18pm UTC](https://discourse.julialang.org/t/julias-business-model/70328/94 "2021-11-09T15:18:01Z")

</div>

I think it might actually be more common for new significant contributors to the language to end up at the Julia Lab at MIT (as PhD students or RSEs) than to end up at Julia Computing.  
Though I am aware of both happening in the last 6 months.

---

<div class="post-metadata">

**Author:** ![GregVernon](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gregvernon/32/5611_2.png) [@GregVernon](https://discourse.julialang.org/u/GregVernon)\
**Post date:** [November 10, 2021, 6:38am UTC](https://discourse.julialang.org/t/julias-business-model/70328/95 "2021-11-10T06:38:06Z")

</div>

> [@StefanKarpinski](#):
>
> We gave Julia the most liberal, permissive license we could—[the MIT license](https://en.wikipedia.org/wiki/MIT_License). It only requires that if you publish something that contains a substantial portion of Julia, you release it under the same license terms as Julia itself. That’s it. Otherwise you can use and modify it as you see fit.

So quick question then – we’ve considered at some point possibly rewriting our commercial products in Julia (currently C/C++). Are you saying that if we write our software in Julia we need to MIT license it, i.e. distribute our software and source-code for free? That doesn’t seem very liberal and permissive?

---

<div class="post-metadata">

**Author:** ![rashid](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/rashid/32/9398_2.png) [@rashid](https://discourse.julialang.org/u/rashid)\
**Post date:** [November 10, 2021, 7:02am UTC](https://discourse.julialang.org/t/julias-business-model/70328/96 "2021-11-10T07:02:49Z")

</div>

> [@GregVernon](#):
>
> Are you saying that if we write our software in Julia we need to MIT license it, i.e. distribute our software and source-code for free?

That is not true as mentioned earlier:

> [@stevengj](#):
>
> All the Julia contributors have explicitly given permission for _anyone_ to make and distribute a derived work, like a hypothetical “Julia+”, in which the new portions have additional restrictions (e.g. they are proprietary “closed source” commercial software). Nor is there any requirement to make the modified “Julia+” source code available (whether to customers of the binaries or to the original authors).

You can read more about the MIT license [here](https://fossa.com/blog/open-source-licenses-101-mit-license/). The only requirement to follow when redistributing a copy and/or modification is to include:

> - The original copyright notice
> - A copy of the license itself

---

<div class="post-metadata">

**Author:** ![gustaphe](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gustaphe/32/18174_2.png) [@gustaphe](https://discourse.julialang.org/u/gustaphe)\
**Post date:** [November 10, 2021, 7:07am UTC](https://discourse.julialang.org/t/julias-business-model/70328/97 "2021-11-10T07:07:13Z")

</div>

I think the important thing here, which is honestly a bit vague in the formulation of the license, is that you (afaict) must only provide the notice _in relation to the redistributed code_. So you can license _your_ code however you want, but the part of your program that is redistributed must be accompanied by its original license. But you can say “Files a, b and c are part of Julia and covered by the MIT license:”

---

<div class="post-metadata">

**Author:** ![Keno](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/keno/32/285_2.png) [@Keno](https://discourse.julialang.org/u/Keno)\
**Post date:** [November 10, 2021, 7:10am UTC](https://discourse.julialang.org/t/julias-business-model/70328/98 "2021-11-10T07:10:58Z")

</div>

> [@GregVernon](#):
>
> Are you saying that if we write our software in Julia we need to MIT license it, i.e. distribute our software and source-code for free?

No

---

<div class="post-metadata">

**Author:** ![GregVernon](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gregvernon/32/5611_2.png) [@GregVernon](https://discourse.julialang.org/u/GregVernon)\
**Post date:** [November 10, 2021, 7:12am UTC](https://discourse.julialang.org/t/julias-business-model/70328/99 "2021-11-10T07:12:08Z")

</div>

Ah, that makes a bit more sense – you’re right that (if you’re correct) is a subtlety-stated point. Glad to know the MIT license doesn’t “invade” the rest of a codebase.

---

<div class="post-metadata">

**Author:** ![DNF](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dnf/32/10191_2.png) [@DNF](https://discourse.julialang.org/u/DNF)\
**Post date:** [November 10, 2021, 8:01am UTC](https://discourse.julialang.org/t/julias-business-model/70328/100 "2021-11-10T08:01:42Z")

</div>

So, that discussion was somewhat beside the question you were asking. There was never any disagreement about whether you can choose what license you want on your own code. The discussion was about whether someone could fork and release the code of Julia, the language _itself_, with the compiler and everything, under a different license.

The freedom to license your own Julia code how you like was never in dispute.

---

<div class="post-metadata">

**Author:** ![GregVernon](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gregvernon/32/5611_2.png) [@GregVernon](https://discourse.julialang.org/u/GregVernon)\
**Post date:** [November 10, 2021, 6:50pm UTC](https://discourse.julialang.org/t/julias-business-model/70328/101 "2021-11-10T18:50:23Z")

</div>

> [@DNF](#):
>
> The discussion was about whether someone could fork and release the code of Julia, the language _itself_ , with the compiler and everything, under a different license.

Right, that’s what I thought we were talking about, but then reading this:

> [@StefanKarpinski](#):
>
> It only requires that if you publish something that contains a substantial portion of Julia _[…]_

“Something” – could be anything  
“Substantial portion” – if +90% of our codebase was written in Julia _and_ we redistribute Julia for API purposes, that would probably qualify as substantial.

It wouldn’t have thrown me off as much if it hadn’t come from a co-founder / co-creator of Julia.

[Previous page](https://discourse.julialang.org/t/julias-business-model/70328.md?page=4)

[Next page](https://discourse.julialang.org/t/julias-business-model/70328.md?page=6)
