4 ms·
> 16k lines of obscure C, riddled with pointer magic and arcane memory manipulations? No thanks Given the popularity of the library I'd imagine it's quite well
by sp1rit 3y ago
> 16k lines of obscure C, riddled with pointer magic and arcane memory manipulations? No thanks
Given the popularity of the library I'd imagine it's quite well tested. I also fail to understand why he attempts to port libshine from C to Go when he could just port the header files from LAME as FFI bindings instead. That should also ensure comparability with windows, as I'm sure such a library us also buildable on windows, given that ffmpeg uses it and ffmpeg works on windows.
- miki123211 3y agoGo programmers usually avoid C bindings if at all possible. Pure Go can be cross-compiled easily, but that goes out the window once you include C code. You can make it a bit easier by using Zig as your c compiler, but it's still a bit of a pain. If you want to expose your code as a Go package, the situation gets even more complicated.