IdeaWell

Project ideas from Hacker News discussions.

Solo – a .so loader for static Linux binaries

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

1. glibc/loader coupling creates ABI fragility

“Mapping parts of files into executable memory, and then executing them, had better be bulletproof!” – arjvik

2. Alternative loader approaches aim for cross‑libc portability

“backed by its own ELF loader (x86‑64 and aarch64) and a glibc ABI bridge” – j16sdiz
“Now it’s possible! Furthermore, SoLo binaries can run, without modification, on glibc‑based distros, Alpine, and soon on Android/bionic.” – pg83

3. LLMs are used for documentation, raising quality‑perception concerns

“By writing your documentation with Claude, my brain immediately associates the quality of the project with the quality of unreviewed Claude output.” – dummydummy1234

4. glibc versioning makes simple “old‑glibc” linking non‑trivial

“glibc has a terrible history of binary incompatibility.” – pg83

🚀 Project Ideas

[ELFPort]

Summary

  • Generates self‑contained, cross‑distro binaries that embed a tiny ELF loader, eliminating the need to ship glibc‑specific libraries.
  • Core value: run the same executable on glibc, musl, and Android bionic without recompilation.

Details

Key Value
Target Audience Independent developers distributing command‑line tools or small apps to a broad Linux audience.
Core Feature Builds a minimal loader shim, bundles it with the user binary, and produces a single self‑contained executable that detects and bridges multiple libc ABIs at runtime.
Tech Stack Rust (for safety), libelf‑rs, custom C shim, Github Actions for CI, Docker for cross‑distro testing.
Difficulty Medium
Monetization Revenue-ready: SaaS tiered pricing (Free hobby builds, $9/mo for commercial builds, $49/mo for priority CI).

Notes

  • Hacks like pg83’s “solo” already exist, but ELFPort adds automated ABI detection, extensive regression testing, and a vetted loader, which HN users repeatedly asked for.
  • Solves the “cannot load proprietary GPU drivers on static binaries” problem by providing a loader interface that can be extended with vendor‑specific shim libraries.

[GPUStatic]

Summary

  • Provides a static‑linking SDK that abstracts vendor GPU drivers (Vulkan/GL) so they can be used without glibc‑linked shared objects.
  • Core value: enables fully static binaries to access GPU acceleration on any Linux host.

Details

Key Value
Target Audience Game developers, scientific visualisation teams, and ISVs shipping proprietary GPU‑heavy applications.
Core Feature Supplies a thin wrapper that loads vendor driver .so files via direct kernel DRM ioctls and Vulkan loader entry points, circumventing glibc dependency.
Tech Stack C++20, Vulkan SDK, Linux DRM/KMS, Docker CI for testing across Ubuntu, Fedora, Alpine, Android.
Difficulty High
Monetization Hobby

Notes

  • Directly addresses arjvik’s security concerns: the wrapper enforces strict capability checks and sandboxing before executing driver code.
  • HN discussion highlighted the impossibility of static GPU usage; GPUStatic offers a concrete solution, likely generating strong community interest.

[CrossDistroPackager]

Summary

  • SaaS platform that takes source code and automatically produces multi‑libc binaries (glibc, musl, Android bionic) with built‑in loader, handling ABI variations.
  • Core value: one‑click distribution of portable executables across all major Linux platforms.

Details

Key Value
Target Audience Open‑source maintainers, indie SaaS founders, and hobbyists wanting to ship binaries without Docker or VM farms.
Core Feature Accepts a Git repo, runs 1000‑package test suite across distro containers, generates ABI‑aware binaries, and provides a downloadable zip with per‑platform artifacts.
Tech Stack Python backend, GitHub Actions, Docker images for Ubuntu, Debian, Alpine, Bionic; SQLite for storing build metadata.
Difficulty Low
Monetization Revenue-ready: Pay‑as‑you‑go $0.01 per build, or $49/mo for unlimited builds and private repo access.

Notes

  • Directly answers pg83’s frustration about building for every distro and account42’s call for an “easy mode SDK.”
  • Community would likely discuss its impact on Docker/flatpak alternatives and potential to replace many existing packaging workflows.

[glibcGuard CI]

Summary

  • Integrated CI service that validates binaries against a matrix of glibc versions, automatically generating fallback builds and reporting compatibility gaps.
  • Core value: prevents shipping binaries that break on older distributions, reducing support overhead.

Details

Key Value
Target Audience DevOps engineers, CI maintainers, and open‑source project maintainers.
Core Feature On each PR, spins up containers with glibc 2.17–2.35, runs the binary through a suite of system‑call stress tests, and returns a compatibility score plus recommended fallback version.
Tech Stack Go, Docker Compose, Prometheus monitoring, PostgreSQL for storing results, Web UI for dashboard.
Difficulty Medium
Monetization Revenue-ready: Free tier (up to 100 builds/mo), $29/mo for professional tier with Slack notifications and audit logs.

Notes

  • Addresses the repeated mentions of “build against oldest glibc you want to support” and the fear of breaking on future distros.
  • HN participants often lament the lack of automated compatibility testing; glibcGuard CI would fill that niche and spark discussion about best practices.

Read Later