News for hackers. Stuff that matters.
Re:RISC-V takes first step toward international ISO/IEC stan... by tester756 on Wednesday November 05, 2025 @06:44AM (#45821818)
C++ "standard" sounds more like an example of why technology should avoid standards
Re:RISC-V takes first step toward international ISO/IEC stan... by 112233 on Wednesday November 05, 2025 @07:03AM (#45821953)
Titanic is not an example of why building ships has to be avoided. C++ is a great example, yes, of the damage ambitious and egotistical personas can inflict when cooperation is necessary.
Re:RISC-V takes first step toward international ISO/IEC stan... by usrnm on Wednesday November 05, 2025 @08:01AM (#45822389)
Say what you will about C++, but it is undoubtedly one of the most successful and influential programming languages in history.
Re:RISC-V takes first step toward international ISO/IEC stan... by high_na_euv on Wednesday November 05, 2025 @09:32AM (#45823253)
By which metric?

C, Java, Rust, JS, C# do exist

Re:RISC-V takes first step toward international ISO/IEC stan... by nutjob2 on Wednesday November 05, 2025 @12:59PM (#45825843)
> influential

It's certainly a cautionary tale

Re:RISC-V takes first step toward international ISO/IEC stan... by actionfromafar on Wednesday November 05, 2025 @06:48AM (#45821839)
If we are taking cheap potshots, there's a standard for standards: https://xkcd.com/927/ or in the proposed XKCD URI form xkcd://927
Re:RISC-V takes first step toward international ISO/IEC stan... by tialaramex on Wednesday November 05, 2025 @09:48AM (#45823403)
It is certainly an example of why SC22 is a bad idea

The "C++ Standards Committee" is Working Group #21 of Sub Committee #22, of the Joint Technical Committee #1 between ISO and the IEC.

It is completely the wrong shape of organization for this work, a large unwieldy bureaucracy created so that sovereign entities could somehow agree things, this works pretty well for ISO 216 (the A-series paper sizes) and while it isn't very productive for something like ISO 26262 (safety) it can't do much harm. For the deeply technical work of a programming language it's hopeless.

The IETF shows a much better way to develop standards for technology.

Re:RISC-V takes first step toward international ISO/IEC stan... by jcranmer on Wednesday November 05, 2025 @10:02AM (#45823594)
The fact that the C++ committee is technically a subgroup of a subgroup of a subgroup is among the least of the issues of ISO for standardization.

The main problem is that ISO is a net negative value-add for standardization. At one point, the ISO editor came back and said "you need to change the standard because you used periods instead of commas for the decimal point, a violation of ISO rules." Small wonder there's muttering about taking C and C++ out of ISO.

Re:RISC-V takes first step toward international ISO/IEC stan... by tialaramex on Wednesday November 05, 2025 @12:26PM (#45825440)
I would argue that the structural problem is an underlying cause. So it won't be the proximate cause, but when you dig deeper, when you keep asking like a five year old, "But why?" the answer is ultimately ISO's structure and nothing to do with Bjarne's language in particular.

Hence the concern for the non-language but still deeply technical RISC-V standardization.