# Julia 1.2 in Nextjournal

**URL:** <https://discourse.julialang.org/t/julia-1-2-in-nextjournal/27801>\
**Category:** Tooling\
**Tags:** announcement, cloud-computing\
**Created:** [August 21, 2019, 2:47pm UTC](https://discourse.julialang.org/t/julia-1-2-in-nextjournal/27801 "2019-08-21T14:47:15Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![sdanisch](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sdanisch/32/1406_2.png) [@sdanisch](https://discourse.julialang.org/u/sdanisch)\
**Post date:** [August 21, 2019, 2:47pm UTC](https://discourse.julialang.org/t/julia-1-2-in-nextjournal/27801/1 "2019-08-21T14:47:15Z")

</div>

Hi everyone,

I’m happy to announce that [Nextjournal](https://nextjournal.com/) updated all default images to [Julia 1.2](https://nextjournal.com/nextjournal/julia-environment/)! Any new article with Julia code cells will now default to this image. There is also a [collection](https://nextjournal.com/julia) with more images that come with packages pre-installed like [DifferentialEquations](https://nextjournal.com/julia/differentialequations), [Plots](https://nextjournal.com/julia/plots), [Makie with WebGL](https://nextjournal.com/julia/webgl-makie), [Julia 1.3](https://nextjournal.com/julia/julia-13) etc. Most of those are ahead of time compiled with [PackageCompiler](https://github.com/JuliaLang/PackageCompiler.jl) to drastically reduce compilation times. Just remix those to get started, or directly [import those images via the runner menu](https://nextjournal.com/help/runtimes-environments#importing-environments).

Let me know if anything is missing, best with an article that installs the packages you feel should be a default!

## Why should you try Nextjournal?

- Come for the Jupyter like [work flow](https://nextjournal.com/help/editor-basics), [GPU support](https://nextjournal.com/help/runtimes-environments#configuring-gpus-and-memory) and [interactivity](https://nextjournal.com/julia/webio-template)
- Stay for the ease to publish reproducible articles with one click, that contain [all data, software and code](https://nextjournal.com/help/runtimes-environments#saving-environments)
- [Remix notebooks, start where the author left](https://nextjournal.com/help/how-to-remix)
- Reproducibility is achieved by turning notebooks and their dependencies into docker containers, so Nextjournal is actually a pretty nice API for creating docker containers
- [Real time collaboration](https://nextjournal.com/help/collaboration)
- [Uploading files](https://nextjournal.com/help/working-with-code-and-data#working-with-uploaded-files), [mounting AWS/Google file storage](https://nextjournal.com/help/s3-gcs)
- [Using secrets](https://nextjournal.com/help/using-secrets)
- [Import/export markdown and Jupyter notebooks](https://nextjournal.com/help/import)
- [Support](https://nextjournal.com/help/quickstart#what-next%3F) & [documentation](https://nextjournal.com/help/)

## What use cases are we imagining

- Scientific/technical blogging, much like all the great [JSOC blog posts on Nextjournal](https://nextjournal.com/jsoc)
- Interactive documentation, tutorials & teaching
- Team collaboration in companies/universities/research groups
- Sharing data analysis with clients or other team members
- Publishing interactive and [reproducible papers](https://nextjournal.com/csi/microbiome-interactions-shape-host-fitness)

## What’s missing

There are a couple of features we are aware off, that are still missing:

- Turning Github repositories / folders into a collection of notebooks
- Notebooks with multiple pages
- Embedding Nextjournal into a web pages
- Editing files stored in the container, e.g. files in a Julia package
- More Medium like features, e.g. liking notebooks, viewing statistics, feed with popular notebooks, meta groups & tagging articles, RSS feeds
- Running Nextjournal on your own hardware
- Open sourcing Nextjournal
- Line by line evaluation and other fancy editor features

Let us know if you’re missing anything, or if there are any deal breaker that hold you back from adopting Nextjournal. We’re open to prioritize certain features! We’re also trying to get more adoption in the teaching & tutorial space, so if you would like to use Nextjournal for that let us know! We’d love to help you get started and have a chat! 🙂

## A little more background

We’re a [small company based in Berlin and completely self funded](https://nextjournal.com/about) - which gives us the freedom to stay true to our ideals!

The creation of Nextjournal was heavily inspired by Bret Victor’s great article: [What can a technologist do about climate change](http://worrydream.com/ClimateChange/). The article motivates, along lots of other topics, to invest time and resources into Julia and explorable programming to fight climate change! It also suggests, that it’s crucial to bundle data, tools and models into articles, to foster fact based discussions. This was pretty much the main driving factor behind our great support for Julia, Open Science and the reproducibility & interactivity of articles.

To implement this vision with maximal flexibility, Nextjournal was written from scratch and, for the better or worse, is not relying on Jupyter. This gives us the freedom to implement our own features without being restricted to the Jupyter protocol. However, to get the best of both worlds, we did implement the [Jupyter protocol](https://nextjournal.com/help/runtimes-environments#runtime-settings) and we also allow users to import Jupyter notebooks! The custom protocol also doesn’t mean that you will get stuck with Nextjournal: you can always export your notebooks as markdown, which works nicely together with e.g. Weave.jl & Atom, or can be imported back into Jupyter.

I hope this helps to better judge what Nextjournal is and how you can use it 🙂 If you have any more questions, don’t hesitate to reach out to me.

Best,  
Simon

---

<div class="post-metadata">

**Author:** ![Joshua\_Bowles](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joshua_bowles/32/4515_2.png) [@Joshua\_Bowles](https://discourse.julialang.org/u/Joshua_Bowles)\
**Post date:** [August 22, 2019, 12:17am UTC](https://discourse.julialang.org/t/julia-1-2-in-nextjournal/27801/2 "2019-08-22T00:17:37Z")

</div>

Awesome. I started giving Nextjournal a try and love it.  
I’ve never been able to blog about the things I want because the mix of code and math meant I always had to trade better math formatting and explanation over long-winded explication of the code and data structures. And often with code it’s enough to print out a formatted result to get the intuition, to see the result, and how it relates to the math… Nextjournal provides a nice balance for my type of blogging. I’ve got some julia NLP blogs in the works and so far I love the workflow.

---

<div class="post-metadata">

**Author:** ![cscherrer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/cscherrer/32/7631_2.png) [@cscherrer](https://discourse.julialang.org/u/cscherrer)\
**Post date:** [August 22, 2019, 3:16am UTC](https://discourse.julialang.org/t/julia-1-2-in-nextjournal/27801/3 "2019-08-22T03:16:17Z")

</div>

> [@sdanisch](#):
>
> We’re also trying to get more adoption in the teaching & tutorial space, so if you would like to use Nextjournal for that let us know!

Hi Simon, I do a lot of teaching and I’ll need something for Soss.jl tutorials once I get past this initial fast-changing API. I’m currently using Hugo, but it looks like Nextjournal can be a bit help with this. Looking forward to checking it out!

---

<div class="post-metadata">

**Author:** ![carstenbauer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/carstenbauer/32/4981_2.png) [@carstenbauer](https://discourse.julialang.org/u/carstenbauer)\
**Post date:** [August 22, 2019, 5:39am UTC](https://discourse.julialang.org/t/julia-1-2-in-nextjournal/27801/4 "2019-08-22T05:39:32Z")

</div>

Is it just me or is `@which` not available on nextjournal?

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [August 22, 2019, 7:51am UTC](https://discourse.julialang.org/t/julia-1-2-in-nextjournal/27801/5 "2019-08-22T07:51:55Z")

</div>

`@which` is defined in `interactiveUtils`, which, IIRC, isn’t loaded automatically on NextJournal.

---

<div class="post-metadata">

**Author:** ![XVilka](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xvilka/32/7155_2.png) [@XVilka](https://discourse.julialang.org/u/XVilka)\
**Post date:** [August 23, 2019, 2:58am UTC](https://discourse.julialang.org/t/julia-1-2-in-nextjournal/27801/6 "2019-08-23T02:58:17Z")

</div>

In general, I am for entirely open-source platforms, but a bit of healthy competition wouldn’t hurt.  
A few years ago, there was also an extensive discussion about possible improvements for the current publishing model and platforms. See several follow up posts too. All of them contain a lot of references and reader’s comments - it worth to read everything:

- [Beyond Papers - GitWikXiv](http://blog.jessriedel.com/2015/04/16/beyond-papers-gitwikxiv/)
- [Distinctions in Academic Tools](http://blog.jessriedel.com/2015/04/27/gitwikxiv-follow-up-distinctions-in-academic-tools/)
- [An Open Attribution Standard](http://blog.jessriedel.com/2015/05/09/gitwikxiv-follow-up-an-open-attribution-standard/)
- [A Path to Forkable Papers](http://blog.jessriedel.com/2015/05/20/gitwikxiv-follow-up-a-path-to-forkable-papers/)

While it is more relevant to scientific publishing as it is, I believe it has some ideas that can be useful to you. There are also quite mature and established [Authorea](https://authorea.com/) and [Overleaf](https://www.overleaf.com/) commercial platforms along with their main FOSS competitor - [PubPub](https://www.pubpub.org/) from MIT.

DARPA recently funded and promoted one more impressive idea - the social network for scientific exchange [Polyplexus](https://polyplexus.com/). Integration or feature parity with something like that might be interesting for you too.

---

<div class="post-metadata">

**Author:** ![lazarusA](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lazarusa/32/6571_2.png) [@lazarusA](https://discourse.julialang.org/u/lazarusA)\
**Post date:** [July 11, 2020, 7:26pm UTC](https://discourse.julialang.org/t/julia-1-2-in-nextjournal/27801/7 "2020-07-11T19:26:37Z")

</div>

Hello,  
I’m recently using Nextjournal, and was wondering how do I display images saved in `./results/`. I know that if I use python or Plots (julia), plotly, ggplot etc…, the figures are shown automatically, but, what if I saved them first, and then I want to show them? How do I achieve this?

---

<div class="post-metadata">

**Author:** ![sairus7](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sairus7/32/10816_2.png) [@sairus7](https://discourse.julialang.org/u/sairus7)\
**Post date:** [July 11, 2020, 9:38pm UTC](https://discourse.julialang.org/t/julia-1-2-in-nextjournal/27801/8 "2020-07-11T21:38:43Z")

</div>

> [@XVilka](#):
>
> DARPA recently funded and promoted one more impressive idea - the social network for scientific exchange [Polyplexus](https://polyplexus.com/). Integration or feature parity with something like that might be interesting for you too.

This is interesting! Looks like it launched a couple of years ago - how its going on now?

---

<div class="post-metadata">

**Author:** ![Wen-Wei\_Tseng](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/wen-wei_tseng/32/28839_2.png) [@Wen-Wei\_Tseng](https://discourse.julialang.org/u/Wen-Wei_Tseng)\
**Post date:** [July 12, 2020, 2:46am UTC](https://discourse.julialang.org/t/julia-1-2-in-nextjournal/27801/9 "2020-07-12T02:46:28Z")

</div>

Hi lazarusA, `display()` works fine. Checkout this [example](https://nextjournal.com/sosiristseng/show-image-in-results-folder).