EDG C++ front-end goes public
- ID
- 30839
- Status
- summarized
- Published
- 01 Oct 2026, 3:26 AM
- Fetched
- 02 Oct 2026, 12:26 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://edgcpp.org/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 5.5
- Created
- 02 Oct 2026, 12:27 AM
- Tags
- Audience
- developers
What happened
On September 30, 2026, the source code for EDG's C++ front end went public, with The C++ Alliance — fiscal sponsor of Boost since 2024 and employer of LLVM/Clang front-end committers — taking over as its nonprofit steward. Development now runs on three tracks: community pull requests reviewed initially by experienced EDG developers, immediate bug-fix maintenance by Alliance engineers, and collectively funded features where organizations pay for a feature that is then released to everyone at once with no early access. The transition page frames this as a change of steward, not a change of course, for a 30-year-old source-to-source engine.
Why it matters
EDG's front end has historically been the licensed parser behind many commercial C++ compilers, so its move to a public repo with a funded-feature track changes the build-vs-buy decision: instead of licensing or maintaining a private front end, you can now read the source, send a PR, or pay to fund a feature your product needs and get it in the same public repo as everyone else. If you ship a C++ toolchain, static analyzer, or DSL that embeds a parser, this is worth a look at the repository before your next compiler dependency review — the practical question is whether contributing or co-funding here beats upstreaming to Clang/GCC, which the page does not answer.
Discussion angle
The collectively funded feature track — one organization pays, everyone gets it simultaneously, no early access — is the unusual part. Would that funding model work for a dependency your team relies on, or does paying for a feature you can't keep private make it a non-starter for commercial toolchain vendors?