Live data from Hacker News

Wrapping Up 2021. Leaving C++

izzys.casa

111–120 of 251 posts

Re: Wrapping Up 2021. Leaving C++

#111
post #88

Quoted post unavailable.

I read the whole article before posting my comment (which is currently top voted, at least it looks like that to me, so maybe that's what you're objecting to). It's quite possible I've missed something, or a lot of things, but your comment isn't helpful determining that... You just said to read the whole thing again. Ok, but what specifically have I got wrong?

What gave you the impression I was directly referring to your comment?

Re: Wrapping Up 2021. Leaving C++

#112
post #88

Quoted post unavailable.

Oh, if I were invested in C++ I would be worried! And it sounds like the committee members should have some takeaways, for sure. But I'm not a member of that community. Bringing up one problem (C++ committee interaction) doesn't mean that is the only problem that was brought up. She has trouble communicating because she's very scrupulous, same as lots of other engineers - some people are responding to that problem. S…

I don't personally equate "scrupulous" to "[having] trouble communicating", nor do I really consider it a "problem". They are mutually exclusive.

Also, from a language design point of view, they have very strong opinions about language design and heavily criticize the design of all modern languages. That shouldn't be surprising to anyone. Programming language design is a field of CS. People are allowed to obsess over it. It'd be a shit world of people didn't obsess over specific fields of science. I can't believe I have to explain this.

The people here aren't arguing with the statements about language, but instead for the author even having opinions about languages at all. That's incredibly demeaning and dismissive.

Re: Wrapping Up 2021. Leaving C++

#113
post #108

> A lack of default arguments, a lack of basic arity overloading, a lack of variadic generics, all make me not want to write Rust. I'm sorry but these are such superficial problems. I don't need overloading (arity or otherwise) since Rust kind of has overloading thanks to the traits. Variadic generics might be necessary since C++ doesn't have a good macro system. But Rust does so you achieve it that way.

Rust has an abysmal macro system that cannot be properly tooled for.

I guess this is why macros aren't the be-all end-all solution to problems in language design: It's difficult to construct tooling around them.

It could be argued that "functions" are a form of programming language extension that are friendlier to tools. For programming-language fascinated beginners, this could be a good way of motivating "functions" as a language feature.

Re: Wrapping Up 2021. Leaving C++

#114
post #111

Earlier quoted context omitted.

I read the whole article before posting my comment (which is currently top voted, at least it looks like that to me, so maybe that's what you're objecting to). It's quite possible I've missed something, or a lot of things, but your comment isn't helpful determining that... You just said to read the whole thing again. Ok, but what specifically have I got wrong?

What gave you the impression I was directly referring to your comment?

Well, nothing in your comment gave me the impression you were referring to anything in particular. But I was honestly trying to understand what your point was. Really, it just comes across as unspecific rant, so I think I was being pretty generous.

Re: Wrapping Up 2021. Leaving C++

#115
post #111

Earlier quoted context omitted.

What gave you the impression I was directly referring to your comment?

Well, nothing in your comment gave me the impression you were referring to anything in particular. But I was honestly trying to understand what your point was. Really, it just comes across as unspecific rant, so I think I was being pretty generous.

What in my comment is "unspecific"? Most of the comments here are speculating about the author's mental state, claiming they must have self-diagnosed this issue (which isn't true), or that they just need to find another language to write apps in (missing the point they were an active contributor to the spec and cared deeply about this language). Very few of them are actually addressing the content of the article itself, instead dismissing the author as either insignificant to the cause or just being whiney, etc.

I have quite a few comments here pointing that out to people. If you didn't get much worth out of my comment, or if it was obvious, perhaps you weren't the intended reader.

Re: Wrapping Up 2021. Leaving C++

#116
post #88

Quoted post unavailable.

I read the whole article before posting my comment (which is currently top voted, at least it looks like that to me, so maybe that's what you're objecting to). It's quite possible I've missed something, or a lot of things, but your comment isn't helpful determining that... You just said to read the whole thing again. Ok, but what specifically have I got wrong?

Not OP, but I can tell you why your comment seemed armchair-psychologist-y to me. The issue is saying "it doesn't seem like her problem is actually X, it seems like it's Y." You read a short article written by someone who, based on the tone and explanation up top, was not in the best frame of mind.

The bigger issue with your comment from my perspective though is that you said "But it seems to me that they're still some way off from understanding their condition", which to my ears is just demeaning. Someone posts an article about leaving a community, with a lead in explaining their state of mind as of writing it, and your response comes down to "sounds like you don't understand your condition you were recently diagnosed with".

Personality disorders are hard, they don't go away and they can take years to get a handle on. When the top response to your article where you mention your disorder is someone saying you don't understand it, it becomes that much harder.

Re: Wrapping Up 2021. Leaving C++

#117
post #108

Earlier quoted context omitted.

Rust has an abysmal macro system that cannot be properly tooled for.

I guess this is why macros aren't the be-all end-all solution to problems in language design: It's difficult to construct tooling around them. It could be argued that "functions" are a form of programming language extension that are friendlier to tools. For programming-language fascinated beginners, this could be a good way of motivating "functions" as a language feature.

I agree, and I would love to see more exploration of this in non-toy programming languages for sure.

Re: Wrapping Up 2021. Leaving C++

#118
I actually like C++, it is not perfect for sure but it's getting better, plus the famous "there are only two kinds of languages: one that nobody uses, one that many complain".

In the end there is really no alternative, in fact there is none. I could not find a language to replace c++ myself in practice, so I will keep using it all the way.

Re: Wrapping Up 2021. Leaving C++

#119

> A lack of default arguments, a lack of basic arity overloading, a lack of variadic generics, all make me not want to write Rust. I'm sorry but these are such superficial problems. I don't need overloading (arity or otherwise) since Rust kind of has overloading thanks to the traits. Variadic generics might be necessary since C++ doesn't have a good macro system. But Rust does so you achieve it that way.

Can you explain how variadic generics are solved by traits, please?

Re: Wrapping Up 2021. Leaving C++

#120
post #64

I met Izzy a few times at cppcon and always came away impressed. I have basically the same thoughts about the c++ community -- it burns people out and it's filled with a ton of negativity and ego and it's very hard to get anything done. While I was at Google I spent some time trying to push for some sort of codes of conduct after a colleague of mine had a reasonable proposal ripped to shreds in email groups with all…

You do not need a code of conduct for complaining about a sexist remark inside a corporation. CoCs ruin projects, create a stifled atmosphere of hate and distrust and it is always the wrong people who obtain power.

Persons who are vocally against CoCs can very well be on your side regarding sexist remarks. Personal attacks are difficult to quantify. Often they are a last resort for shutting up someone who thinks they should dictate everything in a code base, even if it is outside their area of expertise.

Perhaps Google's C++ code base is too mission critical to let it be ruined?

Post reply on HN