30
you are viewing a single comment's thread
view the rest of the comments
[-] witx@lemmy.sdf.org 9 points 2 years ago* (last edited 2 years ago)

I have worked with fairly large c++ codebases: It's totally possible to write much safer code than it ever was and I actually enjoy modern c++. Still it's still a burden and mishaps can and will happen. The time for the c++ committee to show they can overcome the language's issues has passed IMHO there are much better, and more expressive, alternatives.

I don't believe in the whole model of releasing a standard every 3 years and then taking who knows how long to implement it, and not braking compatibility. that shit just hinders the language. With all this said I don't think c++ is going to die any time soon.

[-] lysdexic@programming.dev 2 points 2 years ago

The time for the c++ committee to show they can overcome the language’s issues has passed IMHO there are much better, and more expressive, alternatives.

I'm not sure if this is a good take.

Languages deemed "safe" boil down to two features: supporting specific memory management strategies, and adding static code analysis checks that enforce rules and best practices.

Can't this be done already without involving committees?

[-] technom@programming.dev 3 points 2 years ago

That works only if memory safety is optional. Additions of the language features needed for mandatory memory safety are backwards incompatible.

this post was submitted on 21 Mar 2024
30 points (96.9% liked)

C++

2353 readers
7 users here now

The center for all discussion and news regarding C++.

Rules

founded 3 years ago
MODERATORS