Former C++ committee member writes schizopost about her problems with the committee, names names [bjarne & herb called out]

This person should've never been on the committee to begin with.

Their entire blog is Tunblr-tier attention seeking.

she

>me checking if no way c++ and a real she.

>yep

I just want to mention that I had gotten infected with the Omicron variant of COVID at an event in San Francisco 3 weeks prior to that post (everyone was vaccinated according to the organizers) and I was amongst the first people infected with Omicron. I nearly died, and while I was recovering I did ask myself the question "What the frick are we doing dude? What is the fricking point?" in regards to my career.

Several months later, I learned I had experienced slight brain damage due to hypoxia and I've been slowly recovering ever since. The worst part of all of this is that I said in that post that I was enjoying golang. In other words, I had brain damage and suddenly found writing Go to be fun. Take from that what you will 💀

In case you were wondering if this was a crazy person or not

The first is that nothing changes. Profiles get made, no one ever turns them on or the government says "this isn't good enough, try again". C++ joins the ranks of languages like COBOL, Bjarne's legacy is that he refused to get out of the way and his stubborn nature resulted in him killing his own language, is phased out for new projects at government contractors by 2030. Then any C/C++ code that I write becomes unusable by the American military and government, and I can sleep soundly knowing there is 0 chance of me every writing anything useful for the US Government.

That's an easy, easy win. Zig users might also be in this same place, assuming they stay the course and don't want to be used by governments. Rust users though, you're gonna have a rough time. Knowing the general political make up of so many people in the Rust community, I do question how you will sleep at night knowing that an open source library you wrote (and remember the open source definition requires no discrimination against use) might get used to murder civilians who get reclassified as enemy combatants (and before anyone comes screaming into my mentions online, Turkey is still trying to genocide Kurdish people)

Rust Go and memory safe c++ are evil because the US gov could use it to kill kurdish ppl. This is why we need an authoritarian left wing gov to ban open source so anti kurdish nazis cant use it.

More bizarre shit: this c++ blog contains a rant about Kurds for some reason

This isn't the first time the United States government has thrown supposed allies under the metaphorical bus. During the first Trump administration, we basically threw nearly 20+ years of working with the Kurdish people to the wayside. The people in the AANES, also known as Rojava (and what I will use for the rest of this aside), have had very long standing agreements with the United States government (going back as far as the Iraq invasion), despite their political stance to be very left. Turns out when you're an ethnicity and culture without a place to be recognized on the world stage you might just make a deal with the literal devil.

Rojava and the groups located within it were extremely important in taking out members of ISIS, however when Turkey began their attempt at genocide against the Kurdish people, many ISIS members escaped.

As much as I would love to talk in detail about Rojava, their complex sociopolitical struggle for autonomy, their interactions on the world stage, and how even in the United States we have a large Kurdish diaspora located in Tennesee, it is so outside the realm of this blog post, that I need to put a pin in it.

I only skimmed about 20 pages, noticed he wasnt getting to any particular point, then used the scroll to find the nutter wrote an additional 50-100 pages. Wtf?

The blog post is incredibly entertaining.

A display of a person who doesn't realize the reason no one in the c++ committee wanted to engage with him is that he's just unpleasant. A person that threatened to physically hurt another member over a disagreement in slack, and he doesn't realize why he almost got kicked out. A person who gets triggered that other members have different opinions on how to achieve memory safety, and they dare defend their opinions on /r/cpp. Despite this, this person is still lecturing us on how people need to be nicer in tech and blabla.

A billion schizophrenic digression, from "the new boost logo has a nazi logo in it" and "justine tunney named it 'cosmopolitan' because she hates jews", to Rojava and dark souls and a bunch o other shit.

And what's most ironic is that in the end he's right: everyone is aware the c++ committee is dysfunctional and he just aired more dirty laundry.

I got wasted last night with a stranger who wrote the Circle C++ compiler. Is he actually a big deal in the community or just blowing smoke up my butt?

ngl her writing style is pretty schizo and based, so I did try to take what she's writing seriously.

Unfortunately she caught brain damage among other conditions and now everything she says, while stylistically great, is r-slurred.

In 1967, a 21m31s film was produced for the Philco-Ford Corp. (in celebration of their 75th anniversary), produced by the Tom Thomas Organization, titled "Year 1999 AD". Watch this film and you will see a variety of promises made regarding the future:

...

Except it's now the end of 2024 and the check list isn't fully filled out. And the Baby Boomers are starting to die out. And they need to know, before they're all gone, that the capitalists running various American industries held their promise. They are trying to say they've delivered on their promise. Even if the people in our position, the position of the average tech worker, know it's all fricking smoke and mirrors

What is she talking about? Nearly everything on the list she herself made came to fruition? What about "Children can watch moving entertaining videos at the push of a button" is smoke and mirrors? It's literally actually true.

Brain damage.

TIL @sneedman effortposts about C++

why are obsessed with memory safety?

I cannot think or comprehend of anything more cucked than writing BSD-licensed software. Honestly, think about it rationally. You are designing, programming, debugging and distributing a piece of software for any number of years solely so it can go and get used in proprietary projects by corporations. All the hard work you put into your beautiful software - writing good documentation, making optimizations, making sure it runs well on other machines, formatting it, troubleshooting it. All of it has one simple result: its codebase is more enjoyable for proprietary projects.

Wrote the perfect software? Great. Who benefits? If you're lucky, a random corporation who had nothing to do with the way it was developed, who uses it. That corporation gets to use it in spyware and DRM, like Minix and IME. It gets the benefits of the software's innovation and optimization that came from the way you programmed it.

As a programmer who writes BSD-licensed software, you are LITERALLY dedicating however many years of your life simply to program software for proprietary corporate/government projects to enjoy. It is the ULTIMATE AND FINAL cuck. Think about it logically.

Snapshots:

https://izzys.casa/2024/11/on-safe-cxx/:

• ghostarchive.org

• archive.org

• archive.ph (click to archive)

/r/cpp:

• undelete.pullpush.io

• ghostarchive.org

• archive.org

• archive.ph (click to archive)

SHOW MORE