nowfound

Dev tools · alternatives · 2026

24 alternatives to Threadprocs – executables sharing one address space (0-copy pointers)

This project launches multiple independent programs into a single shared virtual address space, while still behaving like separate processes (independent binaries, globals, and lifetimes). When threadprocs share their address space, pointers are valid across them with no code changes for well-behaved Linux binaries. Unlike threads, each threadproc is a standalone and semi-isolated process. Unlike dlopen-based plugin systems, threadprocs run traditional executables with a `main()` function. Unlike POSIX processes, pointers remain valid across threadprocs because they share the same address…

Threadprocs launches multiple independent programs into a single shared virtual address space on Linux, allowing them to behave as separate processes while sharing memory. Unlike traditional threads, each threadproc… Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes.

  1. 1UC
  2. 2

    A fun toy memory allocator (not thread safe, that's a future TODO). I also wanted to explain how I approached it, so I also wrote a tutorial blog post (~20 minute read) covering the code which you can find the link to in the README.

    Nov 2025 · github.com · its alternatives →

  3. 3

    I wanted to see how fast an isolated code sandbox could start if I never had to boot a fresh VM. So instead of launching a new microVM per execution, I boot Firecracker once with Python and numpy already loaded, then snapshot the full VM state. Every execution after that creates a new KVM VM backed by a `MAP_PRIVATE` mapping of the snapshot memory, so Linux gives me copy-on-write pages automatically. That means each sandbox starts from an already-running Python process inside a real VM, runs the code, and exits. These are real KVM VMs, not containers: separate guest kernel, separate guest…

    Mar 2026 · github.com · its alternatives →

  4. 4

    forkrun is the culmination of a 10-year-long journey focused on "how to make shell parallelization fast". What started as a standard "fork jobs in a loop" has turned into a lock-free, CAS-retry-loop-free, SIMD-accelerated, self-tuning, NUMA aware shell-based stream parallelization engine that is (mostly) a drop-in replacement for xargs -P and GNU parallel. On my 14-core/28-thread i9-7940x, forkrun achieves: * 200,000+ batch dispatches/sec (vs ~500 for GNU Parallel) * ~95–99% CPU utilization across all 28 logical cores, even when the workload is non-existant (bash no-ops / `:`)…

    Mar 2026 · github.com · its alternatives →

  5. 5

    Non-preemptive Thread Hierarchy Manager. Contribute to gueststar/nthm development by creating an account on GitHub.

    2020 · github.com · its alternatives →

  6. 6

    A "living" Linux process with no memory. Contribute to izabera/zeromaps development by creating an account on GitHub.

    2020 · github.com · its alternatives →

  7. 7

    A little web server written in C for Linux. Supports: CGI, Reverse Proxy. Single threaded using I/O multiplexing (select).

    2023 · github.com · its alternatives →

  8. 8

    Hello everyone, Today we released iceoryx2 v0.4! iceoryx2 is a service-based inter-process communication (IPC) library designed to make communication between processes as fast as possible - like Unix domain sockets or message queues, but orders of magnitude faster and easier to use. It also comes with advanced features such as circular buffers, history, event notifications, publish-subscribe messaging, and a decentralized architecture with no need for a broker. For example, if you're working in robotics and need to process frames from a camera across multiple processes, iceoryx2 makes it…

    2024 · ekxide.io · its alternatives →

  9. 9

    Tasks are a primitive for asynchronous programming and an alternative to working with threads directly. Instead of creating a thread, performing work, then waiting on it using synchronization primitives, you only define a unit of work and let a scheduler decide when and where to execute it. The threads that the scheduler uses are created once and reused for many tasks throughout the program's lifetime. In most cases, creating and executing a task requires not even a single syscall and is a significantly faster operation than creating a thread, resulting in lower latency. Furthermore, tasks…

    2024 · github.com · its alternatives →

  10. 10

    Long-simmering side project that is finally ready to see the light. HAMTs are a cool persistent data structure and implementing one has been a lot of fun. Beyond the code, there is likely some value in the extensive and largely complete implementation docs; basic benchmarks are linked in the README, too. Kind of aiming to be "the libavl for HAMTs". That is obviously a high and aspirational bar but a distinct possibility if it stirs up a little interest and/or contribution. Anyways, it's time for this to go out, collect feedback and maybe even some use outside of toy projects. Let me…

    2023 · github.com · its alternatives →

  11. 11

    A simple way to write standalone C programs for i386 - luke8086/boot2c

    2019 · github.com · its alternatives →

  12. 12

    shpool is a terminal session persistence tool developed internally at google to support remote workflows, which we have open sourced.

    2024 · github.com · its alternatives →

  13. 13IB

    This weekend I created stacklib.h - a single-header library that brings Forth-style stack operations to C. It implements a basic interpreter with: - Stack operations (push/pop/dup/swap/over/drop) - Arithmetic (+, -, *, /) - Output (., emit, cr) - Stack inspection (.s, depth) Example usage: Stack s; stack_init(&s); dict_init(); exec(&s, "10 20 + ."); // Prints "30" exec(&s, "1 2 3 4 .s"); // Shows stack contents The library is self-contained, requires no dependencies, and handles basic error checking. It was inspired by wanting to understand…

    2025 · its alternatives →

  14. 14

    Moved to Forgejo! Contribute to krig/LISP development by creating an account on GitHub.

    2018 · github.com · its alternatives →

  15. 15

    An implementation of a dynamic programming language in Rust. Includes: Parser/Compiler, REPL, Virtual Machine, Bytecode Disassembler This started out as a learning project to teach myself Rust. It has grown into a decently substantial piece of software and I've learned quite a bit in the process! Some neat things: + A garbage collector that can store dynamically sized types without any double-indirection (i.e. I have my own Box implementation with manual alloc/dealloc) + The smart pointer used to reference GCed data is a thin pointer. The ptr metadata needed for DSTs is stored in…

    2022 · github.com · its alternatives →

  16. 16DM
  17. 17

    A cross-language, zero-copy coroutine observability framework based on the cTP shared-memory protocol, utilizing lock-free ring buffers for ultra-low overhead state tracing. - lixiasky-back/coroTracer

    Mar 2026 · github.com · its alternatives →

  18. 18

    Hey HN, this is Will and David from Fortress (https://news.ycombinator.com/item?id=41426998). We use a lot of async Rust internally, and created this library out of a need for an async-aware concurrent hashmap since there weren’t many available in the Rust ecosystem. Whirlwind is a sharded HashMap with a fully asynchronous API. Just as dashmap is a replacement for std::sync::RwLock, whirlwind aims to be a replacement for tokio::sync::RwLock. It has a similar design and performance characteristics to dashmap, but seems to perform better in read-heavy workloads with tokio's…

    2024 · github.com · its alternatives →

  19. 19

    This project contains no code from Linux, BSD, Minix, or any other OS. Everything up until this point is written entirely from scratch, including a pure microkernel (that only implements multiprocessor priority scheduling, memory management, and interprocess communication), a work-in-progress implementation of the standard C library, and a variety of servers that provide drivers and other essential OS functionality. At the time of writing this post, the servers provide drivers for the keyboard, NVMe SSDs (that works on real hardware), a Unix-like virtual file system (with a single root…

    2024 · github.com · its alternatives →

  20. 20

    Smart pointers for the (GNU) C programming language - Snaipe/libcsptr

    2015 · github.com · its alternatives →

  21. 21

    Simple, zero-dependency garbage collection for C. Contribute to mkirchner/gc development by creating an account on GitHub.

    2019 · github.com · its alternatives →

  22. 22

    Concurrency library for C (coroutines). Contribute to tidwall/neco development by creating an account on GitHub.

    2024 · github.com · its alternatives →

  23. 23IB
  24. 24

    If you work in C++, and you would like 2+ programs to share data structures (and/or native I/O handles a.k.a. FDs) among each other, there is a good chance Flow-IPC - will make it considerably less annoying to code than typical approaches; and - may massively reduce the latency involved. Those sharing Cap'n Proto-encoded data may have particular interest. Cap'n Proto (https://capnproto.org) is fantastic at its core task - in-place serialization with zero-copy - and we wanted to make the IPC (inter-process communication) involving capnp-serialized messages be zero-copy,…

    2024 · github.com · its alternatives →

Also compare

Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →