‹ BackHN Continuity

Thread

EDG C++ front-end goes public

249 points · 129 comments · iandinwoodie

  1. jabl · · focus · HN ↗
    What's not mentioned in the announcement (at least based on a quick skim) is that EDG the company is winding down, which is likely the reason why they're open sourcing the front end.

    <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Edison_Design_Group" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Edison_Design_Group ref 9: <a href="https:&#x2F;&#x2F;herbsutter.com&#x2F;2025&#x2F;11&#x2F;10&#x2F;trip-report-november-2025-iso-c-standards-meeting-kona-usa&#x2F;" rel="nofollow">https:&#x2F;&#x2F;herbsutter.com&#x2F;2025&#x2F;11&#x2F;10&#x2F;trip-report-november-2025-...

    1. whobre · · focus · HN ↗
      Sad. Those folks are some brilliant computer scientists.
      1. splicebot · · focus · HN ↗
        Not really sad. They are getting older, worked for themselves doing presumably what they wanted their entire career, now they are done. They could have built the company up, instead it has been common knowledge for close to 10 years they were going to retire &#x27;any day now.&#x27;
        1. whizzter · · focus · HN ↗
          Building a company is so fraught with pitfalls, probably realized at some point that their income was good enough that they could safely work towards retiring at some point in the future without problems and drama.
      2. MFHava · · focus · HN ↗
        Don&#x27;t be sad for them. AFAIK those that didn&#x27;t retire are now at Nvidia - hopefully continuing to improve the frontend...
    2. vlovich123 · · focus · HN ↗
      &gt; John was the most vocal person pointing out technical problems with the feature; the committee decided it did not agree and standardized the feature anyway over his and EDG’s sustained objections; and then instead of sitting back and saying “we told you so,” EDG ended up being the only company in the world who ever implemented the feature! To add a sense of proportion: It took the same team longer to implement just the C++98 export template feature than to implement a compiler front-end for the entire Java language. But John and EDG went and did it, to support the committee’s consensus decision… only to have the committee remove export template again a few years later, because John and EDG had been right about the feature’s problems. That’s a model of solid professional behavior.

      Yes, but no reflection on the burn out this causes for the c++ community?

      1. watinthedeutsch · · focus · HN ↗
        EDG has been consistently the most vocal opposers of anything that goes in the language, and in recent years had stopped keeping up. The `export` thign was an exception.
        1. daveedvdv · · focus · HN ↗
          Sorry, but that&#x27;s nonsense. We&#x27;ve supported plenty of features. We&#x27;ve also occasionally been the first to implement them. In recent years, we spearheaded reflection, supported, first-implemented a bunch of constant-evaluation features (consteval etc.), and supported and first-shipped C++23 &quot;explicit this&quot;.
        2. fg137 · · focus · HN ↗
          Doesn&#x27;t make sense. C&#x2F;C++ static analyzers wouldn&#x27;t be using EDG if it can&#x27;t keep up with the language.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.