From dc70ffa63f26f1c61e1762d77f028cf34de577e8 Mon Sep 17 00:00:00 2001 From: tannevaled Date: Mon, 26 Oct 2026 13:49:53 +0100 Subject: [PATCH] Mention the planned julia cells on go-embedded-julia The hero text and the Ruby cells paragraph of Get started say that julia cells are planned on go-embedded-julia (a Julia interpreter in Go, in development at milestones M0 and M1), with links to its landing and to bib/julia.md in the roadmap. go-embedded-ruby has no organisation card here, so go-embedded-julia gets none either: the organisation count and the card check are unchanged. Co-Authored-By: Claude Opus 5.5 --- layouts/index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/layouts/index.html b/layouts/index.html index 10ea895..1092748 100644 --- a/layouts/index.html +++ b/layouts/index.html @@ -31,7 +31,7 @@

Science in Go,
{{/* The sheet's .accent paints with --grad, base to deep: on a dark page this logo's dark slate stops would vanish. --accent and --accent-deep are the same two in light and the bright stop in dark. */}}all the way down.

-

go-scikit is the umbrella over {{ len $orgs }} organisations that together cover what a Python notebook reaches for in NumPy, SciPy, pandas and matplotlib: arrays, FFTs, numerical methods, statistics, labelled tables, figures and notebooks, and, on the way to parity with MATLAB and Mathematica, sparse matrices, interpolation, signal processing and arbitrary precision. Pure Go, CGO=0, and each library measured against its reference, with the documents that say where it is slower or less accurate. A notebook's cells can be Go or Ruby, one cell reading what the other computed.

+

go-scikit is the umbrella over {{ len $orgs }} organisations that together cover what a Python notebook reaches for in NumPy, SciPy, pandas and matplotlib: arrays, FFTs, numerical methods, statistics, labelled tables, figures and notebooks, and, on the way to parity with MATLAB and Mathematica, sparse matrices, interpolation, signal processing and arbitrary precision. Pure Go, CGO=0, and each library measured against its reference, with the documents that say where it is slower or less accurate. A notebook's cells can be Go or Ruby, one cell reading what the other computed. julia cells are planned on go-embedded-julia (plan).

Write a first notebook → {{ partial "icons/book.html" . }}The organisations @@ -126,7 +126,7 @@

A first notebook, in four commands.

# notebook serve first.md the same, live in the browser, editable

Run it again and every cell is kept: a cell whose code and inputs did not change is not run again, across runs. The go-notebook documentation gives the cell rules; to try the arrays and the transforms without installing anything, the go-ndarray and go-fft playgrounds run them compiled to WebAssembly in the browser, and the go-notebook, go-statistics and go-numerics playgrounds run whole notebooks there, Go and Ruby cells alike: edit the cells, run them, see the figures.

-

A ruby cell runs on go-embedded-ruby, a Ruby written in Go, so the notebook stays one Go program with no Ruby to install. It sees the values the Go cells above it defined (here x, a Go []float64), and the Go cells below it see what it defines; the kernel orders and re-runs cells of both languages by what they use. From Ruby, the stack is reached through go-scikit/ruby, which the kernel adds by itself: Stats, Special, Optimize, Integrate, DataFrame and Plot call the same Go functions, with the same answers. The Ruby cells page gives the rules, and the -timeout and -memory limits that stop a runaway cell.

+

A ruby cell runs on go-embedded-ruby, a Ruby written in Go, so the notebook stays one Go program with no Ruby to install. It sees the values the Go cells above it defined (here x, a Go []float64), and the Go cells below it see what it defines; the kernel orders and re-runs cells of both languages by what they use. From Ruby, the stack is reached through go-scikit/ruby, which the kernel adds by itself: Stats, Special, Optimize, Integrate, DataFrame and Plot call the same Go functions, with the same answers. The Ruby cells page gives the rules, and the -timeout and -memory limits that stop a runaway cell. julia cells are planned on go-embedded-julia, a Julia interpreter in Go that is in development (milestones M0 and M1); the plan is bib/julia.md in the roadmap.