From f91f4353976c83360a57e6eeacfad8e202896de9 Mon Sep 17 00:00:00 2001 From: Dmitry Savin Date: Sun, 31 Oct 2021 19:48:19 +0300 Subject: [PATCH] Fix typos caught by LibreOffice --- English/Mythbusters.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/English/Mythbusters.md b/English/Mythbusters.md index e6d3a77..85f8ab1 100644 --- a/English/Mythbusters.md +++ b/English/Mythbusters.md @@ -4,13 +4,13 @@ C++'s not dead. -C++ made its way to the top of a wide range of rating of programming languages, and it is even scoring more points, for example in the [Tiobe](https://www.tiobe.com/tiobe-index/) index. C++ got its notorious "dead language" badge during the noughties, while it was dormant and the languge standardisation committee fell off the radar. But the language is experiencing a renaissance since the C++11 standard. It is arduously getting new features and functionality, every three years. Many problems claimed by the "dead C++ witnesses" have been solved, but since such specialists have stopped developing using C++ - or got a smattering of C++ during courses (from those "witnesses") - they continue repeating and reiterating the myths and legends of the horrors of C++. +C++ made its way to the top of a wide range of rating of programming languages, and it is even scoring more points, for example in the [Tiobe](https://www.tiobe.com/tiobe-index/) index. C++ got its notorious "dead language" badge during the noughties, while it was dormant and the language standardization committee fell off the radar. But the language is experiencing a renaissance since the C++11 standard. It is arduously getting new features and functionality, every three years. Many problems claimed by the "dead C++ witnesses" have been solved, but since such specialists have stopped developing using C++ - or got a smattering of C++ during courses (from those "witnesses") - they continue repeating and reiterating the myths and legends of the horrors of C++. ## Reals programmers learn C++ using Linux/Vim/gcc -If you are unfamiliar with the aforementioned combo, we recommend you concentrate on learing the basics of C++ alone. We also suggest you start developing your first applications using Microsoft Visual Studio IDE (see [PreJunior Books](Books/PreJunior.md) for the details). +If you are unfamiliar with the aforementioned combo, we recommend you concentrate on learning the basics of C++ alone. We also suggest you start developing your first applications using Microsoft Visual Studio IDE (see [PreJunior Books](Books/PreJunior.md) for the details). -Choosing the hard way looks cool, but there is a high chance that the volume of the information needed to build the "Hello World" using Linux + Vim + gcc woukd be overwhelming. It is frauhgt with an early frustration and disaffection with programming. Try to follow the path from simple to complicated. Novices don't try to lift the heaviest weights during the first workout because they know what it might lead to. The same rule applies to education. You can try developing under Linux once you are comfortable with the language. But it's a different story altogether... +Choosing the hard way looks cool, but there is a high chance that the volume of the information needed to build the "Hello World" using Linux + Vim + gcc would be overwhelming. It is fraught with an early frustration and disaffection with programming. Try to follow the path from simple to complicated. Novices don't try to lift the heaviest weights during the first workout because they know what it might lead to. The same rule applies to education. You can try developing under Linux once you are comfortable with the language. But it's a different story altogether... ## You'd better master C/Assembler/etc before learning C++ @@ -22,7 +22,7 @@ This statement continues to live due to two widespread scenarios: it's how they A highly damaging thesis taking origin from the "Old Guard" or someone born with a keyboard in hand. -Those who had extensive experience of development in other languages (C, Fortran, Delphi, etc.) and transitioned to C++ are most likely to give this piece of advice. Stroustrup wrote this book like a reference, threfore one needs to use it in the appropriate manner, which requires some knowledge of the language. Better look at the [Books](Books.md) section, you'll find books for any level of language proficiency. +Those who had extensive experience of development in other languages (C, Fortran, Delphi, etc.) and transitioned to C++ are most likely to give this piece of advice. Stroustrup wrote this book like a reference, therefore one needs to use it in the appropriate manner, which requires some knowledge of the language. Better look at the [Books](Books.md) section, you'll find books for any level of language proficiency. ## Learn C++ using the Standard only @@ -36,6 +36,6 @@ More likely no than yes. Modern C++ and the tooling emerged around the language allow to avoid the lion's share of the problems related to the undefined behavior. We can give a rather simple piece of advice: when hesitant what a particular construct does, read about it on [CppReference](https://en.cppreference.com), [StackOverflow](https://stackoverflow.com/) or other dedicated resources. If still in doubt after the reading, try rewriting the code in a simpler manner to avoid the undefined behavior. In simplicity there lies a great power. -## One needs to manage mamory manually, there is no garbage collection in the language +## One needs to manage memory manually, there is no garbage collection in the language -This is another urban legent from the Old Guard that had stopped writing C++ before C++11 or those who seperficially learned it in university disregarding the latest standards. Modern C++ contatains a set of primitives in its standard library responsible for the automatic memory allocation and deallocation. The memory management fell by the wauside. Many teams and companies even have the rule: "No raw pointers". Once again, do not neglect the modern tools and sanitizers. They can detect possible memory leaks at the source code lovel. +This is another urban legend from the Old Guard that had stopped writing C++ before C++11 or those who superficially learned it in university disregarding the latest standards. Modern C++ contains a set of primitives in its standard library responsible for the automatic memory allocation and deallocation. The memory management fell by the wayside. Many teams and companies even have the rule: "No raw pointers". Once again, do not neglect the modern tools and sanitizers. They can detect possible memory leaks at the source code level.