Comments by "" (@diadetediotedio6918) on "Rust is Not C" video.

6:05 Now look at the C macros for complex codebases and see the "predictability"
18
3:12 I don't think that is a fair comparison at all. It is not like C++ has 38 years and Rust practically only 12-13, there's a fundamental difference in the workings and philosophy of all of these languages.
10
@ccgarciab [" A competent C team will probably attain memory safety by explicitly understanding ownership of data across call sites, and what constitutes safe usage of abstractions."] If this was true, then Rust would not be born in first place.
10
5:36 Also, I mean, a 50 years old language. This man really like to make bad points
9
4:13 Yeah, and also unsafe. If you do not update your C codebase this seems more of lazy than responsible or a "good thing", software changes, operating system changes, things break even outside your control and keeping updated at whatever you are developing is always a good thing.
8
@ccgarciab I don't know, what do you consider competence? I don't place an unrealistic burden on people, human beings make mistakes, and the more you know about the world and about things the more you will realize that mistakes are a good part of the cases in which even the most competent people make things. Even great geniuses make and have made mistakes throughout history, and if I don't consider myself a great genius that's already an excellent reason for me to lower myself as a flawed human being and accept that having help from my tools is better than not having it in almost every possible situation. The thing is, history doesn't seem to care about our definitions of competence, it seems that people make mistakes even when they're big and renowned, great programmers have already created vulnerabilities that cost thousands and even millions of dollars, and that doesn't look like it's going to change as long as we keep insisting on the same extremely abstract and distant notion of 'competence', at least that's what it seems to me.
6
4:44 Also, "more trouble than worth", is very relative, what is the borderline between someone who is just conservative about the things he like and someone who has really good takes on language development and design?
5
@michaelzomsuv3631 Explain further. I would like some examples in both languages as you seem to be very knowledgeable about Rust and C macros. It is also interesting the 'as long as you don't do crazy shit' because I found that doing crazy shit in C is very, very, very easy.
5
13:45 So, the reality every single time punches you in the face for your claims
2
10:00 Android disagree with that take also.
2