# Why is Julia so great?

**URL:** <https://discourse.julialang.org/t/why-is-julia-so-great/94718>\
**Category:** New to Julia\
**Created:** [February 16, 2023, 11:09am UTC](https://discourse.julialang.org/t/why-is-julia-so-great/94718 "2023-02-16T11:09:58Z")\
**Posts on this page:** 1\
**Showing post:** 75

<div class="post-metadata">

**Author:** ![aplavin](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/aplavin/32/222056_2.png) [@aplavin](https://discourse.julialang.org/u/aplavin)\
**Post date:** [April 13, 2023, 11:41am UTC](https://discourse.julialang.org/t/why-is-julia-so-great/94718/75 "2023-04-13T11:41:43Z")

</div>

> [@asbisen](#):
>
> For some reason I don’t see a lot of adoption of DuckDB in the Julia ecosystem. Probably that’s the reason it’s feature parity vis-a-vis Python has started to lag.

I looked at DuckDB to replace SQLite in some usecases, but their Julia package seems (1) not well-integrated, eg regarding julia tables support, (2) heavy in terms of dependencies ([48 deps](https://juliahub.com/ui/Packages/DuckDB/89qwz/0.7.0?page=1), many are nontrivial), and (3) as I understand, doesn’t use basic julia testing practices.  
I didn’t even manage to run their tests when trying to improve (1):

> [@Write a table into SQLite and DuckDB in efficient manner](https://discourse.julialang.org/t/write-a-table-into-sqlite-and-duckdb-in-efficient-manner/93417/22):
>
> A cursory look suggests converting that file from dataframes to arbitrary tables (through columntable) is pretty easy. However, I cannot simply run DuckDB.jl tests successfully, all of these fail for me: ]dev DuckDB + ]test DuckDB clone duckdb, go to juliapkg dir, do ]test clone duckdb, go to juliapkg dir, do ./test.sh Also, their contribution rules aren’t clear: do you know if they even accept outside PRs?

Maybe they just don’t consider julia integration that important, idk.

---

_[View the full topic](https://discourse.julialang.org/t/why-is-julia-so-great/94718)._