News for hackers. Stuff that matters.

A comment on Ask HN: What is the state of C++ vs. Rust?. Parent comment

Re:Ask HN: What is the state of C++ vs. Rust? by agentgt on Wednesday October 19, 2016 @12:05PM (#12745019)
There are libraries (I didn't downvote you but I suppose that is why as simple googling shows that) [1].

That being said one would argue if you are going the microservices route you shouldn't need an exceptional amount of routing anyway. You only need to really handle raw HTTP for the most part (also I would not say HTTP is the end all for microservices... I have been using a Rust AMQP library with some success [2]).

Also although Go has green threads it is still debatable if that is the right way or golden way particularly when so many backends like databases (e.g. postgres) can't handle async (tons of connections) anyway. Old school one thread per request libraries in Java like dropwizard can still do fairly well. I think Rust made the right choice with native threads and hopefully some interesting green thread or reactive libraries will come forth soon (or already here ... haven't googled it).

Also I'm just not sure I really buy into Go's channels but that is just a personal opinion at the moment.

[1]: https://youtu.be/pTQxHIzGqFI?t=964A

[2]: https://github.com/Antti/rust-amqp

[ Parent | on HN ]
Re:Ask HN: What is the state of C++ vs. Rust? by ngrilly on Wednesday October 19, 2016 @05:59PM (#12748078)
When you need to handle a lot of concurrent connections (from your clients, not to your database), Go green threads are invaluable (better than OS threads because a goroutine requires only 2 KB; and better than callbacks). They are also very useful to express concurrent algorithms.
[ Parent | on HN ]