# Questions about Julialang: The Ingredients for a Composable Programming Language

**URL:** <https://discourse.julialang.org/t/questions-about-julialang-the-ingredients-for-a-composable-programming-language/37646>\
**Category:** Community\
**Created:** [April 15, 2020, 2:28pm UTC](https://discourse.julialang.org/t/questions-about-julialang-the-ingredients-for-a-composable-programming-language/37646 "2020-04-15T14:28:34Z")\
**Posts on this page:** 3\
**Page:** 1

<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:** [April 15, 2020, 2:28pm UTC](https://discourse.julialang.org/t/questions-about-julialang-the-ingredients-for-a-composable-programming-language/37646/1 "2020-04-15T14:28:34Z")

</div>

I read this article from @oxinabox with great interest and it’s a great article (and talk)  
[https://t.co/AdeHABesNW?amp=1](https://t.co/AdeHABesNW?amp=1)

One point that I found very interesting was that

> Open classes:
> 
> - so you can create new methods in your package for types/functions declared in another package

and that

> Name collisions make package authors come together and create base packages (like `StatsBase` ) and agree on what the functions mean.

I see this happening with `Tables.jl`.

So my questions is: what do people think are challenge we as a community will face in the future as the community gets bigger and more people are involved in developing packages? Will coordinating and coming up with and agreeing to a common baseline become harder and harder?

---

<div class="post-metadata">

**Author:** ![Oscar\_Smith](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oscar_smith/32/25343_2.png) [@Oscar\_Smith](https://discourse.julialang.org/u/Oscar_Smith)\
**Post date:** [April 15, 2020, 2:33pm UTC](https://discourse.julialang.org/t/questions-about-julialang-the-ingredients-for-a-composable-programming-language/37646/2 "2020-04-15T14:33:51Z")

</div>

To some extent this gets harder, on the other hand, the good news is that many of these conventions have already been made. As long as Julia doesn’t have many fundamental changes most of these decisions have already been made, and don’t need to be made again.

---

<div class="post-metadata">

**Author:** ![oxinabox](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oxinabox/32/206603_2.png) [@oxinabox](https://discourse.julialang.org/u/oxinabox)\
**Post date:** [April 16, 2020, 5:29pm UTC](https://discourse.julialang.org/t/questions-about-julialang-the-ingredients-for-a-composable-programming-language/37646/3 "2020-04-16T17:29:47Z")

</div>

> [@xiaodai](#):
>
> Will coordinating and coming up with and agreeing to a common baseline become harder and harder?

I don’t know, but in a way, and one of the points of that talk is the language almost forces it to happen.  
Which helps with the [Lisp Curse](http://winestockwebdesign.com/Essays/Lisp_Curse.html) I think

(Aside: Tables.jl would have been a better example than StatsBase.)