# Results regarding Julia from HackerRank developer skills report **URL:** \ **Category:** Community\ **Created:** [January 24, 2018, 10:12pm UTC](https://discourse.julialang.org/t/results-regarding-julia-from-hackerrank-developer-skills-report/8574 "2018-01-24T22:12:06Z")\ **Posts on this page:** 7\ **Page:** 2

**Author:** ![ScottPJones](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/scottpjones/32/146_2.png) [@ScottPJones](https://discourse.julialang.org/u/ScottPJones)\ **Post date:** [January 27, 2018, 12:23pm UTC](https://discourse.julialang.org/t/results-regarding-julia-from-hackerrank-developer-skills-report/8574/21 "2018-01-27T12:23:51Z")

> [@ChrisRackauckas](#): > > Some people’s problems are simple enough that somebody else has already written a package for it. And it’s great that we have people like Chris who are _making_ even people’s complex problems simple! ---

**Author:** ![ScottPJones](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/scottpjones/32/146_2.png) [@ScottPJones](https://discourse.julialang.org/u/ScottPJones)\ **Post date:** [January 27, 2018, 12:28pm UTC](https://discourse.julialang.org/t/results-regarding-julia-from-hackerrank-developer-skills-report/8574/22 "2018-01-27T12:28:01Z")

> [@Yifan\_Liu](#): > > Julia should stick to heavy-duty numerical computing, like Fortran and Matlab. This niche is clear and makes a lot of sense to me. No, no, no!!! Julia should continue to support marvelously heavy-duty numerical computing, yes. Julia should _not_ be kept in a niche, away from general purpose programmers (and bit-twiddlers!) like me. (Sometimes I feel like some of the Julia supporters are like Gollum, with Julia as their “precious”! 😆 ) Don’t hide Julia under a rock! ---

**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:** [January 27, 2018, 12:48pm UTC](https://discourse.julialang.org/t/results-regarding-julia-from-hackerrank-developer-skills-report/8574/23 "2018-01-27T12:48:02Z")

> [@ScottPJones](#): > > Don’t hide Julia under a rock! I am not sure what you are referring to. AFAICT no one is hiding anything from anyone, the language is actively promoted on many forums. Also, the wide breadth of registered and unregistered packages make it hard argue that julia is “kept in a niche” in any way. ---

**Author:** ![ScottPJones](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/scottpjones/32/146_2.png) [@ScottPJones](https://discourse.julialang.org/u/ScottPJones)\ **Post date:** [January 27, 2018, 12:53pm UTC](https://discourse.julialang.org/t/results-regarding-julia-from-hackerrank-developer-skills-report/8574/24 "2018-01-27T12:53:04Z")

I was simply replying to the comment “Julia should stick to heavy-duty numerical computing”. I’ve seen that attitude a lot, a number of people in the community don’t care so much about changes to Julia that could help it for general purpose computing (like better string handling or packages for database access), but are willing to spend years discussing just exactly how to do transposes correctly 😀 ---

**Author:** ![zhangliye](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/zhangliye/32/3208_2.png) [@zhangliye](https://discourse.julialang.org/u/zhangliye)\ **Post date:** [January 27, 2018, 2:48pm UTC](https://discourse.julialang.org/t/results-regarding-julia-from-hackerrank-developer-skills-report/8574/25 "2018-01-27T14:48:54Z")

Agree. In my research institute, I try to persuade my colleagues to use Julia for a data analysis project. However, we find there are not so many mature packages, such as Dask and Django. I wrote a demo with Dagger in Julia language, but I cannot make it work correctly. My colleagues finished that with few lines of code with Dask in Python. Moreover, the group members including me are familiar with Python. At last, we decided to use Python. For the daily work, mature packages are important factors to select a language. ---

**Author:** ![xiaodai](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xiaodai/32/15937_2.png) [@xiaodai](https://discourse.julialang.org/u/xiaodai)\ **Post date:** [January 27, 2018, 10:03pm UTC](https://discourse.julialang.org/t/results-regarding-julia-from-hackerrank-developer-skills-report/8574/26 "2018-01-27T22:03:34Z")

the data ecosystem isn’t as well developed just yet ---

**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:** [January 28, 2018, 8:30am UTC](https://discourse.julialang.org/t/results-regarding-julia-from-hackerrank-developer-skills-report/8574/27 "2018-01-28T08:30:47Z")

> [@zhangliye](#): > > However, we find there are not so many mature packages, such as Dask and Django. Given the current state of the package ecosystem, you frequently need to invest some time in a package that you want to use in a production setting, to the point of becoming familiar enough with the internals to submit PRs. Generally, this is how open source works. Projects becoming as mature and polished as some prominent packages in the Python and R ecosystems is more of an exception than the rule, and they also started out this way. > [@zhangliye](#): > > I try to persuade my colleagues to use Julia for a data analysis project. I find that this strategy can easily backfire. Committing to Julia at this point requires a certain mindset, not unlike flying the Millenium Falcon: it is designed to be blazingly fast, but things can break down at inconvenient moments and then you have to be able to repair them. This is perhaps more suited for research than production. [Previous page](https://discourse.julialang.org/t/results-regarding-julia-from-hackerrank-developer-skills-report/8574.md?page=1)