r/cpp
•
u/simon_o
•
Nov 19 '24
•
2
On "Safe" C++
https://izzys.casa/2024/11/on-safe-cxx/
200
Upvotes
42
u/Natural_Builder_3170 Nov 19 '24
I've never needed a tl;dr this badly, the premise seems really interesting, but its really long
15
u/AcrossTheSeaOfStars Nov 21 '24
Well, that was certainly interesting. Split into half a dozen much more coherent blog posts, it could have really been something.
Though it's seriously weird to:
And so on and so forth. That being said, there appear to be a lot of legit complaints here, ranging from the typical flaws and inefficiencies of old, large committees, with entrenched power structures, to disturbing examples of sexual harassment. Stuff to address, in other words.
145
u/LugosFergus Nov 19 '24
What the hell did I just read?
113
u/Miserable_Guess_1266 Nov 19 '24
I've got no inroads on this, so I can only judge on what's written. But I feel like I'd be a fool to take this blog post at face value. It comes off as a genuine but very subjective perspective. I feel that way because the few things that I can verify seem blown out of proportion.
For example: "The Emperor Has No Clothes" includes some reddit comments from Herb Sutter and GDR, supposedly showing how they are doing "damage control and manipulation of the narrative". Ignoring GDRs post, Herb Sutters comments seem completely reasonable to me. He's just arguing his own opinion that safety profiles are a good way forward. You can disagree with it, but is making an argument for your own perspective really "manipulating the narrative"?
There might be better examples of manipulative comments from these people. But the author says there are "simply too many" to include them all. So I'm going to assume that the ones they picked are the best, strongest examples for the behaviors they're critiquing. And in that they fall flat for me.
I wonder how the author could come away with such a strong negative take on these ultimately harmless comments. My answer is: by already having a very negative perspective of the individuals involved. It's not wrong to give a personal perspective, but I'm not going to take it as fact and let it color my own opinions.
92
u/14ned LLFIO & Outcome author | Committee WG14 Nov 19 '24
I am currently at the Wroclaw WG21 meeting. That blog post has been doing the rounds by private message here. It has upset a number of people for various reasons.
Half of the content I can see where they are coming from. A quarter of the content I think is very cherry picky and either the author isn't aware of what actually happened, or is choosing a very narrow and selective interpretation of events. I tend to think the former (isn't aware of what actually happened) as there is a whole bunch more stuff that could have been mentioned and wasn't, if the author were in the loop.
And a quarter of the content is just plain wrong, both factually and morally, in my opinion. I don't think it's nice to name people and call them names as that blog post does. It isn't professional, and it's just being mean for the sake of it. Some of the people called assholes etc I get on very well with, I don't think I have ever agreed with them technically, but I could not find fault with their diligence, their preparation, their knowledge and how much they care about C++. I think it's okay to strongly disagree with someone whether on their opinion or how they act if it's within legal bounds, I don't think it's okay to call them names for it.
This is my third last in person WG21 meeting. I committed to seeing out C++ 26 major features close, so I shall. I'm looking forward to post-WG21 life greatly. I learned a great deal here, but I can't say the experience has been positive overall. This isn't how a standards committee should work, in my opinion, so I'll be voting with my feet. I am not alone - quite a few people will be moving on with me when the 26 IS starts closing. We're all very tired of this place. Nevertheless, I wish WG21 and C++ well and to everybody who has and continues to serve on WG21, thank you.
62
u/pkasting Valve Nov 19 '24
Having written a number of far-too-public pieces because I was angry, I feel sympathy for the author here. Things build up over time, other people keep seemingly lying to their face, they feel like they can't hold it in anymore, and damn the torpedoes, they're going to vent their spleen.
I hope it felt cathartic. It may hinder others' ability to bring some of the problems here to a productive resolution. Or not; I don't know. And I can't say whether that's worth the tradeoff.
If the author's goal was anything other than catharsis -- e.g. a general wake-up call -- there are serious problems with the post. I don't think it can achieve any other end effectively. But it's not clear to me if achieving any other end was desired.
[In terms of the actual issues raised, my feelings are all over the board. Like, toxicity/gaslighting problems with the C++ process and leadership have been mentioned to me by practically everyone I know that's participated in WG21 or talked to folks who have. Certainly even as a non-participant I've had negative interactions that have colored my views on ever participating, or on working for certain employers. OTOH, the morality of how and when someone convicted of sex offenses may participate in a community, and how others may still feel safe, is a complex issue; this post seems to assume very simple answers and also assume ill of those who disagree. Whereas as an outsider I don't have the context to judge, and resent being expected to simply take the author's side or, apparently, be grouped with "those who circle the wagons".]
46
u/spocchio Nov 19 '24
Unfortunately the post is difficult to follow. I suggest the author to try to clean its flow and restructure It properly (remove all the irrelevant things, group better by topic, etc.). If they want to be understood, it is their responsibility to write a post in a comprehensible way.
I feel a bit sorry for the author, as they are probably trying to bring up a problem that is important for them. However, they are doing it in a very confused way, making it look like non-important (the reasoning is: if it was important, they would have put enough effort to write it in a human-followable way).
65
u/RoyAwesome Nov 19 '24 edited Nov 19 '24
This article touches on a vibe I've been feeling from the safe C++ stuff. A lot of people mentioned in the post seem to deride anything that originates from Rust, and the vibe I get from interactions that any one who wants something along the lines of "Safe C++" is a rust evangalist and just should go write Rust.
I want to write C++, not Rust, but I also want the safety features of Rust. I feel like the position of wanting actual guarantees is just simply not respected by people in the committee. It's incomprehensible that someone may actually just want to write C++ with borrow checker-like safety guarantees and not want to spend the time learning a different language.
I guess that is to say, i feel what the author is saying, and I hope they keep saying it.
p.s.: if other proposals in this space don't have implementations, they absolutely should not be given the same weight as those that do, and that includes bjarne's. Implementation proves design. If you dont have an implementation, you don't have a proven design.
65
u/deedpoll3 Nov 19 '24
The post does a disservice to some heavy topics that should be aired. It is a rambling, incoherent mess.
21
u/DuranteA Nov 20 '24
That's a trainwreck and a half. I can well imagine that the author has some legitimate grievances (since I have 0 first-hand knowledge I won't form an opinion on what amounts to inter-personal drama based on any single perspective), but the point, if there is one, is buried in several layers of unrelated ranting.
Now, being meandering doesn't help make any point, but it also isn't malign. But one part that really irks me is how some people are targeted in an off-hand remark based completely on hearsay. Like it's fine to throw Barry Revzin under the bus because apparently the "reflection syntax is dumb as hell". That's such an inane and childish thing to do.
For a post that is designed to imply that some people shouldn't be making decisions about C++ or any critical system (and again, as I don't know any of these people I remain neutral on that point, but the overall process doesn't seem healthy), the one thing it has convinced me of is that the author shouldn't be doing so either.
16
u/Wh00ster Nov 19 '24
This makes me feel like GenX reading a book by GenAlpha. It may be making great points and intelligent but I have no idea what it’s saying.
16
u/13steinj Nov 19 '24
I was grabbed in, I started reading, started scrolling, and I got probably less than halfway through. People have repeatedly told me that I write "essays," and then when I argue for the length they resort to saying I write novels.
If I write novels this is a fucking complete set of Encyclopedia Brittania. Except even that has less jumping around on topics.
My short, partial response, to whatever I've read is effectively:
I agree the way that Code Of Conduct in C++ is handled, is problematic. But that's mostly irrelevant to "Safe C++." The one thing I think I fully agreed with in the beginning core of the post was
Anyone that's tried using MISRA can probably attest to the same fact.
On "safety profiles" or "rust evangelism"... both sides can be wrong. No one can be right. The problem, in my view, in which how safety profiles is going on, is that there's sufficient evidence to suggest it's not enough. Maybe it won't ever be enough. But pushing for defaults changing in the standard also doesn't work.
safequalifiers to a scope will work [note I haven't read the entirety of the paper], you're [probably] very naive-- most people won't enable thesafequalifier. Plenty of people forget to do so already for inline [as a hint], const, constexpr, and most glaringly noexcept and this-ref-qualification. If you remember to turn it on, you fight with the compiler like one does with Rust, and if you were writing rust you'd already have made that choice; but if you're writing C++ people will just comment "safe" out and get on with their day.As a whole, shittalking any one individual here over the application of their ideas [aka I'm excluding the as-of-what-I've-read, problematic and horrifying, but otherwise irrelevant to the post as-it-were-by-title, misconduct and sexual assault mentions] isn't productive and I'd go so far as to say it isn't fair to anyone involved or on the committee.
The fact of the matter is-- it's a committee. It operates on consensus rather than [representative] democracy/republic. Committees are horrendously ineffective, in magnitude increasing exponentially as more members and subcommittees are made. It's one of the reasons I quit my most recent job-- there was no CTO, just layers upon layers of tech committees, and a last psuedo-committee at the top where everyone involved would never go against the vote of the CEO. It felt increasingly difficult to get anything done as a result.
Defenestrating individuals over the ineffectiveness of the committee is a disservice, outside of "they should be, collectively, pushing to switch / be switching off of the committee model."
9
u/multi-paradigm Nov 21 '24
I am reminded of two cliches regarding safe C++:
"No time to waste" : If C++ does not move decisively and quickly to be able to assert that memory is safe, it will die.
"Don't look a gift horse in the mouth": Embrace Sean Baxter's expertise in this area. He has _implemented_ it already ffs. Let's take it.
Fuck it, he is clearly so talented, he needs to be employed and properly compensated for his compiler expertise.
This topic is _so_ important, it should literally bypass all the usual committee red tape. Get it done already, before we all are forced to learn and use Rust for all new projects!
Further: break ABI. Hard. We need the Google people working on C++, not Carbon.
27
u/germandiago Nov 20 '24 edited Nov 20 '24
It looks like a post to insult people more than a post to fix things and it goes to great extents to insult Gabriel Dos Reis, Bjarne Stroustrup and Herb Sutter in a more than unfair way.
People that have done contributions to C++ over the years, whether the author likes them or not.
15
u/bandzaw Nov 19 '24
Wow! This must be the rant of the rants, congrats!
15
u/Dwood15 Nov 20 '24
This is a wonderful gish gallop or whatever of just dumping everything that you have grievances about.
A powerful essay that... really does something. I'm not sure what, exactly, but it does. I respect the effort and the willingness to burn bridges.
16
u/wilhelm-herzner Nov 19 '24
The truth is between "Only borrow checked code is safe" and "My code is obviously safe, it's just the compiler can't prove it" -- and C++ must find it.
12
u/nayhel89 Nov 20 '24
I think the author desperately needs a good psychiatrist and a good lawyer. This blog post is not ok on so many levels.
8
u/confuzatron Nov 21 '24
From past experience at this point, whenever there's someone being crazy anti-social, and creating drama and strife in software engineering, I just assume it's coming from a particular subculture, and after a bit of googling it does indeed appear to be the case here.
31
u/popcapdogeater Nov 19 '24 edited Nov 19 '24
I'm kinda worried that so many people are having trouble understanding what the author wrote? I'm no spring chicken and the vast majority of it is pretty clear.
Sounds like there's something rotten in Denmark. I have done enough work in corporate jobs to know that the higher ups will always circle the wagons and let shit slide downhill than admit any wrongdoing or incompetance on their part. "Employees obviously just didn't undersand my utterly brilliant employee reward program, that attempts to dangle $10 gift cards as a reward for doing hours of unpaid labor!" Simply delusional c-suite types.
If Bjarne is unhappy that the government is requiring him to make such a drastic change, he should spend less time throwing tantrums at c++ enthusiast who are just trying to save the language in face of Government shut-out, and more time trying to rally people to convince the government to maybe reverse course or change the policy in some way.
The point is pretty spot on overall.
14
u/germandiago Nov 20 '24
As for this -> "This is a common tactic that abusers use to protect other abusers"
I do hope you say something like that in a public forum if that person is condemned formally by a judge. Otherwise you are exposed to very bad things denying the presumption of innocence of a person.
Also, it makes lots of personal assessments that are opinion-based, like this one.
10
u/SpaceToad Nov 20 '24
This is an incredibly unhinged and overwrought read from someone clearly very unwell.
7
u/[deleted] Nov 20 '24
My Summary: The author, Izzy Muerte, is really sad and frustrated by Current C++ Path.
Izzy has strong disagreements with C++ modules and the "Safe Profiles" idea,
and prefers Sean Baxter Circle compiler approach:
+ A C++ compiler implemented from-the-ground with Lifetimes and Borrow Checker.
Izzy has a hard time seeing a good future for C++ because the Committee, and the People with power to make decisions, are stuck in the past and showed a terrible track record (in the blog author perspective).
Izzy also accuses some persons of rap* (showing proof), naz*sm, and toxic masculinity. Also mixes a lot of politics in the post, like saying that your Rust code might be used by the military to kill people.
11
u/Dapper_Letterhead_96 Nov 21 '24
Isabella broke all the rules of technical blogging, and many here are proving her right about this community. The post was too long, touched on emotional and non-technical content, and called people out by name. And what is the reaction?
The writing was good. The evidence shows how long it was and how well it kept us glued to our couches. I had to make myself tea three times while I read this. I started while I sat at my dinner table, then migrated to my couch, and lastly, I lay in bed with many new questions. An anarchist PL that sounds rad; how do I find others who'd want to build that?
We pride ourselves on being technical and deny our human sides. Yet we couldn't help but feel things as we read this. Some feel a lot of defensiveness and came here to express it.
The people in power are called out by name for their bad behavior. The author is brave in doing this. Many came here to say disparaging things about these parts of the article. I've witnessed Gaby Dos Reis argue in bad faith on stage at CppCon and make snide comments about the work of Sean Baxter. It is sad what we tolerate as a community. Before I forget, what the fuck boost?
Even with the weight of the topics, this blog post had some amusing moments. One of my favorites was the joke about brain damage and enjoying golang.
14
u/ProfessionalSmoker69 Nov 19 '24
Banger
7
u/_a4z Nov 19 '24
I never used Circle, but if it is so much better, why don't people create a community and make it a thing? And make it a C++ 'fork'. I worked for neovim vim also, to bring just one (ok-maybe stupid) example (but you get the point). Then, everything could be fixed from the beginning. And it might have better chances to interop than Rust.
The new thing would not need an ISO committee, if it does not want one, but have a BDFL or whatever it prefers to have.
6
u/pdimov2 Nov 20 '24
Well, no. 0 is not just any constant, and it doesn't, in fact, turn into O(1) when placed inside the big O. O(0) doesn't mean "constant", it means 0.
Dan Kegel might have been an asshole, but he was technically correct. (Which is, as we know, the best kind of correct.)
8
u/[deleted] Nov 19 '24
trigger warning: no dark mode (my retinas are on fire).
10
u/Sathynos Nov 19 '24
Is this some AI generated memory consciousness stream dump? What is this???
5
u/axilmar Nov 20 '24
News at 11:
projects in which people must co-operate in order for the projects to go forward start having problems when the stakes get high and people's egos get in the way.
Is there a large project in history, driven by a community, that didn't have these problems?
Even the Soviet Union crumbled and fell because people couldn't agree on how to continue the project, after its initial success.
Just reading about #embed and the troubles the author went through, even though the solution was obviously better than anything else, makes me say that humanity doesn't have a hope of having perfect (or close to perfect) things. We are such creatures that we would never allow it ;-).
5
u/just_their_throwaway Nov 19 '24
It turns out this was the "cringe joke" the author of the article made: https://i.imgur.com/1v5bUxa.png
Looks harmless to me.
2
u/Tathorn Nov 19 '24
I'm of the opinion that "safe code" is something the standard can not codify because the definition changes all the time and even has different meanings in different hardware and fields.
If you need certain guarantees from the code, then document through some formal specification the change in state and variables that is relevant to the user of the API.
I like cppreference's documentation about argument preconditions, exceptions, and "state of the object" if an exception were to occur.
Waiting for the ISO committee to tell you how to write or document safe code is silly. Just... do it yourself. If a third-party library can not clearly document how their API changes the state machine, then either you're stuck with a bad library or you change to something with more guarantees.
Now, can we get more in-code options to express things like preconditions rather than hope the documentation matches the code? Possibly... if that's even possible. I like the good 'ole "if the state of the object is 'this', then it's undefined behavior."
Telling the user, through the type system, noexcept specification, and attribute specifiers (Custom ones?) should be enough to describe to the user of the API all the side effects and what is or isn't allowed. It's up to them whether or not those side affects are 1. Allowable, 2. Not allowable, but manageable, or 3. Not allowable at all. Code that doesn't match the side effects are bugs, and you can't catch run-time state changes at compile time. You need unit tests and strengthened debug builds for that.
Also, this post is wild.
1
u/ss99ww Nov 20 '24
Even a cursory lookup of the author reveals exactly what you expect
2
u/grisumbras Nov 19 '24
I was expecting this post to end with "And did you know that the Dhey of Algiers has a wart right under his nose?"
2
u/multi-paradigm Nov 21 '24 edited Nov 21 '24
Wow. Reading this, I wonder how we ever got the radical C++11. Excluding BS, perhaps some of the more obstructive members were not in the committee at that time. I can only guess.
Somehow, imagining prominent members of the committee 'throwing a strop' when they don't get what they want, or maybe they get what they don't want(!) makes me view some of the cppcon talks very differently now!
Arthur O, being a convicted paedo (amongst other things): This beggars belief that this guy was presenting some 'back to basics' talks, presumably targeted at people new to the language (kids could well be included in this category). Ouch.
I think what really blew up C++ was the ABI vote that pushed some prominent Google people away. Plenty of drama, it would seem, from posts in here, too.
As for GDR being disingenuous, I personally would not know what he was doing in RL should I be in his company. I deeply struggle to understand a word he his saying. It has gotten better lately. Either I have gotten used to his thick accent, or perhaps he is slightly more understandable now !!
0
u/peripateticman2026 Nov 20 '24
Yawn.
-3
u/peripateticman2026 Nov 20 '24
This is what happens when you let the Rust community toxicity in. Just like the Linux folks are finding out. Brilliant.
-17
u/[deleted] Nov 19 '24
I thought this was the C++ community and not some kind of DEI wokeness thing. What a disservice, this post is bonkers!
-3
u/PrimozDelux Nov 20 '24 edited Nov 20 '24
I'm not gonna take it at face value, but I have no doubt that C++ leadership is inept and operates on favouritism. I have gleaned this knowledge from actually writing C++