The goose language has dynamic allocation via builtin types, like most systems for the past 40 years (Folks were using dynamic allocation on systems back when 640k was a lot of memory). Most embedded systems these days far exceed the capabilities of 40 year old desk top computers and also use extensive dynamic allocation.

The distinction for goose is that it has fixed locations where the free must occur (function return, effectively), not that it doesn't have dynamic allocation (because it does have dynamic allocation)

Yeah embedded means a lot of things.

People working on cortex m series chips still static alloc though. :D

Them and game programmers. Also the HFT people from my understanding.

The latter two are due to latency concerns.

Still though, it is something that I think more engineers should try out once or twice. Thinking about how buffers actually need to be is a useful exercise.