mighty interesting, i scanned the nuances about the memory model, but it doesn't explicitly say so, but am I right that some workloads will result in heavy fragmented physical memory allocations?

What are the down sides? That's the key question when a better thing comes along.

Lobster is the author's other programming language, previously discussed on HN: https://news.ycombinator.com/item?id=47239955

I'm curious, when returning a dynamically sized array from a function, does the whole array need to be copied? C++/Rust would simple move the array out of the function (i.e., they would only copy the pointer to the underlying data), but it seems this wouldn't work in Goose if the stack the dynamic array lives in is cleared on return?

Im not gonna judge it by anything other than name. Its awesome, Goose it up.

> Memory is a handful of data stacks that the compiler assigns statically

I doubt this can work well in all cases. Sooner or later one needs proper heap.

I hate when I see a new programming language, get my hopes up and it turns out to be AI slop again.

There might be some decent design ideas there but if you can't be arsed to write them down in your own words but instead make me read AI generated slop I am out.