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

  1. 0:00, interesting point you mentioned a startup. C++ is my favorite by far, but I don't know if I would trust it in the hands of a junior team. Maybe if there would be a long deadline ("done when it's done" mode) or if I would be watching close what they do (an almost "pair programming"). 1:19, I often use inheritance, and have no issues with that. I barely can imagine its absence. 1:40, optional type is comfortable to code and understand, but it has a concerning drawback: it carries within a potential branch, which may lead to slower code. Each f() doesn't know if it's valid or not, leading to too many IFs, ugly code, redundant work and prone to slowness. It works like a 9-months pregnant woman, making everyone apprehensive.
    3
  2. 6:38, to have this nil "fixed" at compile time, it must know at compilation all data values that interact with it. For instance, C/C++ nullptr is not necessarily known at compile time.
    1
  3. ​@llIlllIIlIIlllIlllIlI'm saying from the C++ PoV: if you send an optional<T> type, it'll be send, whether or not T is valid. Then a check for that will be needed. Rust's make some compile checkings, resulting in a different approach. About more checkings is meant if 1 keeps passing that type along f()s. For instance, if I use a pointer meant to not be NULL after true on initialization, I mentally know that I won't need to check it on other f()s. Plus, 1 can always make a NonNULLptr type. Both cases defeat the meaning for optional.
    1