# JuliaBox and other ways to expose new users to Julia

**URL:** <https://discourse.julialang.org/t/juliabox-and-other-ways-to-expose-new-users-to-julia/4720>\
**Category:** Community\
**Tags:** juliabox, advocacy\
**Created:** [July 7, 2017, 5:21pm UTC](https://discourse.julialang.org/t/juliabox-and-other-ways-to-expose-new-users-to-julia/4720 "2017-07-07T17:21:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon94023334](https://avatars.discourse-cdn.com/v4/letter/a/e274bd/32.png) [@anon94023334](https://discourse.julialang.org/u/anon94023334)\
**Post date:** [July 7, 2017, 5:21pm UTC](https://discourse.julialang.org/t/juliabox-and-other-ways-to-expose-new-users-to-julia/4720/1 "2017-07-07T17:21:24Z")

</div>

I wanted to report an issue with JuliaBox (should be simple to fix) and to suggest another avenue that I’ve found particularly helpful when evaluating a new language.

1. JuliaBox currently only has 0.6.0-rc2 and 0.7.0-DEV as (modern) kernels. The 0.6.0-rc2 version is limited to outdated packages that are known to be broken in some cases. It’d be really helpful to ensure that JuliaBox is on -RELEASE.

2. It would be supremely cool to have an in-browser REPL on [julialang.org](http://julialang.org)’s homepage, similar to what [Haskell](https://www.haskell.org), [Go](https://golang.org), [Rust](http://rust-lang.org), and others do.

The former should probably be resolved; the latter is merely a suggestion for discussion.