Comments by "MrAbrazildo" (@MrAbrazildo) on "Golang is BAD for SMART PEOPLE" video.

  1. 7:12, this guy missed the point that companies wet dream is to hire juniors only. This is a goal, but hasn't been possible so far. It's predictable that some of them would eventually ask, for its top programmers, to develop a language/library to help noobs. 14:06, you should, because otherwise it's prone to erros: similar blocks of code put your guard down, while a bug is hidden between them. But there are some caveats for that: 1) Copy-paste is good practice, due to saving energy, which will be important on the long run. I even timed that once: it took me 20h to create 1 bug due to that, meanwhile I saved energy many times. 1 just needs to be a bit more careful when doing that, compared to normal code. And soon being ready to make the number 2: 2) A common code for all repeated block. Not with ifs between them, which leads to bad performance, due to branches. Just the actual common code should be extracted. 14:36, nice statement. Is it yours? I heard that for performance, but now that you said that, it seems more real for abstractions. 22:28, if a language lacks encapsulation, it's over to me.
    1