Login

u/cladamski79

▲ 0 r/Python

Hica in comparison to Python

Hej,

I've been working on a language called hica and Python has been one of its inspirations, especially working with lists. I have created a Hica vs. Python comparison at https://cladam.github.io/hica/docs/hica-vs-python and the verdict is ofc Python 🙂

From my conclusion:

>Python is the safe, proven choice with the largest ecosystem and lowest barrier to entry.

>hica emphasises foundations like immutability, type safety, pattern matching, and explicit error handling. Students who learn hica carry these patterns into Python, Rust, TypeScript, or whatever they use next.

>Why not both? Start with hica to build the foundations, then move to Python with a head start on the concepts that matter most.

What does this community think? My Python is a bit rusty, any feedback is welcome.

reddit.com
u/cladamski79 — 3 days ago
▲ 1 r/ADHD_Programmers

hica, a statically typed, expression-oriented language targeting Koka

Hej,

I’ve always wanted to design a language, but the "plumbing" (backends, GC, and low-level infrastructure) is a massive barrier to entry (for me at least...). I have done some tries but it has been daunting, my ADHD makes me impatient... So, I decided to bypass this by targeting the Koka compiler as my backend. By emitting .kk source, hica inherits Perceus deterministic memory management and a robust algebraic effect system while providing a distinct, approachable syntax.

I used a Genie (what I call my GenAI model, thanks Kent Beck for the term) as a pair-programming partner. I maintain the backlog and iterate until it’s right. It lets me focus on the design decisions; the Genie handles the mechanical parts. It’s been superfun, and a breath of fresh air compared to grinding through boilerplate alone.

Technical Architecture The compiler (transpiler) is a multi-stage pipeline:

  1. Lexing & Parsing: Uses a Pratt parser to handle expression-oriented syntax.
  2. Type Checking: Implements Hindley-Milner unification. It infers types across function boundaries, making annotations optional.
  3. Effect Tracking: Every compiler phase is internally effect-tracked.
  4. Emission: Translates the desugared AST into Koka source, which is then compiled to native C11, JS, or WASM.

Key Features

  • Expression-First: if, match, and blocks all return values. There is no return keyword.
  • Safety thsnks to Koka: Leverages Perceus for Functional But In-Place (FBIP) updates, providing the safety of immutability with high-performance mutation.
  • Transparent Tooling: Includes a full CLI (hica check for effects, hica fmt, hica test) built on my custom Koka libraries, klap and kunit.

Verification & Quality To make sure my language keeps its promise, I’ve implemented over 500 tests (using kunit) covering the lexer, parser, checker, and codegen.

Links

Would love to get feedback on the language from this community.

u/cladamski79 — 5 days ago
▲ 0 r/rust

hica in comparison to Rust

Hej,

I've been developing my own language called hica and Rust has been one of its inspirations. I have created a Hica vs. Rust comparison at https://cladam.github.io/hica/docs/hica-vs-rust/ and the verdict is ofc Rust :), see hica as a gateway to Rust.

From my conclusion:

>If you already know Rust, you’ll read hica code fluently. If you’re learning hica first, you’ll find that many of its patterns (Result types, match expressions, immutability) transfer directly when you’re ready for Rust.

What does this community think?

reddit.com
u/cladamski79 — 5 days ago