News for hackers. Stuff that matters.
Re:Brad Fitzpatrick on the future of Go by pjmlp on Tuesday October 14, 2014 @03:07PM (#8455121)
Well, at least it can replace 90% of the use cases one would use C for.

I am leaving those 10% for kernel code and portable macro assembler tricks.

Even with my position regarding generics in Go, I have to agree interface {} is way better than void* or macro tricks.

EDIT: Should mention that those 10% also include embedded deployments where ANSI C barely fits.

Re:Brad Fitzpatrick on the future of Go by 23david on Tuesday October 14, 2014 @05:07PM (#8455824)
From what I've seen lately, Golang programs take up too much disk space to replace small C utilities that are used in lightweight or resource-constrained environments. Memory usage also tends to be much higher, but that may be less of an issue since it can be optimized through careful profiling. I haven't seen any way to really optimize disk usage yet...

I hope I'm wrong though. It'd be exciting to see Golang equivalents of optimized C utilities that come close to using the same disk and memory. Or maybe there's an embedded golang compiler in development that does a good job of optimizing for these use cases...?

Re:Brad Fitzpatrick on the future of Go by Blackthorn on Wednesday October 15, 2014 @12:52AM (#8457223)
I don't see how that's all surprising. I'd be surprised if a Go program without the explicit goal of being tiny managed to compete on disk size and similar metrics with something like Busybox, which has the explicit goal of being tiny.