Is this the Rust killer?>Goose>A memory-safe systems language with no heap allocator, garbage collector, or lifetime annotations. In this repository's benchmarks, Goose runs faster than C++ and Rust while using less memory.>Goose has syntax familiar to C and Rust programmers, but there is no heap. Every dynamic value lives inline on a data stack managed by the compiler. Growth advances a pointer, and memory is freed when its scope ends. The language's type and lifetime rules make this memory model safe to use.https://aardappel.github.io/goose/
>>110142164sussy logo
>no garbage collector>has a garbage collectorwhy do cniles keep reinventing garbage collection while pretending it's not that
>>110142164>fn longest(a: u8[:], b: u8[:]) -> u8[:] { if a.len >= b.len { a } else { b } }I've used and seen so many alt-langs, that a short syntax snippet is all i need to save time.
fn longest(a: u8[:], b: u8[:]) -> u8[:] { if a.len >= b.len { a } else { b } }
>>110142283Uh oh!
>>110142164No, it's not a systems programming language
>>110142204Java did military-grade FUD to Garbage Collection as a concept, and subsequently the collective mind of programmers, who think the technology just stopped progressing after the 90s.They ultimately yearn for the Garbage Collector, but need the charade of having to implement their own ad-hoc version, to feel "in control".
>>110142164>>Goose has syntax familiar to [...] RustHow the fuck is this supposed to be a selling point?
System code has data survive beyond the original scope all day every day.Copy at the drop of a hat makes life easier, that's why Swift did it. Then they dropped it for embedded swift.
>systems language Demonstrate how you would write a byte to memory address 0x000B8000 in Goose.
>>110142164>There is no shared mutable memory.DOA for real programming
>>110142543Makes it easier to transition.
>>110142164it's a vibe meme from a person who doesn't even know what a heap is.the fact that you didn't up on that says it all.no serious post-rust language has showed up yet, only WIP one man experiments, which is unfortunate, because such a language, or languages, would be interesting.
>>110144786 (me)*didn't pick up on that
>>110144786>no serious post-rust language has showed up yetWhat more could you even do in systems programming. All people wanted was just a better designed, modern C++, but Rust just did all of that and so much more. All the Rust criticism boils down to superficial things like syntax or being "too difficult". There is nothing to improve outside of personal preferences and small irrelevant things. Systems programming is going to be a solved problems for a very long time.
>>110142164> syntax familiar to C and Rust programmersThat's like saying> taste familiar from italian and english food
>>110144786Look up who the author is, what he have studied and what experience he has in programming languages.
>>110143429Rust users have already transitioned though
> Rust killer> Rust-like syntaxKYS goose-troon
>>110145623he doesn't know what a heap is (possibly confusing it with the specific C interface to it), and this is clear to anyone with low-level knowledge going through the README.no amount of appeal to supposed authority can change that factual reality.
>>110142164>fnNo.
>>110145657Heh.
>goose>not promoting tranny horseshitThe world would be a better place.
>>110142164
>>110144786/threadShow me any genuine improvement on RustGrouped borrows from Vale are sort of interesting but I suspect they are not fully sound
