Remix.run Logo
Retr0id 2 hours ago

I don't really "get" the sweet-spot being targeted here. You don't get channels, goroutines, or gc, so aside from syntax and spatial memory safety you're not really inheriting much from Go. There is also no pathway to integrate with existing Go libraries.

Spatial memory safety is nice but it's the temporal safety that worries me most, in nontrivial C codebases.

tidwall 2 hours ago | parent [-]

Looks to me like having the ability to write Go syntax and interop directly with C is the plus.

Retr0id 2 hours ago | parent | next [-]

I do like Go's syntax but I can't help thinking the best language for C interop is C.

AdieuToLogic 2 hours ago | parent [-]

> I do like Go's syntax but I can't help thinking the best language for C interop is C.

SWIG[0] is a viable option for incorporating C code as well.

0 - https://swig.org/Doc4.4/Go.html#Go

stevekemp an hour ago | parent [-]

I love how SWIG is still around! I first used it about 30 years ago to integrate with Perl, then later with Java.

whateveracct 19 minutes ago | parent | prev [-]

Go's syntax is basically C tho lol

what's the benefit? for loops?