# Get it together, guys!

**URL:** https://discourse.julialang.org/t/get-it-together-guys/27826
**Category:** Community
**Created:** [August 22, 2019, 2:07am UTC](https://discourse.julialang.org/t/get-it-together-guys/27826 "2019-08-22T02:07:40Z")
**Posts on this page:** 1
**Showing post:** 6

<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: [August 22, 2019, 5:02am UTC](https://discourse.julialang.org/t/get-it-together-guys/27826/6 "2019-08-22T05:02:46Z")

</div>

> [@Compiler work priorities](https://discourse.julialang.org/t/compiler-work-priorities/17623):
>
> In response to I thought I might write a little post about the rough priorities of the compiler team: Correctness finding and fixing compiler and inference bugs Multithreading [non-copying task stack switching](https://github.com/JuliaLang/julia/pull/13099) (done) [new PARTR parallel runtime](https://github.com/JuliaLang/julia/pull/22631)[locks for I/O operations](https://github.com/libuv/libuv/issues/1595) other thread safety Compile-time latency, aka “the time-to-first-plot problem” making compilation faster caching more things Compiler-related packages and tools [PackageCompiler](https://github.com/JuliaLang/PackageCompiler.jl) Debugger [Cxx](https://github.com/Keno/Cxx.jl) type checking/linting J…

This is a post where are the priorities of the development team. debugging and tools are after reducing latency (a problem a lot of the userbase is having, for what i have noticed in those discourse forums). So the team is aware of the need for tooling, but is not the top priority right now (offtopic, normally the community is mentioned as one of the strengths of the Julia language, and finding the development priorities in a post is a clear example)

> [@Brad\_Hines](#):
>
> When I buy Matlab, they don’t tell me that I need to buy professional support just to be able to use it. It just works

You are paying some thousands of dollars for that software, better be good 😄 , the same dollars could be invested in first class support from the Julia Team. but obviously depends of the use case. You want simulation of dynamical systems? Simulink is the industry standard right now. your workflow requires solving a lot of differential equations?, DifferencialEquations.jl moops the floor with ode15s.

One problem with MATLAB is deploying the software. MATLAB is excelent to prototype, but there is no way (as far as i know) to move the code to a production stage (if your product is software), or to generate pipelines compatible with computers without MATLAB (if your product is the data produced with your code)

If your Startup, after economic analysis, concludes that buying MATLAB licences is more cost-effective, that is totally fine, Julia has other strenghs that maybe you don’t need (or don’t see) right now, is not my job to sell you Julia nor to help you decide what you want to do with your business.

---

_[View the full topic](https://discourse.julialang.org/t/get-it-together-guys/27826)._