Working on the game Voxile. Prev. Wasm / FlatBuffers / games&VR at Google. Made TreeSheets, PLs (Goose, Lobster, False, Amiga E) and game engines (Cube..).
San Francisco, CA
Joined February 2009
- Tweets1.1K
- Following267
- Followers5K
- Likes2.9K
The "rewrite it in Goose" movement is already gaining steam, see here some early results of rewriting expertly written ninja/json/yaml/jq parsing in Goose and getting large speedups: github.com/calpeyser/goose-e…
Or these carefully curated independent benchmark where Goose gets *higher* speedups over C++/Rust than my own internal benchmarks (final numbers still out, but likely close to 1.6x on average): github.com/kostya/LangArena/…
That benchmark is now out: xitter.cf/wvo/status/21127086427…
The first independent benchmark featuring Goose is out, making it 42% faster than the next fastest languages (C and Rust) across 50 real world inspired tasks: kostya.github.io/LangArena/#…
The first independent benchmark featuring Goose is out, making it 42% faster than the next fastest languages (C and Rust) across 50 real world inspired tasks: kostya.github.io/LangArena/#…
For comparison, here are my own benchmarks where the distance with "expertly written" C++ and Rust is smaller, because I allow them to use very non-idiomatic code: aardappel.github.io/goose/be…
And this is early days for Goose. We're still adding features that allow further "safe speed", like the "typed indices" from a few days ago that move critical bounds checks from where indices are used to where indices are created.
Come help us out, Goose Discord: discord.gg/397eZdbnsR or Github: github.com/aardappel/goose
If anyone wants to chat about my new Goose programming language, the #goose channel in the Lobster discord is for now the place to be! discord.gg/szJPYdX
Ok, seemed people preferred a dedicated Goose Discord after all: discord.gg/397eZdbnsR
Threads that share nothing. A worker is compiled as a separate program with its own memory.
Flat values sent in typed queues as a memcpy (since Goose values are contiguous). No data races, locks or atomics.
13/
Note: these numbers are already slightly out of date, numbers that include the latest optimizations are here: github.com/aardappel/goose/b…
And for those that have complained that my benchmarks may be biased, here is Goose in some independent benchmark, where it runs at **almost twice** the speed of C++/Rust, much greater than my own benchmarks: github.com/kostya/LangArena/…
Wouter van Oortmerssen retweeted
Been experimenting with Goose and built a modern UI, a small editor/Git workbench, and HTTP(S) support.
Still early, but it’s been fun building some practical things with it!
Goose: my latest programming language. Safer, faster and less memory than Rust/C++ for algorithms where tightly packed, flat data structures matter.
It can represent more kinds of data structures as flat, pointer-free bytes than any language I know.
github.com/aardappel/goose
1/
Wouter van Oortmerssen retweeted
Goose (xitter.cf/wvo/status/21079796605…) beats Milo on all five of its benchmarks on the largest inputs (1% to 34% faster) and uses less memory on three, up to 3.9x less. Impressive work @wvo.
Milo: fast like Rust, simple like TypeScript. A memory-safe systems language on a new point of the tradeoff curve: no GC, no lifetimes, one owner per value.
Also: SMT-proved contracts, reverse debugging, packages, 86 std modules, checked FFI, LSP.
github.com/milo-language/mil…
What it costs you: you think about who owns data and how long its scope lasts. Recursive functions cannot keep growable data across a recursive call. Arrays of variable-size elements iterate but do not index. No escaping closures or function pointers. Whole-program only.
16/
I designed Goose years ago but never had time to finish it. Claude Fable implemented it almost entirely from that design, and the back and forth made it a better language.
Today: a 30k line compiler, spec, stdlib, 29 samples, CI on 3 OSes. Start here: github.com/aardappel/goose/b…
17/
