Go best practices, six years in

Re:Go best practices, six years in by takeda on Sunday May 01, 2016 @08:46PM (#11608582)

Rust really aims to be replacement for C. It allows you to program in low level, but you have much more powerful type checking and keeps track of ownership which reduces number of errors that plagued C language.

Yes go also claims to be C replacement, but probably the only similarity is its simplicity, but unlike C it is not as expressive.

[ Parent | on HN ]

Re:Go best practices, six years in by BuckRogers on Sunday May 01, 2016 @09:47PM (#11608758)

I haven't used Rust extensively, more Go for sure. But it seems to me that Go was aiming for simplicity more than being a true innovation. It's basically a compiled Python with type annotations and unfortunately a GC to spoil it all.

Rust was aiming at innovating and advancing the PL space with meaning. I can't say looking back the time I invested with Go was well-spent.

Rust is probably worth the effort if you have the need for what it offers. It just requires more out of you than Go does.

[ Parent | on HN ]