Comments by "MrAbrazildo" (@MrAbrazildo) on "Bjarne Says C++ Is Under Attack" video.

  1. 1:06, 🙄...! This is tiresomely obsolete, as the tools almost banished those memory errors forever. "The problems of the industry are not there. And I watched a lot of port-mortems" - David Sankel, from Adobe, Bloomberg and others. I guess I'll have to code this as libraries, just to shut up these outsiders. Rust plays nice with newcomers. This is something we should learn from it.
    3
  2. 2:50, dump C++ for what? I want/need: - Nonpolymorphic inheritance, instead of composition; - Actual encapsulation, breakable only by a selected group of few f()s (meaning data is actually private, not indirectly public by allowing to use filters/modifiers, as C does) ; - Full freedom to interact over a container. This way I decide the level of use constrains, by coding my own; - Not to be forced to lose performance, because somebody else decided it for me - GC, for instance. In C++ I code things that I turn on/off security by clapping fingers. Does Rust has that? Can I turn its slow compile on/off anytime? - Lots of things able to work hiddenly on backstage (several anytime-optional checkings, for instance), so that I can dev. powerful tools.
    2
  3. ​@ But I'm talking about other languages, since their idea is to "dump C++".
    1
  4. 12:00, the standard is conservative: keeping a language with "all features" is already a lot of things. And since it aims to have backwards compatibility as much as possible, it's desirable to keep off things that seems to be "born to be external" tools. I guess this view of not breaking things along the way allowed the language to exist, with success, for so long time. 12:14, chat: its syntax is a war crime. I find it to be quite clever: it's productive, since you type 1 thing, and it's likely to be correct - the context will tell exactly what it is. ie: you don't type defaults, saving energy - what would be an error, it's allowed under a certain context. I don't know how many languages have 'var' and 'let', but this last 1 for constant is stupid: it should not exist (const as default). 12:36, it could be worse: forced to use identation. 19:19, you can only be joking. With a bit of effort, C++ jumps to a kind of high level language. 19:55, for instance, when 1 makes an algorithm traverse from [begin; end), the pointers are always trapped. I never got a memory seg fault using that! Ok, only 1 time I fell for the "invalid pointers", when the memory was reallocated. But never again! And it was an easy to catch bug.
    1
  5. 3:20, it's political, because the language is being condemned by things it almost got rid of. So he's saying that they should implement those safety measures as frameworks, instead of the already existing external tools. Because otherwise people go to Rust and alikes, and once other codebases grow with those languages, there won't be place for C++, outside its giant legacy codebases. It'll be the new COBOL! An undeserved destiny for the best language! 8:07, it looks contradictory: the language always was made unsafe (for performance) and always aimed safety, as a long term goal. It has a conservative way to see things: it wants to evolve, without sacrificing things on the way. I guess that vision is correct, for its ambitious goals. And having this in mind, the language has indeed evolved quite beautifully, in my opinion. 10:22, that's because he was wrong. People are too enthusiastic over Rust, at the point of misjudging C++. 11:31, Clang compiler launched a 'modernize' tool, that rewrites old working code to new standards.
    1