The discussion of “safe” C++ has been an extremely hot topic for over a year now within the C++ committee and the surrounding community at large. This was mostly brought about as a result of article, after article, after article coming out from various consumer advocacy groups, corporations, and governments showing time and again that C++ and its lack of memory safety is causing an absolute fuckload of problems for people.

And unfortunately, this means that WG21, the C++ committee, has to take action because people are demanding it. Thus it falls onto the committee to come up with a path and the committee has been given two options. Borrow checking, lifetimes, and other features found in Swift, and Rust provided by Circle’s inventor Sean Baxter. Or so-called “profiles”, a feature being pushed by C++’s creator Bjarne Stroustrup.

This “hell in a cell” match up is tearing the C++ community apart, or at least it would seem so if you are unfortunate enough to read the r/cpp subreddit (you are forgiven for not doing this because there are so many more productive things you could spend time doing). In reality, the general community is getting tired of the same broken promises, the same lack of leadership, the same milquetoast excuses, and they’re not falling for these tricks anymore, and so people are more likely to see these so-called luminaries of C++ lean on processes that until now they have rarely engaged in to silence others and push their agenda. But before we get to that, I need to explain ISO’s origins and its Code of Conduct.

  • thingsiplay@beehaw.org
    link
    fedilink
    arrow-up
    0
    ·
    2 days ago

    At the top of the blog post:

    CONTENT WARNING

    Unfortunately, this post has mentions of rape and sexual assault.

    What the hell?

    • BatmanAoD@programming.dev
      link
      fedilink
      arrow-up
      0
      ·
      1 day ago

      The article is more about the behavior of members of the C++ committee than about the language. (It also has quite a few tangents.)

    • LearnedDonkey@kbin.earthOP
      link
      fedilink
      arrow-up
      0
      ·
      2 days ago

      If you think that’s WTH-worthy, then you definitely shouldn’t read the /r/cpp thread (sample comments: [1][2]).


      (edit to see if this will federate)

      • thingsiplay@beehaw.org
        link
        fedilink
        arrow-up
        0
        ·
        1 day ago

        This is a lot going on there. I’m thankful the blog poster did a content warning, I truly appreciate that. It’s a bit too hard subjects to read for me, so not going into details now.

        BTW I’m on beehaw and your reply looks like this to me, in case if it helps to see if it federates the way you was expecting it:

        If you think that’s WTH-worthy, then you definitely shouldn’t read the /r/cpp thread (sample comments: [1][2]).

        (edit to see if this will federate)

        • LearnedDonkey@kbin.earthOP
          link
          fedilink
          arrow-up
          0
          ·
          1 day ago

          RE federation, the comment only federated after the edit.

          I tried upvoting+downvoting myself first, which is a trick that may have helped in the past, but no dice. So federation doesn’t appear to be reliable unfortunately.

          I understand and don’t mind delays, but content still getting missing from federation queues is something i thought doesn’t happen anymore.


          Edit: This one federated within a couple of minutes. Not bad.