# What are your most coveted functionalities missing in the ecosystem?

**URL:** <https://discourse.julialang.org/t/what-are-your-most-coveted-functionalities-missing-in-the-ecosystem/26962>\
**Category:** Community\
**Tags:** package, proposal\
**Created:** [July 30, 2019, 2:18am UTC](https://discourse.julialang.org/t/what-are-your-most-coveted-functionalities-missing-in-the-ecosystem/26962 "2019-07-30T02:18:23Z")\
**Posts on this page:** 16\
**Page:** 3

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [August 5, 2019, 9:45pm UTC](https://discourse.julialang.org/t/what-are-your-most-coveted-functionalities-missing-in-the-ecosystem/26962/42 "2019-08-05T21:45:28Z")

</div>

I think code-server might also work, but my guess is that the various remote extensions that MS is putting out are probably a more stable story. But not sure, I haven’t really tried 🙂

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [August 5, 2019, 9:47pm UTC](https://discourse.julialang.org/t/what-are-your-most-coveted-functionalities-missing-in-the-ecosystem/26962/43 "2019-08-05T21:47:58Z")

</div>

> [@juliohm](#):
>
> Does VegaLite.jl support plot recipes?

No, not at this point. I assume it is something that could be added, though, but I’m not familiar enough with that ecosystem right now. Has the whole plots recipe story settled, or is that all in flux with the imminent Makie.jl story? I have to admit I haven’t followed this closely. BUT, it would be great to use vega and vega-lite plotting capabilities for non grammar of graphics APIs as well.

---

<div class="post-metadata">

**Author:** ![juliohm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/juliohm/32/215266_2.png) [@juliohm](https://discourse.julialang.org/u/juliohm)\
**Post date:** [August 5, 2019, 9:51pm UTC](https://discourse.julialang.org/t/what-are-your-most-coveted-functionalities-missing-in-the-ecosystem/26962/44 "2019-08-05T21:51:05Z")

</div>

I think the recipes API is still evolving because of Makie.jl. Maintainers of these projects already pointed out that their plan is to migrate all existing recipes as smooth as possible to the new ecosystem.

---

<div class="post-metadata">

**Author:** ![tkf](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkf/32/17635_2.png) [@tkf](https://discourse.julialang.org/u/tkf)\
**Post date:** [August 5, 2019, 10:44pm UTC](https://discourse.julialang.org/t/what-are-your-most-coveted-functionalities-missing-in-the-ecosystem/26962/45 "2019-08-05T22:44:01Z")

</div>

Vega-Lite and Vega themselves _are_ language-agnostic recipe systems (plus the runtime implemented in JavaScript). I think a better direction is to implement Vega-Lite/Vega runtime in Julia to handle amount of data which is too large to put in row-oriented JSON format. It would be beneficial for people outside Julia community, too. Of course, this is a pretty ambitious project… (Also, there is already [https://github.com/vega/vega-loader-arrow](https://github.com/vega/vega-loader-arrow) so this may not be necessary at all)

---

<div class="post-metadata">

**Author:** ![RoyiAvital](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/royiavital/32/571_2.png) [@RoyiAvital](https://discourse.julialang.org/u/RoyiAvital)\
**Post date:** [August 6, 2019, 10:20am UTC](https://discourse.julialang.org/t/what-are-your-most-coveted-functionalities-missing-in-the-ecosystem/26962/46 "2019-08-06T10:20:29Z")

</div>

My wish list:

1. Simple way to generate independent Shared / Static Libraries from Julia code which doesn’t require embedding Julia when linked to a C / C++ code. With support for Windows, macOS and Linux.
2. Easily generate standalone applications from Julia code with UI.
3. First class support for Intel MKL with all optimizations (JIT in MKL, Batch API, Compact API, etc…). Including utilizing MKL Solvers, MKL Sparse Matrices support, etc…
4. First class support for Intel SVML.
5. Better control for vectorization of code.

---

<div class="post-metadata">

**Author:** ![JackDevine](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jackdevine/32/1048_2.png) [@JackDevine](https://discourse.julialang.org/u/JackDevine)\
**Post date:** [August 6, 2019, 11:59pm UTC](https://discourse.julialang.org/t/what-are-your-most-coveted-functionalities-missing-in-the-ecosystem/26962/47 "2019-08-06T23:59:00Z")

</div>

This is a little off topic with regards to the original post, feel free to split this discussion out into a separate thread.

> [@davidanthoff](#):
>
> it would be great to use vega and vega-lite plotting capabilities for non grammar of graphics APIs as well.

Yes, that sounds very interesting. Reading through the [paper](https://idl.cs.washington.edu/files/2017-VegaLite-InfoVis.pdf) explaining vega-lite, it seems to me that there are shared goals between vega-lite and Makie with respect to interactivity. One key advantage of vega-lite is that you can send interactive visualizations to people and they can open it in their browsers without jumping over any installation hurdles. My understanding is that [WGLMakie](https://github.com/JuliaPlots/WGLMakie.jl) will bring similar functionality to Makie.

To me, the logical way to make vega/vega-lite available in a non grammar of graphics form would be to make a vega/vega-lite backend for either Plots.jl or Makie.jl. Or were you thinking of making a non grammar of graphics API that is separate to those packages?

Making a separate API would be sad because then you can’t support plot recipes. However, making vega-lite a backend to Plots/Makie is also sad because then you lose the grammar of interactive graphics which one of the central features of vega-lite.

Maybe we should just be greedy and do both.

---

<div class="post-metadata">

**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:** [August 7, 2019, 12:49am UTC](https://discourse.julialang.org/t/what-are-your-most-coveted-functionalities-missing-in-the-ecosystem/26962/48 "2019-08-07T00:49:47Z")

</div>

Complete Elimination of compilation latency! When installling a package, I imagine a scrip called, to\_compile.jl can be supplied with the package and anything contained within it will be compiled, so that when you load up a packages it just loads the compile versions so it starts up until you try to run a funcion that isn’t in the to\_compile.jl then it will compile, otherwise my true feelings are that Julia feel too “lethargic” to use. But compiliation latency is a top prioritise as listed in the “What’s bad about Julia” talk at Juliacon 2019. So I am sure something is being worked on.

---

<div class="post-metadata">

**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:** [August 7, 2019, 12:54am UTC](https://discourse.julialang.org/t/what-are-your-most-coveted-functionalities-missing-in-the-ecosystem/26962/49 "2019-08-07T00:54:43Z")

</div>

> [@Nosferican](#):
>
> that it may handle bigger than RAM memory data.

JuliaDB.jl! Everytime it nevered worked for my use-case and the thing is I can’t share the data that I tried to use it with! So I can’t give the JuliaDB team much useful info! Also some key features seems to be missing from JuliaDB (e.g. [chunks argument to loadtable not working as expected · Issue #257 · JuliaData/JuliaDB.jl · GitHub](https://github.com/JuliaComputing/JuliaDB.jl/issues/257)).

I still use R for larger data because JuliaDB.jl doesn’t work on my data. It’s hard to beat R’s data.table though, so I have builit a R medium data tool ([GitHub - DiskFrame/disk.frame: Fast Disk-Based Parallelized Data Manipulation Framework for Larger-than-RAM Data](https://github.com/xiaodaigh/disk.frame)) which is generating some interests in the R community. Once I am happy with the R pacakge, I might create a disk.frame.jl package. I think CSV.jl and DataFrames.jl have come a long way!

---

<div class="post-metadata">

**Author:** ![mirkobunse](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mirkobunse/32/7244_2.png) [@mirkobunse](https://discourse.julialang.org/u/mirkobunse)\
**Post date:** [December 11, 2019, 9:34am UTC](https://discourse.julialang.org/t/what-are-your-most-coveted-functionalities-missing-in-the-ecosystem/26962/50 "2019-12-11T09:34:37Z")

</div>

Hi @Maurizio_Tomasi,

since the pull request [#68](https://github.com/BioJulia/YAML.jl/pull/68) has been merged, [YAML.jl](https://github.com/BioJulia/YAML.jl) is able to emit Julia objects to YAML files (and YAML-formatted strings).

---

<div class="post-metadata">

**Author:** ![John\_Gibson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/john_gibson/32/5321_2.png) [@John\_Gibson](https://discourse.julialang.org/u/John_Gibson)\
**Post date:** [December 11, 2019, 12:51pm UTC](https://discourse.julialang.org/t/what-are-your-most-coveted-functionalities-missing-in-the-ecosystem/26962/51 "2019-12-11T12:51:48Z")

</div>

A Julia interface to distributed-memory FFTW-MPI that works with DistributedArrays.jl.

---

<div class="post-metadata">

**Author:** ![jablauvelt](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jablauvelt/32/8792_2.png) [@jablauvelt](https://discourse.julialang.org/u/jablauvelt)\
**Post date:** [December 12, 2019, 7:55pm UTC](https://discourse.julialang.org/t/what-are-your-most-coveted-functionalities-missing-in-the-ecosystem/26962/52 "2019-12-12T19:55:04Z")

</div>

A dataframe package that works and is fast as data.table in R. This would be a killer feature to bring over a lot of people that use R and Python for data analysis, which in turn would bring even more development support.

---

<div class="post-metadata">

**Author:** ![anon92994695](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@anon92994695](https://discourse.julialang.org/u/anon92994695)\
**Post date:** [December 12, 2019, 11:11pm UTC](https://discourse.julialang.org/t/what-are-your-most-coveted-functionalities-missing-in-the-ecosystem/26962/53 "2019-12-12T23:11:30Z")

</div>

More generic UI widgets. IE: Interactive plots, click and drag event listeners.

---

<div class="post-metadata">

**Author:** ![Sijun](https://avatars.discourse-cdn.com/v4/letter/s/b2d939/32.png) [@Sijun](https://discourse.julialang.org/u/Sijun)\
**Post date:** [December 13, 2019, 1:20am UTC](https://discourse.julialang.org/t/what-are-your-most-coveted-functionalities-missing-in-the-ecosystem/26962/54 "2019-12-13T01:20:31Z")

</div>

I wish Julia version of Simulink. It will be the lethal strike to Matlab.

---

<div class="post-metadata">

**Author:** ![ChrisRackauckas](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chrisrackauckas/32/77_2.png) [@ChrisRackauckas](https://discourse.julialang.org/u/ChrisRackauckas)\
**Post date:** [December 13, 2019, 1:52am UTC](https://discourse.julialang.org/t/what-are-your-most-coveted-functionalities-missing-in-the-ecosystem/26962/55 "2019-12-13T01:52:05Z")

</div>

Hold your horses.

---

<div class="post-metadata">

**Author:** ![JesseSantoso](https://avatars.discourse-cdn.com/v4/letter/j/dfb087/32.png) [@JesseSantoso](https://discourse.julialang.org/u/JesseSantoso)\
**Post date:** [December 13, 2019, 5:13am UTC](https://discourse.julialang.org/t/what-are-your-most-coveted-functionalities-missing-in-the-ecosystem/26962/56 "2019-12-13T05:13:10Z")

</div>

The option to create concretely “typed” functions similar to FunctionWrappers.jl (except without the ccall and both the run time and compilation overheads which are currently killing me).

---

<div class="post-metadata">

**Author:** ![Nosferican](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nosferican/32/9275_2.png) [@Nosferican](https://discourse.julialang.org/u/Nosferican)\
**Post date:** [December 19, 2019, 5:21am UTC](https://discourse.julialang.org/t/what-are-your-most-coveted-functionalities-missing-in-the-ecosystem/26962/57 "2019-12-19T05:21:32Z")

</div>

I want to share that I have worked on getting my top coveted functionality for the ecosystem.

> [@Reviving WebDriver.jl](https://discourse.julialang.org/t/reviving-webdriver-jl/32468):
>
> I am pleased to share my initial draft towards reviving WebDriver.jl for Julia v1 at The package allows to interact with a remote web driver and covers most of the implementation in the current Selenium WebDriver project (i.e., a mix of the W3C WebDriver [API](https://w3c.github.io/webdriver/) and the JSON Wire [Protocol](https://github.com/SeleniumHQ/selenium/wiki/JsonWireProtocol)). Check it out and let me know comments, feedback, and PR are encouraged.

[Previous page](https://discourse.julialang.org/t/what-are-your-most-coveted-functionalities-missing-in-the-ecosystem/26962.md?page=2)