Goose programming language

“Within the first couple of paragraphs and bullets it made a completely false claim”

“Goose checks off a lot of my dream language syntax features.”

“Because you really can't do all the static checking and convenience like that with a library.”

“Goose isn't doing anything special there. What it is doing is doing the same with better safety guarantees”

“Goose proves it to be safe at compile time, with simple readable code.”

“How can you claim Goose is faster than C++, i.e. faster than the language whose subset (i.e. C) it compiles to?”

“It has great support for higher order functions and other functional patterns”

“The main page was such obvious AI slop that I didn't bother looking further”

“From 17MB ram usage to 6MB ram usage.”

“And these strings in Goose are 6 bytes, while the ones in C++ are apparently 16 to 24 bytes each.”

“It's less being slop and more being technical bomb drop”

“That's just not true especially when the author designed the language with the LLM like he says in the end”

“All is in pretty good taste, and I like what I've seen so far.”

“I had a really strong design in mind that I think should exist.”

“Almost every word on the front page readme is a features and benefits sales pitch.”

“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”

“I've having a blast writing Goose code by hand in my spare time”

“Negatives of the language as a brief point 18 on the tutorial makes the negatives look hidden.”

“The documentation is clear about what the language does. You can download it and test it out if you like”

“The docs are perfectly legible and to the point.”

“I would throw the entire docs out and write it from scratch in your own words”

“Goose has no "unsafe" feature, and no undefined behavior, and is fully memory safe.”

“The concepts seem interesting but it's painful to wade through stuff like”

“The idea is that you don’t need to make representable all programs: a language for a restricted purpose is ok.”

“Isn’t this just re-inventing the index arena pattern, which nullifies much of the benefit over rust?”

“It is much more reference safe since you are only ever freeing stuff in a certain context”

“This doesn't seem like something you could easily represent.”

“Most of my current Goose projects are games, not surprisingly”

“Not optimized for reallocation. Creates pressure to overload types, making secure software unattainable.”

“These AI generated docs would make more sense if you instruct it to not include numbers unless they form a complete example.”

“It makes for big space savings vs these languages.”

“This is really nice because allocating memory is just adding to the pointer”

“cover pages need some better TL;DR, about the purpose.”

“The relative references and built in binary structure validation also enable direct memory mapping of data structures”

“Safer, faster and less memory than Rust/C++ for algorithms where tightly packed, flat data structures matter.”

“I can at least see the value proposition clearly-enough that it seems really cool.”

“You need a test suite comprised of a wide variety of real world programs, not 16 microbenchmarks”

“an expert language designer using a tool to explore an idea they otherwise wouldn't have time for”

“it was implemented by LLM instead of explored by someone with curiosity”

“the benchmarks are tiny, and it’s likely that Goose was tuned on them.”