Linus Torvalds on C++ (2007)
thread.gmane.org
Linus Torvalds on C++ (2007)
1–10 of 33 posts
Re: Linus Torvalds on C++ (2007)
#2Re: Linus Torvalds on C++ (2007)
#3This was seemingly discussed on HN 7.5+ years ago: https://news.ycombinator.com/item?id=51451
Meanwhile, I believe the submission guideline is to include the year (2007).
Re: Linus Torvalds on C++ (2007)
#4http://thread.gmane.org/gmane.comp.version-control.git/57643...
> Unfortunately, I haven't had any time inte the last few days to code, nor read mail. I'm assuming that there is no point in me finishing the patch and that git will go with the strbuf solution? /Lukas
... with no response.
Re: Linus Torvalds on C++ (2007)
#5Re: Linus Torvalds on C++ (2007)
#6The opposite can also be said. By re-inventing a simple data structure, you can end up 2 years later in the same position where your structure is inefficient (list vs. array, etc) and you end up having to rewrite your app. While implicit operator overload was probably a C++ mistake, it does allow to replace some kind of structures with other one without changing the code relying on them.
Other than that, I kind of agree that C++ is kind of terrible. So is perl, php, js or any other languages that send a barrage of features to the programmer without managing to educate them on their impact on performance and memory structure. Most C++ devs know about vTables and that's about it. I would also argue that C isn't a very good language either. It may be simpler to "get" what actually happen when you run your code, but has sub par code organization, total lack of "pointer flow" tracking, causing huge security traps and has an evil reliance on casting for any kind of structure/callback abstraction. All of those things could be "fixed" in new languages, but beside Rust, it seem there is no leverage for proper system level languages these days. OOP is probably a better choice for business programming anyway, but that's not even half of the market.
Re: Linus Torvalds on C++ (2007)
#7It's only this time around that I've read the sad conclusion to this thread, from the original contributor http://thread.gmane.org/gmane.comp.version-control.git/57643... > Unfortunately, I haven't had any time inte the last few days to code, nor read mail. I'm assuming that there is no point in me finishing the patch and that git will go with the strbuf solution? /Lukas ... with no response.
Re: Linus Torvalds on C++ (2007)
#8Re: Linus Torvalds on C++ (2007)
#9However, C in all its simplicity already has its potential for abuse. Macros can go very bad. Very bad. (Just look at openSSL).
It is also not difficult to abuse the left-right rule in pointer arithmetic: *x->a->c=5. It can easily become incomprehensible.
We did not need C++. We needed a way to further simplify C.
Re: Linus Torvalds on C++ (2007)
#10It's only this time around that I've read the sad conclusion to this thread, from the original contributor http://thread.gmane.org/gmane.comp.version-control.git/57643... > Unfortunately, I haven't had any time inte the last few days to code, nor read mail. I'm assuming that there is no point in me finishing the patch and that git will go with the strbuf solution? /Lukas ... with no response.
Typical Linus. Pretty much an opinionated ass, with very (very very) few of the positive connotations that come with being opinionated.
Yeah, only "getting shit done" and "getting Linux and Git" happen, which is pretty much all he attempted to do.