Comments by "Vitaly L" (@vitalyl1327) on "Why Go Or Rust On New Projects" video.

  1. I always use the most suitable tool for the problem I'm solving. Yet, I cannot think of a single problem that I may ever face that would have warranted using Go. Of course I'm very biased - I don't have many use cases for languages with a GC, as most of the things I do are real-time. I can think of a couple of cases where I'd use Rust instead of C++ though, so for me Rust beats Go. Another issue I have with Go is that it's a very low level language, much lower level than Rust and C++. Why? Because Rust have proper AST macros. C++ have Turing-complete templates. Go got nothing. Not a single tool for building higher levels of abstraction. And any meta-language (even tiniest of Forths) is infinitely more powerful than any fixed language.
    4
  2.  @josevargas686  indeed, languages with built-in eval at least allow runtime metaprogramming. There are even some hygienic macro implementations for JS.
    1
  3.  @vikramkrishnan6414  this is what lazy developers want to believe. In reality, GC is a source of countless problems.
    1
  4.  @otaxhu  it is not. There is no such a thing as a perfect GC, and GC in Go is pretty awful even by the industry standards. 10ms latency - that's ridiculous.
    1