Skip to content
Published on

Niche & Emerging Programming Languages 2026 — Crystal / Nim / V / Carbon / Mojo / Pony / Hare / Roc / Hylo / Vale / Koka / Tcl 9 / Fortran 2023 Deep Dive

🇰🇷KO🇺🇸EN🇯🇵JA
Split View필사 모드
Authors

1. A 2026 Map of Niche & Emerging Languages — Systems / FP / Safety / Domain

As of May 2026, the world outside the mainstream (Python, JavaScript/TypeScript, Java, C#, Go, Rust, C/C++, Swift, Kotlin) is still a rich ecosystem. The "niche and emerging" languages we cover here all sit below 1% of GitHub users, outside TIOBE top 30, and in the middle band of the RedMonk plot — yet for specific workloads or philosophies they remain better answers than the majors.

Four axes capture them.

CategoryRepresentative languagesCore value
Systems / nativeCrystal, Nim, V, Carbon, HareRuby/Python-like syntax with native compilation, or C/C++ successors
Safety / ownershipPony, Hylo, Vale, Inko, KokaNew safety models: borrow, region, capability, effect
FunctionalRoc, Racket, Common Lisp (SBCL)Strong types or strong macros, research-oriented
Domain / historicalMojo, Fortran 2023, Tcl 9, OpenSCAD, J, Forth, Modula-3AI acceleration, scientific computing, embedded, 3D, array

The axes are not mutually exclusive. Mojo is systems + AI domain, Roc is functional + safety, Hylo straddles systems + safety. Still, it is a useful starting point.

Three myths to flag up front:

  • "Niche means dead" is wrong. Common Lisp has been alive with SBCL since the 1980s, and the Fortran 2023 standard just passed.
  • "Newer means better" is also wrong. V (Vlang) has stayed in beta for seven years since 2019.
  • Almost no niche language can beat the depth of library, hiring, and AI-assist coverage of a major language. But there are still domains where "this is the right answer".

2. Crystal — Ruby-like Compiled (1.14)

Crystal was first released in 2014 with the slogan "Ruby's syntax, C's speed", reached 1.0 in 2021, and shipped 1.14 in November 2024. As of May 2026, 1.14 is the stable line and 1.15 is in RC.

Key features:

  • LLVM-based AOT compiler, static types with strong inference
  • Ruby-like syntax (blocks, symbols, but a missing method is a compile error rather than NoMethodError)
  • Green threads (fibers) plus Channels — concurrency model very close to Go
  • Null safety: nil is its own type, the compiler tracks it as a union

A short example:

# fibers + channels — very close to Go
ch = Channel(Int32).new

spawn do
  ch.send 42
end

puts ch.receive  # => 42

Where Crystal fits:

  • Refactoring a Ruby on Rails backend into static types and compiled performance
  • Workloads where rewriting Ruby code wholesale is painful (Sidekiq workers, CLI tools)
  • Real users: Manas Tech, some NeoVim plugins, some fintech backends

Honest limitations:

  1. Multi-threaded execution is still experimental (the -Dpreview_mt flag). On 1.14 in 2026, the default model is single-threaded fibers.
  2. The library ecosystem is thinner than Ruby's or Go's. ORMs are basically Granite, Jennifer, and Avram.
  3. Windows support came late and is still not a first-class citizen.

3. Nim — Python-like Compiled (2.x)

Nim aims for "Python-like syntax compiled through a C/C++ backend" and started in 2008. Nim 2.0 shipped in August 2023; as of May 2026 the stable line is 2.0.x and the dev line is 2.2.x.

Features:

  • Indentation-based syntax (Python-like) with static types
  • C, C++, ObjC, and JavaScript backends — the same code can target both web and native
  • Compile-time macros (macro, template) — Lisp-level metaprogramming
  • ARC/ORC memory management (default since 2.0) — no GC, only a cycle collector

Key 2.0 changes:

  • Default memory management unified on ORC (the old mark&sweep refc is now legacy)
  • View types (openArray, lent) start to bring borrow-like safety
  • Strict mode for explicitly undefined variables

A snippet:

import std/[asyncdispatch, httpclient]

proc fetch(url: string): Future[string] {.async.} =
  let client = newAsyncHttpClient()
  defer: client.close()
  result = await client.getContent(url)

echo waitFor fetch("https://example.com")

Nim's real strength is compile-time macros. Status's Ethereum 2.0 consensus client Nimbus is the flagship example, generating SSZ serialisation code at compile time via Nim macros.

Weaknesses:

  1. Nearly invisible on Korean/Japanese job markets — think about how learning Nim connects to your next role.
  2. The standard library is a little disorganised for historical reasons.
  3. The community is slightly smaller than Crystal's.

4. V (Vlang) — The Controversial Eternal Beta

V was announced in 2019 with very broad promises: faster compile than Go, safety like Rust, no garbage collector, even an interactive GUI. As of May 2026 the official version is 0.4.x — its seventh year in beta.

Why it is controversial:

  • Many launch-era promises (1 MB hello world, one-second compile, automatic memory management, "C-level" performance) have been revised or remain incomplete over the years.
  • A part of the community has long argued "marketing runs ahead of technology" — many Hacker News threads from 2019 to 2021 capture this debate.

Even so, V is still alive:

  • The syntax looks a lot like Go (C-style, short keywords).
  • It transpiles to C and compiles through any C compiler — with TCC the compile is genuinely fast.
  • The standard library bundles GUI (vlang/ui), web (vweb), and ORM (vorm).

Example:

struct User {
  name string
  age  int
}

fn main() {
  users := [User{'Anna', 30}, User{'Bob', 25}]
  for u in users {
    println('${u.name} is ${u.age}')
  }
}

When should you use V? Honest answer: in 2026 it is hard to recommend for production. For learning, experimentation, or small CLIs, the fast compile and terse syntax are fun. But before betting a system on V-only features (auto-free, built-in ORM), Crystal, Nim, Go, or Rust will almost always be a safer choice in the same niche.

5. Carbon (Google) — C++ Successor, Slow Going

Carbon was announced by Google's Chandler Carruth at CppCon 2022 as a "successor to C++". As of May 2026 carbon-language/carbon-lang is still active, but the official stage is "experimental" — it has not yet reached even a 0.1 alpha.

Design intent:

  • Bidirectional interop with C++ — import C++ libraries directly from Carbon, call Carbon from C++.
  • Shed the 30 years of design debt that C++'s ABI and syntax carry.
  • Opt-in memory safety like Rust — choose safe mode or fast mode per module.

A snippet:

package Geometry api;

class Circle {
  var r: f64;
  fn Area[me: Self]() -> f64 { return 3.14159 * me.r * me.r; }
}

fn Main() -> i32 {
  var c: Circle = {.r = 2.0};
  Core.Print(c.Area());
  return 0;
}

Status as of May 2026:

  • The toolchain/ self-compiler is in alpha — some examples build, but the standard library is incomplete.
  • The spec accumulates in the design/ directory on GitHub as Markdown — interesting design-review reading.
  • Google has announced small in-house pilots but has not published the actual internal adoption footprint.

Realistic take: Carbon is not a "language you write today", it is a "telescope into where the C++ camp is going". Rust is safer, Mojo reached GA faster, but for very large C++ ABI-bound codebases (Chromium, Android, some game engines) Carbon could still be meaningful.

6. Mojo (Modular) — Python Superset (2024.8 GA)

Mojo is built by Modular, the company founded by LLVM/Swift's Chris Lattner. The first public reveal was in May 2023, and stable GA (1.0) arrived in August 2024. As of May 2026 the stable line is 24.x — released quarterly.

Mojo's promises are large:

  • Python superset — import existing Python code directly.
  • Systems programming — MLIR-based, C-level performance, SIMD/GPU intrinsics.
  • AI acceleration — target NVIDIA, AMD, and Apple Silicon GPUs from the same code.

Snippet (simplified):

from sys.info import simdwidthof
from algorithm import vectorize

fn dot[type: DType, size: Int](a: SIMD[type, size], b: SIMD[type, size]) -> Scalar[type]:
  return (a * b).reduce_add()

fn main():
  var a = SIMD[DType.float32, 4](1.0, 2.0, 3.0, 4.0)
  var b = SIMD[DType.float32, 4](5.0, 6.0, 7.0, 8.0)
  print(dot(a, b))  # 70.0

Modular's central weapon is the MAX (Modular Accelerated eXecution) platform — Mojo plus MLIR plus an inference engine packaged together. As of 2026 you can write OpenAI-compatible inference servers directly in Mojo, and published benchmarks show MAX-compiled PyTorch graphs hitting 1.5x to 3x the throughput of stock PyTorch on the same GPU.

Strengths:

  • Python compatibility — import a subset of existing NumPy/PyTorch code as-is.
  • GPU as a first-class citizen — single code surface across CUDA, ROCm, and Metal.
  • A company stands behind it — Modular has raised through Series B and is focused on AI infra.

Risks:

  • Language spec and standard library still move fast — some APIs broke between 24.1 and 24.3.
  • The compiler is not open source (a phased open-sourcing was announced in 2024, but as of May 2026 the compiler proper remains closed).
  • The licence is "free to use, restricted to redistribute" — fine for learning, but check your company's policy.

7. Pony — Capabilities-Secure

Pony is an actor language by Cambridge alumnus Sylvan Clebsch, designed so that "data races are impossible at compile time". As of May 2026 ponylang/ponyc is actively maintained and 0.58.x is the latest stable.

The core idea — Reference Capabilities:

  • Every reference carries one of six capabilities: iso, val, ref, box, tag, trn.
  • iso means isolated (safe to send to another actor); val means immutable; ref means mutable but actor-local.
  • The compiler tracks these so any code that could race simply does not compile.
actor Counter
  var _n: U32 = 0

  be inc() => _n = _n + 1
  be get(promise: Promise[U32]) => promise(_n)

actor Main
  new create(env: Env) =>
    let c = Counter
    c.inc()
    c.inc()

Where Pony shines:

  • High-throughput actor systems (message passing). WallarooLabs's data streaming engine built on Pony (2017 to 2020) is the most famous industrial example.
  • Domains where data races themselves are business risk — finance, some embedded.

Limits:

  • WallarooLabs wound down in 2021, taking the biggest industrial sponsor with it. Sylvan Clebsch and a few engineers at Microsoft have kept the community going since.
  • The learning curve is steep — keeping six capabilities in your head is a real cost.
  • The library ecosystem is small.

Even so, if you want to see "an actor model with no data races, as code", Pony remains worth reading.

8. Hare (Drew DeVault) — Suckless C Alternative

Hare is a "minimal, C99-compatible systems language" started by sr.ht founder Drew DeVault. The first public release was April 2022; as of May 2026 0.25.x is the latest stable. 1.0 is deliberately kept distant.

Hare's philosophy (suckless-influenced):

  • A small, explicit standard library.
  • No GC, no exceptions, no macros — simplicity like C.
  • Its own assembler and linker (harec plus qbe) — minimal external dependencies.
use fmt;

export fn main() void = {
  for (let i: int = 0; i < 5; i += 1) {
    fmt::printfln("hello {}", i)!;
  }
};

Among many "C replacements", Hare's specifics are:

  • GPLv3 licensed — reflecting Drew DeVault's free-software stance.
  • Aims to build its own OS (Hare OS, Helios) — language and OS evolving together.
  • No Windows or macOS support — Linux, BSD, and Plan 9 only.

Realistic position:

  • A good study resource for systems programming — see syscalls and memory without the complexity of C++ or Rust.
  • Fits minimal-system projects (your own OS, your own init, your own compiler).
  • The hiring market is effectively zero.

9. Roc (Richard Feldman) — Functional, No Built-in Errors

Roc is a functional language by Richard Feldman, well known from the Elm community. As of May 2026 it is still 0.x (no official 1.0), but 0.0.x releases are active and some companies use it for internal tooling.

What sets Roc apart:

  • Pure functional with strong Hindley-Milner inference — Elm/Haskell family.
  • "No built-in errors" — build errors are the compiler's job and runtime errors are the platform's responsibility (the language itself has no exception concept).
  • Platform / Application split — the same Roc code can run on CLI, web, AWS Lambda, etc., via different platforms.
app "hello"
  packages { pf: "https://example.com/basic-cli/platform" }
  imports [pf.Stdout]
  provides [main] to pf

main =
  Stdout.line "Hello, Roc!"

Use cases:

  • CLI tools, static site generators, some Lambda workloads — bringing Elm-style safety to the server.
  • Richard Feldman's NoRedInk is the headline user (Elm plus some Roc).

Honest limits:

  • 1.0 is still far away — the language spec is not yet stable.
  • The standard library is intentionally minimal — platforms fill in the rest.
  • AI-assist tools (Copilot et al.) are weak at writing Roc.

10. Hylo (formerly Val) — Carbon-Adjacent, Value-Oriented

Hylo started life in 2020 as "Val", aiming for the same "C++ successor" seat as Carbon. It was renamed Hylo in 2023 to avoid a clash with Vale. As of May 2026 hylo-lang/hylo is still in 0.x.

Core design:

  • Value semantics by default — every variable is a value, and references appear only when you explicitly borrow.
  • Generic programming as a first-class citizen — aims to combine the good parts of C++ templates and Rust generics.
  • Mutable value semantics — a softer borrow model than Rust's.
// Hylo's syntax visually resembles Carbon (both belong to the C++ successor camp).
fun main() {
  var nums = [1, 2, 3]
  inout last = nums[2]
  &last = 42
  print(nums)  // [1, 2, 42]
}

(Note: the snippet above is pseudo-code for flavour. The real Hylo syntax is still evolving.)

Assessment:

  • Clear academic value — what does a "safe systems language built on value semantics" look like?
  • Hylo and Carbon compete for the same "C++ successor" slot, but Hylo leans academic and Carbon leans pragmatic.
  • Industrial adoption is negligible.

11. Vale (Evan Ovadia) — Region-Based Borrow

Vale is a one-person project led by Evan Ovadia, but its design draws academic attention. As of May 2026 it sits in 0.x.

The hook — Region-based borrow checking:

  • Rust's borrow checker is "one mutable reference at a time", a strong invariant.
  • Vale introduces "regions" — explicitly open a region and apply a consistent set of borrow rules inside, with different rules outside.
  • Result: more expressive than Rust, with data races and iterator invalidation caught at region boundaries.

Vale also explores intriguing ideas like "Higher RAII" — not just RAII, but the compiler tracking destructor call order.

The code surface changes quickly, so I will not reproduce it here. If you are curious, read the vale.dev blog post "Single Ownership and Memory Safety without Borrow Checking, RC, or GC".

Industrial adoption: effectively zero. But a good reference for anyone studying borrow models.

12. Inko — Concurrent + Safe

Inko is a concurrent language by Yorick Peterse from the Netherlands. As of May 2026 it is in 0.x, with active development.

Features:

  • Actor model plus Rust-like ownership.
  • A bespoke compiler IR with an LLVM backend.
  • Async I/O as a first-class citizen — its own runtime abstracts over epoll/kqueue.
// Inko's syntax gives a very Rust-like impression.
import std.stdio.STDOUT

class async Main {
  fn async main {
    STDOUT.write("Hello, Inko!\n")
  }
}

Inko's slot:

  • Direct competitor to Pony — the "safe + concurrent + native" space.
  • Lighter than Pony's capabilities, more focused than Rust on concurrency.
  • The one-person-project caveat — corporate risk is almost entirely a single contributor.

13. Koka (Microsoft) — Effect Handlers

Koka is a research language led by Daan Leijen at Microsoft Research. As of May 2026 it is on its 3.x line.

Koka's real innovation: algebraic effects with effect handlers.

  • A function's type signature explicitly states which effects it can raise.
  • Exceptions, async, generators, state, nondeterminism are all expressed through the same effect-handler mechanism.
// Koka's syntax sits in the ML/Haskell family.
fun greet(name : string) : console ()
  println("Hello, " ++ name)

(This fence is for visual reference; Koka's official syntax keeps evolving.)

Use cases:

  • Academic — the most mature language demonstrating effect handlers as a practical primitive.
  • Wide influence — OCaml 5's effects, Java's Loom, Swift's typed throws are all variations on this theme.
  • No industrial adoption to speak of, but the best entry point if you want to see what a functional language with an effect system looks like.

14. Common Lisp (SBCL) / Racket — Academic + Research

Two languages that have been alive too long to call "niche", taken together.

Common Lisp + SBCL

  • ANSI standardised in 1984, with no subsequent major revision. Yet it refuses to die.
  • SBCL (Steel Bank Common Lisp) is the most mature open-source implementation — as of May 2026 the 2.4.x line ships quarterly.
  • The macro system (macros, reader macros) is still unmatched. The language that most naturally expresses "code that writes itself".

Real users:

  • Grammarly's core NLP engine has Common Lisp components.
  • ITA Software, now Google Flights, has its search core originally written in Common Lisp.
  • Some research groups at NTT in Japan have published material about using it for domain modelling.

Code:

(defun factorial (n)
  (if (<= n 1)
      1
      (* n (factorial (- n 1)))))

(print (factorial 10))  ; 3628800

Racket

  • A Lisp-family language, direct descendant of Scheme.
  • Renamed from PLT Scheme to Racket in 2007 — it has positioned itself less as "a language" and more as "a language for making languages".
  • As of May 2026 Racket 8.x is current, with racket/cs (Chez Scheme backend) as default.

Uses:

  • Standard tool for undergraduate PL courses (successor to SICP).
  • DSL creation — define a new language with #lang ....
  • Academic research plus some industry domain modelling.
#lang racket

(define (factorial n)
  (if (<= n 1) 1 (* n (factorial (- n 1)))))

(displayln (factorial 10))

15. Tcl 9 (September 2023) — First Major Release in 26 Years

Tcl (Tool Command Language) was created in 1988 by John Ousterhout. Tcl 8.0 shipped in 1997, and 26 years later Tcl 9.0 was released in September 2023. As of May 2026 9.0.1 is the current stable.

Key Tcl 9 changes:

  • 64-bit integers as first-class.
  • UTF-32 encoding, much improved multi-byte and multi-character string handling.
  • Native handling of large data (over 2 GB) — string, list, dict all operate on 64-bit lengths.
  • Tk 9.0 shipped alongside — new widgets, HiDPI support.
puts "Hello, Tcl 9.0!"

set users {alice bob carol}
foreach u $users {
  puts "User: $u"
}

Where Tcl is still alive:

  • EDA (electronic design automation) — Synopsys, Cadence, and Mentor's tools still adopt Tcl as their scripting layer.
  • Network equipment automation — parts of Cisco IOS and NX-OS automation are still Tcl-based.
  • expect — effectively the standard for TUI automation.

16. Fortran 2023 — Scientific Computing in Production

Fortran was the first high-level compiled language, released by IBM's John Backus in 1957. And in May 2026 it remains one of the core languages of supercomputing.

Fortran 2023 (ISO/IEC 1539:2023):

  • Standardisation completed in November 2023.
  • Strengthened generic programming (generic procedures closer to C++ templates).
  • ASYNCHRONOUS attribute, improvements to do concurrent and coarrays.
  • Wider integer and real types in ISO_FORTRAN_ENV.
program hello
  implicit none
  integer :: i
  do concurrent (i = 1:5)
    print *, "Hello, Fortran 2023, iteration =", i
  end do
end program hello

Real usage:

  • Weather models (WRF, CESM), climate models, fluid dynamics (OpenFOAM is C++, but much of the surrounding tooling is Fortran).
  • Ocean simulation, nuclear simulation (US NNSA).
  • LAPACK and BLAS — the roots of essentially every scientific computing library.

Fortran does not go away for a simple reason: almost no compiler beats Fortran on numeric array workloads in both speed and stability, and the cost of rewriting 60 years of validated code exceeds any migration benefit.

17. Modula-3 / J language / OpenSCAD / Forth — History + Curiosities

Short notes in three groups.

Modula-3

  • A systems language built by DEC between 1986 and 1993.
  • Successor to Modula-2, packaging GC, threads, and modules together — earlier than Java did the same.
  • Industrially almost gone, but still cited in OS courses (e.g., SPIN OS) and systems-design literature.

J language

  • Descendant of APL — an array/vector-first language.
  • Still used by some algorithmic traders and statisticians.
  • Code reads almost like mathematical notation (+/ % # is the mean).

OpenSCAD

  • A declarative CAD language for 3D printing.
  • In 2026, still the headline tool in the RepRap and Prusa communities.
// OpenSCAD one-liner
// A box 20 wide, 10 deep, 5 tall
cube([20, 10, 5]);

Forth

  • Created by Charles Moore around 1970 — stack-based, metaprogrammable, embeddable.
  • Still running observatory telescope control, parts of BIOS, and NASA mission probes.
  • Study value — the most extreme example of "a language defining itself".

Factor and Joy are Forth-family stack languages. The academic significance is high.

Plan 9 from Bell Labs

  • Not a language but an OS — yet it took "everything is a file" further than Unix did.
  • The 9P protocol, the Acme editor, and the rc shell remain sources of inspiration.

18. Korea / Japan — Niche Communities

Korea

  • Korean-language material on Crystal/Nim is scattered across awesome-* lists on GitHub and personal blogs. KLDP and "School of AI" (Modulabs) have hosted study groups.
  • Mojo has been covered in NVIDIA AI Day Korea sessions, and a handful of startups have PoC'd it for inference acceleration.
  • Common Lisp and Racket survive in PL conferences and graduate programmes.

Japan

  • Japan historically has deep Common Lisp use — published material exists from NTT research labs, NEC, and game studios (e.g., the older Hyper-FX line).
  • There is no Modular Japan office, but PFN (Preferred Networks) and the team operating the MN-3 supercomputer have publicly expressed interest in new AI languages.
  • Tcl/Tk is still used in Japan for EDA and instrument automation.

19. Which Languages Survive — A 2026 Forecast

An honest five-year forecast:

LanguageProbability of survivingReason
MojoVery highAI acceleration workloads plus Modular's capital plus Lattner's reputation
CrystalMediumSolid subset of the Ruby community, but explosive growth is unlikely
NimMediumBig anchor users like Nimbus
CarbonMedium-lowAlmost no adoption outside Google. Could still be in alpha five years out
VLowSeven years in beta; trust needs rebuilding
PonyLowNo industrial sponsor
HareVery lowDeliberately small, one-person project
RocMediumRichard Feldman's reputation plus the Elm community
Hylo/ValeSurvives academicallyIndustry adoption unlikely
InkoLow-mediumOne-person-project risk
KokaSurvives academicallyBig influence; almost no direct adoption
Common LispSurvivesIf it lived 40 years, it lives five more
RacketSurvivesAcademic tool
Tcl 9SurvivesAs long as EDA is alive
Fortran 2023SurvivesAs long as HPC is alive
Modula-3/J/ForthSurvives in museumsIndustry adoption zero

The best learning path:

  1. First get good at 2 or 3 majors (Python, TypeScript, Go, Rust).
  2. Then read one niche language "for the philosophy" — Mojo (systems + AI), Roc (functional), Common Lisp (macros), Fortran (arrays).
  3. Worry about "can I use this at work" last. Most niche languages have almost no hiring market.

20. References

Discuss on Twitter • View on GitHub