> I also don't really see an advantage of using something like this over something like the Go net/http package.
C runs "everywhere". Your old C64 from the 80's? Has C compilers.
Go does not, even with gccgo.
I'd bet there are also still likely at least two orders of magnitude more programmers that know C well, and still more programmers with in depth experience of embedded development in C than have even tried Go.
I've still yet to meet anyone outside of the startup devops bubble that have written any Go, and often what language the developers have experience with matters more.
Yeah, but the idea to use them back then was like trying to use Ruby for real time applications in modern days, given how shitty they were.
Home computers might have had implementations of C and Pascal dialects, but we all used Assembly when stepping out of the built-in Basic and Forth enviroments.
C runs "everywhere". Your old C64 from the 80's? Has C compilers.
Go does not, even with gccgo.
I'd bet there are also still likely at least two orders of magnitude more programmers that know C well, and still more programmers with in depth experience of embedded development in C than have even tried Go.
I've still yet to meet anyone outside of the startup devops bubble that have written any Go, and often what language the developers have experience with matters more.