2
Shane first post
C++ Memory Safety Guide: Don’t write code that violates memory safety. Added initial video to check
Added test video:
"A language does not support a technique if it takes exceptional effort or skill to write such programs; it merely enables the technique to be used." - Creator of C++ 25 years ago
2
Okkkkk
To be fair, C++ did make it easier to manage memory compared to C without paying GC cost.
It’s just that programming research has progressed a lot beyond in the 90’s.
The frustrating thing with the C++ committee now is that they refuse to pick a lane. They refuse to break ABI to make important performance optimizations. They refuse to break API to compete with Rust more directly. So it’s a slow and unsafe language, fine, maybe it’s just for legacy development? Except they pile on a hundred new features every release, except for a package manager (which is table stakes for new project).
It’s like they can’t decide if they are a legacy project focused on stability, versus an active language that wants to compete head-to-head on performance, safety, and ergonomics.
So they do the classic C++ committee thing where they split the difference a hundred ways and end up with a nonsensical blob.
1
test reply with image
0
another image. edit check
0
3rd reply check
0
added another check here @codalata
0
Test comment @jasz again
0
another @jasz comment
Login to leave a comment.
Comments (7)