# Julia is Ranked 35th on the TIOBE Index

**URL:** <https://discourse.julialang.org/t/julia-is-ranked-35th-on-the-tiobe-index/7026>\
**Category:** Community\
**Tags:** blog\
**Created:** [November 12, 2017, 5:09pm UTC](https://discourse.julialang.org/t/julia-is-ranked-35th-on-the-tiobe-index/7026 "2017-11-12T17:09:25Z")\
**Posts on this page:** 10\
**Page:** 3

<div class="post-metadata">

**Author:** ![chakravala](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chakravala/32/6832_2.png) [@chakravala](https://discourse.julialang.org/u/chakravala)\
**Post date:** [April 3, 2019, 3:16pm UTC](https://discourse.julialang.org/t/julia-is-ranked-35th-on-the-tiobe-index/7026/41 "2019-04-03T15:16:43Z")

</div>

Yet again, it sounds like the Julia website could greatly benefit from having a generic open source / free software tutorial video, which explains how to work with git and how to best interact with the rest of the julia community.

Most new users at this point will not have the necessary background, and their transition would be greatly accelerated by having this standard tutorial on the main julia homepage.

This would help eliminate some of the redundancy on the discourse and assist when introducing collaborators to julia workflow.

---

<div class="post-metadata">

**Author:** ![pdeffebach](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pdeffebach/32/10320_2.png) [@pdeffebach](https://discourse.julialang.org/u/pdeffebach)\
**Post date:** [April 3, 2019, 3:24pm UTC](https://discourse.julialang.org/t/julia-is-ranked-35th-on-the-tiobe-index/7026/42 "2019-04-03T15:24:47Z")

</div>

> [@Tamas\_Papp](#):
>
> I think that the biggest selling point of version control is the ability to review and comment each other’s code on Github/Gitlab/… .

This 100%. Even having persistent discussions about changes to the text and results of a paper is enormously helpful. It can ensure PIs are on the same page with a change and that results aren’t jumping around more than they ought to with small refinements. A selling point of Julia could be that this kind of _way more effective collaboration_ is easy and built into the language.

---

<div class="post-metadata">

**Author:** ![jacobadenbaum](https://avatars.discourse-cdn.com/v4/letter/j/5daacb/32.png) [@jacobadenbaum](https://discourse.julialang.org/u/jacobadenbaum)\
**Post date:** [April 3, 2019, 3:35pm UTC](https://discourse.julialang.org/t/julia-is-ranked-35th-on-the-tiobe-index/7026/43 "2019-04-03T15:35:54Z")

</div>

> [@Tamas\_Papp](#):
>
> when we build code for estimating a structural economic model, I first write a quick & dirty version with extensive tests,

Sorry if this a bit off topic, but I’d be really interested in what your tests look like for these kinds of models. Like, I have a really good sense of how to write unit tests for packages that are mostly tooling, but I am often a little lost on what they should look like when most of the code is written for an iterative method.

---

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [April 3, 2019, 3:43pm UTC](https://discourse.julialang.org/t/julia-is-ranked-35th-on-the-tiobe-index/7026/44 "2019-04-03T15:43:28Z")

</div>

> [@jacobadenbaum](#):
>
> what your tests look like for these kinds of models

The code will (of course) be public when the paper is published, but think of eg the following:

1. equilibrium conditions hold (in a numerically approximate sense) for the numerically obtained solution,

2. for value functions, you can simulate paths and get discounted present value, and compare,

3. transition matrices (for simulating a discretized model) sum to 1 (amazing what that uncovers 😉), also compare to toy 2x2 versions,

4. analytically calculated moments are roughly equal to simulated versions (when we have both).

5. a bunch of `@inferred` peppered through the tests (we want speed, changes should keep the compiler happy).

It is not really that different from any other kind of code. Initially, it is kind of hard to think of invariants you want to maintain and toy versions of your model to solve, but it becomes kind of a habit. Also, simplified versions of the model are super-useful for presentations.

---

<div class="post-metadata">

**Author:** ![doomphoenix-qxz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/doomphoenix-qxz/32/7009_2.png) [@doomphoenix-qxz](https://discourse.julialang.org/u/doomphoenix-qxz)\
**Post date:** [April 3, 2019, 3:56pm UTC](https://discourse.julialang.org/t/julia-is-ranked-35th-on-the-tiobe-index/7026/45 "2019-04-03T15:56:04Z")

</div>

While I agree that git or other version control is the long-term way to go for scientific research, it’s a pretty high barrier for somebody who’s new to programming and might feel overwhelmed by having to learn programming, a new language, _and_ git. Even if they know (some) programming, needing to learn git gives Julia a much higher learning curve than Python or Matlab (which are its main competitors if they’re a non-CS trained engineer like me).

I also don’t think learning git is strictly necessary to be able to use Julia for throwaway scripts. It shouldn’t be too hard to teach people a simple Revise-based workflow in which they open a REPL, import packages needed by their script directly in the REPL session, `includet` their script, then just call the ` __main__ ()` function from their script, edit as needed, save, call it again and repeat as necessary. It may take them 10 minutes to get used to but it will quickly feel as easy as writing a script in Python. Then, after they’ve discovered how nice Julia is, it will be easier to show them “My actual workflow looks like this, because I use git and unit tests. Unit tests help you prove that small a piece of code does what you think it does, and git helps you keep track of changes over time.”

Then again, these are just my thoughts based on how I like to learn new things, and I actually haven’t yet needed to teach anybody else to use Julia.

---

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [April 3, 2019, 4:33pm UTC](https://discourse.julialang.org/t/julia-is-ranked-35th-on-the-tiobe-index/7026/46 "2019-04-03T16:33:41Z")

</div>

> [@doomphoenix-qxz](#):
>
> might feel overwhelmed by having to learn programming, a new language, _and_ git

I think learning Julia + git (CI is kind of thrown in, it’s more of a habit 😉) is for someone who knows how to program already (in any language), and is somewhat computer-savvy (power user level, can install programs, interpret an error message, follow a tutorial).

I don’t think anyone would suggest that someone who is learning _programming_ as something new start with all this. But for those people, I may not recommend Julia anyway — it is possible to learn as a first programming language, but a lot of the details just won’t make sense for a while.

---

<div class="post-metadata">

**Author:** ![tamasgal](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamasgal/32/27946_2.png) [@tamasgal](https://discourse.julialang.org/u/tamasgal)\
**Post date:** [October 2, 2020, 8:54am UTC](https://discourse.julialang.org/t/julia-is-ranked-35th-on-the-tiobe-index/7026/47 "2020-10-02T08:54:36Z")

</div>

For everyone who feels better when Julia bubbles to the top of the TIOBE index:

As of **September 2020, Julia is rank 28** with a rating of 0.55%, above Scala, Scheme, Lisp, Fortran, Haskell and Clojure and right below D.

---

<div class="post-metadata">

**Author:** ![longemen3000](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/longemen3000/32/7298_2.png) [@longemen3000](https://discourse.julialang.org/u/longemen3000)\
**Post date:** [December 14, 2020, 12:49am UTC](https://discourse.julialang.org/t/julia-is-ranked-35th-on-the-tiobe-index/7026/48 "2020-12-14T00:49:03Z")

</div>

December 2020 update:

Julia surpassed D, and sits now at 26th place

---

<div class="post-metadata">

**Author:** ![tamasgal](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamasgal/32/27946_2.png) [@tamasgal](https://discourse.julialang.org/u/tamasgal)\
**Post date:** [December 14, 2020, 8:15am UTC](https://discourse.julialang.org/t/julia-is-ranked-35th-on-the-tiobe-index/7026/49 "2020-12-14T08:15:04Z")

</div>

Top20 for 2021 is quite realistic I guess and I assume that it will be a self-enhancing thing 🙂

---

<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:** [December 14, 2020, 1:42pm UTC](https://discourse.julialang.org/t/julia-is-ranked-35th-on-the-tiobe-index/7026/50 "2020-12-14T13:42:07Z")

</div>

Julia was ranked 6th in “[the most loved languages](https://insights.stackoverflow.com/survey/2020#most-loved-dreaded-and-wanted)” in this year’s stack overflow developer’s survey. Just mentioning as I didn’t see anyone mentioning this here or elsewhere. Julia was ranked after Rust, TypeScript, Python, Kotlin and Go.

[Previous page](https://discourse.julialang.org/t/julia-is-ranked-35th-on-the-tiobe-index/7026.md?page=2)
