Hacker News Reader

Comment by dominotw | Hacker News Reader

i would say rust is the new kid on the block, go is old news.

Actually I'm a little more annoyed by the Rust and Elixir people. At least the Go stuff is "Hey I did something in Go". The Rust and Elixir stuff is almost always as a response to something someone did in Go, C, C++, Java or some other language, and almost always in the form of: "You might like Rust", "You should check out Elixir".

At least Go can generate it's own hype, and doesn't need to piggyback on others.

The main problem of rust is that it's not implemented in go. The reverse is also true.

Didn't see a lot of HN posts about "How one rewrote Y from Z to Rust" yet.

Plenty of Rust related posts, though.

My point is, Go posts easily appears on HN homepage, more than anything else. I didn't see a lot of posts about Java or Python there lately.

BTW, where's the guy who replies "What an amazing time to be alive!" to every go post? I'm worried.

Maybe the drugs wore off? :D

Redis reimplemented with Rust

https://news.ycombinator.com/item?id=9741625

Go 1.0 is 4 years old now, after 5 years working on developing what is essentially and was always "C with garbage collection and threading". Rust is a year old, after 6 years of research building something novel outside of academic languages, with the final shape of the language heavily changing in the last year. Rust also doesn't ship with an extensive standard library including nearly all the things you'd want to make a basic web app.

Basically - Go had a very strong focus on web servers from the start, making it easy to pick up and develop web servers with. Web developers make good early adopters - they'll pick up new tools faster than almost any other group of developers. Rust was released without any of those tools, and they're still changing as the ecosystem develops (especially around async frameworks). And even with that, there's a fair few companies using it for all sorts of cool things: https://www.rust-lang.org/en-US/friends.html

And Go is rather pointless to begin with. The only thing it get's right is the excellent microthreads and CSP implementation.

The only reason it gained any traction is the big name of the mothership...

It's ok to dislike the hype but it's disingenuous to say it only gets one thing right.

> The only thing it get's write is the excellent microthreads and CSP implementation.

No at all. It's very far from even remotely decent implementation, the interface is too inconsistent and full of implicit behaviors and the performance is an order of magnitude slower than anything acceptable. But anyone actually using it already knows..

I admit we dropped Go before getting to production, with any kind of performance requirements.

I liked the goroutine related apis though.

What I remember being PAINFULLY slow is reflection. Which is very inconvenient for certain tasks (building objects from db queries, (json) serializing,...). Macros could help here, but alas, code generation is the only alternative available. Which I'm not a fan of.

---

What's are your gripes with Gos CSP?

The reflection is slow indeed but most of the time you can use caching to improve it(at least that was my case). I like Go a lot but I must admit that some features would make my life easier and perhaps the language more expressive too(i.e. variant types). If that is not good enough you can use code generation(last resort)

What it gets right is that it's just a tool not a play field for academics.

I admit to having a personal gripe with Go.

I initially really liked it. But the languages designers just skipped over countless years of achievements in language design and implemented a C with garbage collection, with interfaces and a baked in CSP runtime.

If you read a bit in the groups / release notes, they were just too lazy to implement generics. Or it was too hard.

Go's ecosystem is really weak (for example, barely any library does proper versioning or any release procedure at all).

I think that is at least part due to the difficulty of writing clean, generic code. And the lack of proper packaging.

The lack of features is not a selling point, even if they try.

Easy distribution/static linking is what got me.

Reply on news.ycombinator.com