4 ms·
There's no much hope C++ to go away any time soon, so C++20 is fine, there are C++25, C++30 and C++48 for more features to add.
by snaky 9y ago
There's no much hope C++ to go away any time soon, so C++20 is fine, there are C++25, C++30 and C++48 for more features to add.
- pjmlp 9y agoAs polyglot dev, I am kind of ok with C++17 and beyond, as ANSI C++ groups at least care about improving the security story, not like ANSI C.
- snaky 9y agoI know it's unpopular, but I think security is overrated. No, I don't like the way it is, but really - do we know a company that gone bankrupt due the security breach? Do we know a single mobile app that lost it's major audience due the data exposure, or broken crypto implementation? Do we know any business that gone out of business due the security related reasons? I'm not saying we should not care, but I'm convinced we can't turn the table over by polishing the tools. The user's perception of security is a show stopper as for now.
- lomnakkus 9y ago> I'm not saying we should not care, but I'm convinced we can't turn the table over by polishing the tools. Why? We know for a fact that GC'ed langauges can e.g. prevent double-free for ever and ever. Obviously, this is modulo the language/runtime implementation, but if there are bugs there you fix them once and every single program out there gets the fix instantly. Similarly for many other types of 'dangerous' bugs.