[–] 2 points 1 week ago*

As a member of one the objecting NBs (Finland), I think the problems here are far more complex than what this post addresses.

I've not been in the committee as long as Andreas has, but I've been trying to dig through historics as things have unfolded.

I think there are multiple causes, some of which are a decade old by now, why we ended up in this clusterfuck we are in. And yes, our NB voted knowing this clusterfuck might be the end result, even though it didn't seem probable to me (though I knew it was possible).

Am I happy we're in this mess? No. I don't think anyone in the WG21 is.

But I also think WG21 tends to forget that even though we call it "The C++ Committee", it is not an official ISO committee. We are a working group that presents the standard draft to the actual programming languages committee, that is SC22. A good bunch of WG21 members seem to forget this way too often. And a good bunch of them seem to just not have read the ISO code of conduct or rules altogether.

And the situation is not helped by a few individuals in the committee that basically shitpost misinformed or opinions why NBs did what they did based on WG21-internal rumours. And yes, there are ~200 active and around 500 in total WG21 members, so we are not going to avoid rumours.

There's a lot to unpack. From my point of view this divide started from how the ANSI/INCITS (the US NB) in 2014 changed from "one-company-one-vote" to "everyone votes individually" and how that effects the measured difference between WG21-internal polls and NB opinions. Even though that was what ISO wanted, as we are supposed to be individual experts inside WG21. But ISO also wants the NBs to have the final say, as NBs work as checks and balances from its perspective. From my understanding, WG21 used to have these checks and balances in the "one-company-one-vote" -rule, but since that is now gone, those have moved to the NB level. Which is what we see here. This has changed gauging the NB consensus inside the WG21 and made our internal polls less informative towards that direction. And it's a very small gradual change that comes from people following the systems without any greater purpose one way or an another.

I need to say that the above paragraph is just how I see it, but I'd love to know whether more WG21 members feel the same or can debunk it if I'm wrong.

Normally, my articles are technically focused and free of personal opinion. Regarding the rejected DIS, I can only say that I consider it a massive disaster and feel sorry for the entire C++ community.

I disagree with this. Sure, this is a blow to WG21, and a major shakeup there. But there are people who claim they saw this coming a full decade ago, just not sure when. If it wasn't for contracts, it would've been something else. And I have little reason to doubt them from what I've witnessed. And if that is the case, this needed to happen, and it might be better that it happened now than with greater consequences later on.

Saying it's a massive disaster for the entire C++ community, I don't buy. That said, I am sorry to those people who are hit by this, and I view this as a failure of the group I am a member of, and maybe I should've been more outspoken earlier, but I don't know if my voice would've been just one more cook in the entire mess, and I never will.

Regardless of whether someone likes Contracts, considers them important, or sees major weaknesses in them, the topic has been worked on for years and has received a majority vote multiple times in its current form. By voting “no,” an established system, one based primarily on trust and respectful collaboration, has been shaken.

This part is not really even an opinion, it's just true. Though how established that system truly was in reality is up for debate.

Every ISO standard is simply a set of compromises. Everyone loses sometimes, and everyone wins sometimes. Overall, the result is one in which all participants have given their best. During the DIS vote, the losing parties refused to accept their loss.

This is what I most vehemently disagree with. Making an international standard is not about winning or losing. And if NB comments are not acted on, even if they are heard, there is very little reason to those NBs to change their vote. As WG21, we, unlike in most previous cases, but using the same process as previously, gambled that the dissenting voices were not numerous enough to vote down the DIS. That gamble did not pay off and now we're here.

The reality I see from historical notes and the current situation here is that WG21 has changed both in composition and how seriously it has taken the NB votes. Our processes have not kept up with the changes, and this is the end result.

The question that primarily determines how to move forward is whether the group can rebuild trust.

100% agree on this one.

  • source
  • [–] 5 points 3 weeks ago (4 children)

    What this means is:

    WG21, what we usually call "the C++ committee" is the working group that prepares the C++ draft to the actual ISO committee, that is SC22, that approves the standard.

    In WG21, people vote (or poll, really) as individual experts, who are members of one national board or an another. WG21 decided to send a draft to SC22 with knowledge that multiple national bodies (NBs) would object, it wasn't exactly a secret to anyone.

    Then, in the ratification of the actual standard, it is NBs from different countries that actually vote. These are usually the same people who take part in WG21 work, though NBs can decide by themselves how they choose their vote.

    In my national board, majority was against, with zero objections, so our NB chose to be one of the 9 countries who voted against. I do not know how other national boards work out their vote, but AFAIK most of them also have internal vote for that. This is how international standards committees are supposed to work, as to not have any country or entity push a standard that doesn't have clear consensus. There are varying opinions if that suits programming language development or not, and I'm not interested in that debate.

    For the standard to be ratified, it needs both 2/3s majority in favour, and no more than 1/4th objecting. Now the SC22 vote failed on both counts, which pretty much means there isn't going to be C++26. We don't have time in the committee to get it approved in 2026 anymore.

    I have my own thoughts about why we went from "zero objections ever" to failing both requirements. And even if I was part of the objecting votes, I hardly consider the result of having disapproved ballot a good outcome. It shouldn't have ever gotten to the point where that was even an option.

  • source
  • [–] 6 points 2 months ago (1 child)

    Meni suomalaisen naisen kanssa naimisiin että pääsee kohta suomeen takaisin.

    Morsian asuu uutisen mukaan Kurdistanissa, ja lumeavioliitot ovat syy hylätä oleskelulupa, ja oleskeluluvat voidaan hylätä / peruttaa rikostaustan takia.

    Jaff kertoo Iltalehdelle itse aikovansa vielä palata Suomeen ”jonakin kauniina päivänä”.

    Eli uutinen on about "Suomesta karkotettu tyyppi aikoo ehkä käyttää porsaanreikää, jota ei välttämättä oikeastaan edes ole olemassa, palatakseen Suomeen jonain kauniina päivänä."

    Riveting tale, chap.

  • source
  • [–] 13 points 5 months ago (1 child)

    En tiiä onko tää eka hallitus joka tota tietosesti tekee, mut ainaki tää o eka hallitus joka ylpeilee sillä.

    En tiiä, ite en usko et tää maa lähtee nousuu enne ku tullee joku seuraava katastrofinpoikane joka pistää ihmisiä tekkeen taas yhteistyötä sen sijaa et harrastetaa vaa toistemme sabotoimista minkä keritään. Toivoin että tää hallitus ois ollu tarpeeks iso katastrofi siihe, mut näköjää ei.

  • source
  • [–] 11 points 8 months ago

    En tiiä rajoittuuko toimittajiin. Oon kiertänyt noita EU:n avosorsatapahtumia yms., ja tuntuu olevan täysin ylitsepääsemätöntä isolle osalle tajuta, että aivan kaikkia palveluja ei tehdä kaupallisilla perusteilla. Eikä tuo edes ole minkään blokin aivotorppaus, vaan useemmin siellä joutuu sanomaan et "niin, ei tätä oo tehty rahan tai näkyvyyen tai tämmösen takia."

    Koskee alustapalvelujen lisäksi about kaikkia muitakin digitaalisia palveluita.

  • source
  • parent
  • context
  • [–] 10 points 8 months ago (3 children)

    En tiiä missä Heikura on ollu IT-alalla, mutta tuossa Heikutan kommentissa ole kyllä mitään järkeä.

    Ei sillä että muutenkaan tuossa tekstissä mainituista kommenteista jäisi semmonen "nyt nää jätkät tietää mitä tapahtuu"-fiilis.

  • source
  • [–] 8 points 8 months ago* (2 children)

    Täs tulee ongelma kun ihmiset tajuaa ettei Sailfishillä toimi iso osa Eurooppalaisista pankkisovelluksista, EU:n puskemat iäntarkistushirviöt, eikä Google Wallet / Apple Pay.

    Oishan se kiva saaha kyllä puhelinkäyttiksiinki vähän kilpailua, mut toistaiseksi historia on opettanu että ihmiset valittee helppouden about kaiken muun yli. Tosin Jolla o ollu yks niistä firmoista, jolla siitä on kokemusta jo ennestään. Vois pitää peukkuja et tosta tulee jotain.

  • source
  • [–] 7 points 8 months ago (1 child)

    Niin kaua ku valtiota pyöritetää kvartaalitaloudella toivoen uutta Nokiaa samalla ku luovutaan niistä lähtöasetelmista, mistä Nokiaki aikoinaan syntyi, niin ei tän homman voi oottaa tästä paranevan.

    Ja asenteet on siirtynyt siihen suuntaan, et tätä samaa paskaa halutaan lisää, ei että siitä haluttais eroon. Ehkä vielä enne ku meikät kuopataan niin tää suunta kääntyy.

  • source
  • [–] 2 points 9 months ago

    In the early days of internet, when people could host mail servers with their residential connections, there were plenty of people who did not understand how to secure their SMTP server.

    That meant, even without those people realising it, their self-hosted mail servers were used as relays for spamming. That's why residential IPs SMTP ports are blocked AFAIK.

    I'm not sure even digital rights associations (EFFI in Finland) oppose this. If you want to self-host your mail, you pretty much need static IP address with good reputation anyways to get anything delivered.

  • source
  • [–] 4 points 9 months ago (1 child)

    Toivoisi että ainakin serverit vois pitää Suomessa, vaikka olisikin ulkomaalaisten firmojen ylläpitämiä. Siihen on kuitenki IMO hyvät teknisetkin perusteet, ja meikästä aika tärkeetä suvereeniteettiä ajatellen.

    Vaikkei tässä nykytilanteessa myöskään oo hirveen oleellista, niin meikästä ois silti hyvä, ettei me sidottais tuota EU/ETA-maihin sillä tavalla, että tilanteissa, joissa Suomi päättäis karata EU:sta syystä XYZ, niin sit pitäis muuttaa lainsäädäntöö siten, että vois pitää ratkaisujaan Suomessa. Toi toki voidaan tehä hyvin yksinkertaisesti lainsäädännössä vaikka tyyliin:

    "Soveltuvat maat (EU/ETA-maat, Suomi)" ja sit käytetään tota "soveltuvat maat".

    ...oon lukenu ihan liikaa lakitekstiä ja teknisiä speksejä lähiaikoina.

  • source
  • parent
  • context
  •  

    This community has been locked and we would like to redirect you to a similar, more active community at !cpp@programming.dev

    Would you like to reopen this community and moderate it? Contact Sopuli's admins or @ananas@sopuli.xyz and we can talk!

    Tämä yhteisö on lukittu ja haluaisimme ohjata sinut samankaltaiseen, aktiivisempaan yhteisöön !cpp@programming.dev

    Haluaisitko avata tämän yhteisön ja ottaa sen hoidettavaksesi? Ota yhteyttä Sopulin ylläpitäjiin tai käyttäjään @ananas@ananas@sopuli.xyz niin jutellaan!

    Ja jos on kiinnostusta suomenkielistä C++ -keskustelua kohtaan, niin @ananas@sopuli.xyz avaa tämän mielellään kunhan se ei ohjaa pois aktiivisemmasta keskustelusta.

    view more: next ›