#rewriteInC

The future is C.

Why rewrite in C? Build in the lowest common denominator: every language can call it, it runs on every platform, is smaller and faster, is computation modality independent (single/multi threaded, async/sync, messaging-passing / IPC / one process, etc.) and you win every tech nerd neckbeard debate.

License: All projects are Apache-2.0, MIT, or CC0 licensed.

Frameworks for 'end' developers

Libraries these depend on

std::filesystem inspired interface for C89 (MSVC2005, Cygwin, MSVC2026, Linux, macOS, etc.)
C++ 1
HTTP/HTTPS client interface reusing abstractions for Windows (WinHTTP,WinINet), macOS (CommonCrypto), iOS, Android, GTK+4 (libsoup), with fallback to libcurl
C 0
SQLite & PostgreSQL compatible simple ORM for C. Alembic/diesel style schema migration support. VERY portable.
C 0
OpenAPI ↔ C. Frontend for C, concentrating on: generation from code; single-file analysis; modification; and emission (prettyprinting).

Additional projects

string functions from newer standards / common non-standards for C89
C 2
UTF-8 replacement for C strings, supporting zero-copy use-cases (non-null-terminated).
C 1
Shared GitHub actions for my C projects to build & test on {MSVC,MinGW,Cygwin,Linux (gcc),macOS (clang)}
C 0