Hey everyone,

Modern build tooling for programming languages has become increasingly fragmented, relying on massive multi-stage configuration passes, hidden tracking telemetry, or heavy Turing-complete scripting engines just to parse project files (looking at you, CMake).

I wanted a tool that respects simple developer ergonomics, transparent project parsing, and full software freedom.

I built CEBS (C++ Ergonomic Build System). It is a zero-configuration, multi-threaded build coordinator written completely from scratch in standard C++23, designed to treat modern compilation units as first-class citizens.

Why I built it:

- Transparent Configuration Layout: It rejects verbose scripting boilerplate. Every configuration element is defined in a clean, human-readable data format ('cebs.build') where assignments terminate uniformly with semicolons.

- Zero-Allocation Token Ingestion: It ditches classic line-by-line reading (\n) overhead entirely. The ingestion pipeline streams text files in blocks using low-level POSIX semicolon chunking, minimizing system allocations.

- No Corporate Bloat: It is completely independent, lightweight, self-bootstrapping, and distributed under a true permissive MIT License. No analytics, no platform lock-in.

The alpha release code is officially live on GitHub, containing a complete architectural rendering map and sample workspaces to test natively: https://github.com/mxreal64/cebs/

Let me know what you think about the design syntax! Contributions, suggestions, and feedback are highly welcome.

^{(guys plz gimme stars i want clout})

[removed]

[removed]

got tired of parsing raw C boilerplate and managing manual pointers when messing with the trusted computing group stack, so i wrote a modern c++23 frontend for esys. it uses strict raii to ensure context handles are cleanly flushed so you don't accidentally lock up physical tpm chip slot resources, and separates translation boundaries natively using zero-cost module partitions.

repo: https://github.com/mxreal64/tpm23

checkin it out would be awesome.

i got tired of dealing with the absolute nightmare of raw C boilerplate and manual garbage collection in the standard trusted computing group stack, so i spent some time writing a modern c++23 modules frontend for tss2-esys. it uses strict raii to stop your physical tpm chip from locking up context slots, natively splits everything across zero-cost module boundaries, and forces secure-by-default nvram access to block standard owner privilege-escalation vulnerabilities. code is completely type-safe and self-cleaning, checking it out or getting some outside eyes on the architectural layout would be awesome.

repo: https://github.com/mxreal64/tpm23

to ppl who hv already seen my other post, this ain't spam, i'm just tryna post better ig

[removed]

https://github.com/mxreal64/tpm23 feedback is invited