Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

Orbit a systems level programming language that compiles .sh to LLVM

Details

External ID
46323693
Source
HN
Company
—
Product
Orbit a systems level programming language that compiles .sh to LLVM
Website domain
github.com
Launched
Dec. 19, 2025
Cohort
—
Upvotes
17
Upvotes percentile
0.6288167938931297
Tags
—
Fetched at
Sept. 7, 2026, 9:25 p.m.
Updated at
Sept. 7, 2026, 9:25 p.m.

Enrichment

Theme
developer tools and programming utilities
Vertical
Horizontal
Function
Dev tools
Audience
Developer
AI stance
Not AI
Project type
Hobby / open-source project
Normalized one-liner
shell script to llvm compiler
Manually corrected
False

Could you build this?

No Compiling shell script syntax down to LLVM bitcode requires building an advanced compiler frontend, resolving bash's untyped runtime dynamics, and targeting LLVM primitives. This demands expert-level knowledge of compiler design, static analysis, and LLVM backend APIs.

What it would actually take: A functioning compiler needs a full Bash/POSIX shell parser (handling parameter expansion, command substitution, subshells), an inference engine to lift dynamically typed shell semantics into static operations, an IR lowering layer, and an LLVM backend (via inkwell or llvm-sys). The hard part is translating POSIX process models (pipes, forks, signal handling) and dynamically evaluated strings into high-performance, safe machine code. This requires deep systems programming and compiler toolchain development skills.

Discussion

13 comments analyzed.

Competitors mentioned: Python (for verbose scripting), Go (for systems programming), Deno with $ template literals, Bun (shell execution), PowerShell

Concerns raised: Only supports u8 arrays, lacks Unicode support, Parser implementation appears incomplete/skeleton with hypothetical benchmarks only, Security through Omission model not practically useful, Verbose syntax less readable than shell piping (A|B|C), Mandatory structured array arguments worsen readability vs optional approach

Feature requests: Support both mandatory and optional argument array formats for readability, Multiple error handling modes beyond strict POSIX contracts, Preserve original Bash behavior (unquoted variable expansion, word splitting) or enforce stricter semantics explicitly, Built-in commands to replace process launches for better performance

Competitors

Other products that read as similar to this one — 550 launches clear the similarity bar, closest 8 shown.

Attention rank: #210 of 551 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 49 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a dev tools tool for Sales yet.