Skip to content

Docs: Julia cells run in the playground (v0.18.0) - #25

Merged
tannevaled merged 1 commit into
mainfrom
docs/julia-runs-in-page
Nov 15, 2026
Merged

tannevaled merged 1 commit into
mainfrom
docs/julia-runs-in-page

Conversation

@tannevaled

Copy link
Copy Markdown
Contributor

Playground v0.18.0 runs Julia cells in the page. The playground and Julia pages said they were check-only in the browser.

  • julia.md, "In the browser": Julia runs on go-embedded-julia v0.17.0 in a third core loaded on first use, about 28 MB (20 MB core, 7.8 MB image, gzipped) and about 20 s, shown on the cell; the limits (512 MiB, 20 million statements, 20 s, 16 MiB output); Julia is isolated from Go in the page; each run that executed Julia is followed by a new worker (go-embedded-julia/julia issues 92 and 93).
  • playground.md: the intro, the language menu paragraph (only C is check-only now), a new "Julia cells" section.
  • fortran.md: a Julia cell loads a third core, not the second.

Sizes, times and limits are what the playground's pull request measured and its README states. Refs go-notebook/playground#41

🤖 Generated with Claude Code

…ts, the isolation

content/en/julia.md "In the browser" and content/en/playground.md say what
playground v0.18.0 does: Julia runs in a third core loaded on first use (about
28 MB, about 20 s), bounded by 512 MiB, 20 million statements and 20 s, isolated
from Go in the page, with a new worker after each Julia run
(go-embedded-julia#92, #93). fortran.md names the third core.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@tannevaled
tannevaled merged commit 08dd03e into main Nov 15, 2026
3 checks passed
@tannevaled
tannevaled deleted the docs/julia-runs-in-page branch November 15, 2026 23:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant