15 ms·

equivalents to all those tools (and more) are available in the C ecosystem.... just saying.... BTW: C is a much more mature ecosystem than that of Go.

_ph_ 10y ago
No one doubts that there is a rich ecosystem available for C. The thing just is, when you are working in a Go environment, what benefit would adding C with its own toolchain bring?
- coldtea 10y ago
  No need for bootstrapping step, 90% of portability taken care off for free, ability to use lower level and faster primitives than Go offers, access to tons of great C libraries.
  - ngrilly 10y ago
    > ability to use lower level and faster primitives than Go offers Like what? Go's unsafe code is free from doing almost anything (except things like array bound checks that are always enforced).
  - koffiezet 10y ago
    > 90% of portability taken care off for free You sir, have clearly never attempted to write portable C or Go code. Writing portable C code takes a serious effort. It's not hard if you know what you have to pay attention to - but 90% portability taken care of for free? That's simply not true, unless you think being portable is "it runs on a POSIX system". Writing portable Go code - in most cases - you don't need to do anything or make only slight changes to your code, and cross-compiling is the easiest I've ever encountered.
deleted 10y ago
[deleted]
drivebyops 10y ago
Not the build system, a pain to get the libraries in Windows for a Multiplatform project that I wanna compile. Where in Go this is very easy
PopsiclePete 10y ago
C has an eco-system? Really? Yeah, sure I can download source code and headers and somehow use 12 different antiquated tools that strung together with duck tape and bubble gum that are also not standard on Windows let's say, to actually hopefully compile that code, and then worry about 12 other different tools each with 6 different options to be able to do something simple like "link a library", and hope that works on FreeBSD and OS X and Windows, but it won't, it never does, without spending an insane amount of time tweaking headers and m4 macros, before giving up and learning CMake, but if that's what you consider a "mature eco-system", then you have very low standards.

_ph_ 10y ago

No one doubts that there is a rich ecosystem available for C. The thing just is, when you are working in a Go environment, what benefit would adding C with its own toolchain bring?

coldtea 10y ago
No need for bootstrapping step, 90% of portability taken care off for free, ability to use lower level and faster primitives than Go offers, access to tons of great C libraries.
- ngrilly 10y ago
  > ability to use lower level and faster primitives than Go offers Like what? Go's unsafe code is free from doing almost anything (except things like array bound checks that are always enforced).
- koffiezet 10y ago
  > 90% of portability taken care off for free You sir, have clearly never attempted to write portable C or Go code. Writing portable C code takes a serious effort. It's not hard if you know what you have to pay attention to - but 90% portability taken care of for free? That's simply not true, unless you think being portable is "it runs on a POSIX system". Writing portable Go code - in most cases - you don't need to do anything or make only slight changes to your code, and cross-compiling is the easiest I've ever encountered.

deleted 10y ago

[deleted]

drivebyops 10y ago

Not the build system, a pain to get the libraries in Windows for a Multiplatform project that I wanna compile. Where in Go this is very easy

PopsiclePete 10y ago

C has an eco-system? Really? Yeah, sure I can download source code and headers and somehow use 12 different antiquated tools that strung together with duck tape and bubble gum that are also not standard on Windows let's say, to actually hopefully compile that code, and then worry about 12 other different tools each with 6 different options to be able to do something simple like "link a library", and hope that works on FreeBSD and OS X and Windows, but it won't, it never does, without spending an insane amount of time tweaking headers and m4 macros, before giving up and learning CMake, but if that's what you consider a "mature eco-system", then you have very low standards.