Re:Proposal: Go 2 transition
by steveklabnik on Friday October 26, 2018 @04:59PM
(#18312665)
They’ve moved away from “systems” as a moniker, and Rust slowly is too.
It’s just too confusing of a term these days, and nobody knows what it actually means, so it’s not useful.
I would say if one can write OSes, device drivers, debuggers, compilers, target bare metal deployments on language X, then it is a systems language, regardless of what label people put on it.
The problem with that is it's a narrowing of the 'historical' use of the term and just confuses things further. The Go (and now Rust, it seems) people are right to move away from it.
Even when Go started and used the term I don't think this is what they meant by it.
Well given its use in Fucshia TCP/IP stack, file system management tooling, Android GPU debugger, not everyone at Google thinks like that.
Likewise those universities doing OS research in Go, submitting their findings to USENIX.
Sure the upfront investment in Rust higher, Go is almost too small, but the upfront cost of Rust is amortized via the hours you save with all the abstractions and performance you get right out of the box.