I build runtime software where ordinary application code meets constrained systems: Windows kernel drivers, NT Native APIs, Win32 APIs, Chromium/Electron internals, media pipelines, and typed transports for TypeScript and Rust.
Most of my work is about making hard boundaries usable: kernel/user mode, native/browser, main/renderer, worker/process, protocol/runtime, and missing behavior in stock runtimes.
- CRT/STL support for practical C++ development inside Windows kernel drivers.
- Chromium/Electron and Linux media source work for Chrome VA-API hotpatching, VA-API HEVC/H.265, NVENC-backed VA-API encode paths, Widevine packaging, preload coverage, trusted input dispatch, text-state APIs, and browser identity control.
- Type-safe runtime bridges across Electron CDP, MessagePort, Web Workers, Node.js processes, and Rust services.
| Project | Core idea | Why it matters |
|---|---|---|
| crtsys | C/C++ runtime library for Windows kernel drivers. | Brings CRT/STL-like development patterns, C++ runtime features, and driver helpers into a restricted WDK environment. |
| win32-ex | Native Win32 extension layer. | Turns noisy service, process, session, token, privilege, SID, and security-descriptor code into reusable C++ APIs. |
| ext | Portable C++ utility library. | Collects the small building blocks real systems keep needing: result, process control, pipes, callbacks, URI/version parsing, strings, units, and compatibility helpers. |
| electron-port-workspace | Reusable Electron/Chromium feature-port workspace. | Carries source-level features such as Linux VA-API HEVC/H.265 work, Widevine packaging, preload coverage, trusted input dispatch, text state APIs, print/dialog handling, and browser identity fixes across Electron targets. |
| chrome-vaapi-hotpatch | Linux Google Chrome VA-API enablement runtime. | Makes official Chrome use VA-API paths that stock Linux Chrome still does not expose: WebCodecs H.264 encode with shared-memory I420 input, Chrome-side HEVC/H.265 encode support through trampoline/delegate injection, and HEVC decode checks across Intel and NVIDIA without replacing the system browser. |
nvidia-vaapi-driver (nvenc) |
Experimental NVENC encode path for NVIDIA VA-API. | Adds capability-gated H.264/HEVC/AV1 VAEntrypointEncSlice exposure, rate-control mapping, direct CUDA/DMABUF import paths, NVENC 13 headers, and runtime encode/decode validation. |
| electron-cdp | Typed DevTools Protocol helpers for Electron. | Makes CDP sessions, command/event typing, context tracking, iframe/worker attachment, evaluation, and serialization easier to use from TypeScript. |
| electron-protocol-provider | Application-style routing for Electron custom protocols. | Treats custom schemes as structured routes with methods, path parameters, request objects, responses, and context injection. |
| typed-message-transport | Type-safe message transport for JavaScript runtimes. | Keeps request/response contracts explicit across MessagePort, workers, Node.js processes, and other serializable transports. |
| wsmq-rs / service-rs | Rust messaging and service lifecycle experiments. | Explores protocol-buffer-backed WebSocket flows, request/reply handling, progress hooks, and pause/resume/stop service states. |
| ts-default / isim-rs | Small boundary-focused tools. | Covers tiny but useful API conventions such as explicit default values and Node/Rust native-addon experiments. |
- Make restricted runtimes feel less isolated from normal application development.
- Prefer explicit contracts at process, protocol, worker, renderer, and native boundaries.
- Treat patches, build scripts, packaging, and upgrade notes as part of the product surface.
- Keep code portable across compilers, OS targets, SDK/WDK versions, Electron majors, and Chromium source trees.
Also maintained: ldk, util-linux-cpp and ci-version. Some public forks are research and contribution branches around Electron, Chromium, CEF, LLDB/GDB/MI debugging, Windows internals, and driver techniques.
For project-specific questions, open an issue in the relevant repository. For collaboration, start from the project closest to the runtime boundary you care about.