Geul: Korean SOV Programming Language

Picture this: a language where arguments bind via particles, not position, mirroring Korean's SOV flow. Geul does it – and on Intel Ultra 5 hardware, it sieves 1M primes in just 10ms, 1.3x off MSVC-optimized C.

Geul: The Korean SOV Language That Sieves 1M Primes in 10ms, Nipping at C's Heels — theAIcatchup

Key Takeaways

  • Geul uses Korean particles for flexible argument binding, true to SOV grammar.
  • Self-hosting compiler with hand-written x86 backend delivers near-C performance.
  • Prototype stage but proves grammar-native languages are viable beyond keyword swaps.

10ms. That’s Geul sieving 1 million primes on an Intel Core Ultra 5 226V – median of five runs, beating Python by 16.7x while trailing MSVC /O2 C by a mere 1.3x.

Geul programming language doesn’t mess around. It’s the first to genuinely embrace Korean’s SOV grammar – subject-object-verb, with particles dictating roles – instead of slapping Hangul labels on English syntax.

Here’s the creator’s pitch, straight up:

Korean is structurally different. It’s SOV (Subject-Object-Verb), and meaning is carried by grammatical particles attached to words — not by word position.

Spot on. Most ‘international’ langs? Lazy keyword swaps. if to si. Grammar? Still SVO, mentally taxing for native Korean speakers who think SOV.

Why Design Around Particles, Not Positions?

Think add(5, 3). Position screams ‘left, then right’. In Geul? 5를 3에 더하다. 5-[object] 3-[to] add-[verb]. Particles rule. Reorder freely – meaning holds.

Function sigs declare particles: [정수 왼쪽을 정수 오른쪽에 더하기]는 -> 정수. Parser matches ‘을’ to left arg, ‘에’ to right. No position fights.

Brilliant for Korean devs. But here’s my take: this isn’t just localization candy. It’s a blueprint for grammar-native langs everywhere. Remember APL in the ’60s? Built for math notation, ignored English linearity – birthed array langs still kicking. Geul could do the same for Asia’s 1.5B non-English speakers, forcing Big Tech to rethink i18n beyond emojis.

And performance? No joke.

Can Geul’s Compiler Outpace Hype?

Self-hosting. Geul compiles Geul. Bootstrap binary spits SHA256-fixed output matching source compile. Zero deps in native backend – hand-writes PE headers, x86-64 machine code.

Optimizations pack punch:

  • Compare-branch fusion: cmp+jcc, direct emit.
  • Register pinning: loops hug callee-saved regs.
  • Peephole: nukes dead stores, copy spam.
  • Loop-invariant motion.
  • Tail calls to jmp.

Benchmarks tell the tale:

Benchmark Geul C /O2 ratio
fib(40) 464ms 321ms 1.45x
Sieve 1M 10ms 8ms 1.30x
Bubble 30k 1564ms 564ms 2.77x

Bubble sort lags – nested loops thrash registers, inner var evicts. Fixable. Still, fib recursive? 15.9x Python. Sieve near-C. For v0.7.1? Impressive.

Morpheme magic at parse: Korean verbs conjugate wild. 더하다 (add) strips to 더하기 (adding) via recursive analyzer. Compile-time only.

Static types? Ironclad. 정수 값 = "문자열"? Build fail. Checks decls, assigns, returns, calls.

What’s Under the Hood – And Where’s It Weak?

Pipeline: .글 → morphemes → recursive descent → AST → 3-address IR → C transpile or native x86.

Windows only now. Linux ELF incoming. Stdlib? Slim: 9 modules, 62 fns. No packager yet. VS Code LSP – syntax, F5 run, autocomplete. Playground: geul-web.vercel.app/playground. GitHub MIT: github.com/wwoosshh/geul-lang.

Weak spots scream prototype. Bubble sort flop hints immaturity in reg alloc. No GC? Manual mem? Docs skimpy – playground helps, but onboarding’s rough for non-Korean speakers.

Yet.

This proves SOV langs aren’t gimmicks. Korean market? 50M speakers, booming dev scene (Coupang, Kakao). If Geul hits 1% adoption there, it’s validation for grammar-first design. Prediction: by 2026, expect forks for Japanese (SOV too), Turkish. Wasm target? Game over for English-centrism.

Corporate spin? None here – solo dev, open source pure. No VC fluff.

Look, English syntax dominates because history, not superiority. Geul flips the script. Devs worldwide – try the playground. Feels alien? Good. That’s progress.

Is Geul Ready for Real Work?

Not yet. But trajectory? Steep. 18 releases to v0.7.1. Self-hosting seals credibility.

Bubble sort aside, sieve/fib show backend chops. Particle binding scales – imagine dataflow graphs, args reorder for cache.

Critique time: perf gaps in sorts scream for better alloc. Add GC, threads? Watch ratios flip.

Bold call – Geul sparks ‘grammar wars’. Like Vim/Emacs, but syntax. English wins inertia; locals win cognition.

Worth watching.

**


🧬 Related Insights

Frequently Asked Questions**

What is Geul programming language?

Geul is an open-source language designed for Korean SOV grammar, using particles for argument roles instead of position. Self-hosts to x86-64, rivals C speeds.

How fast is Geul compared to C?

In benchmarks on Intel Ultra 5: 1.3x slower on sieve, 1.45x on fib, 2.77x on bubble sort vs MSVC /O2 C. Crushes Python.

Where can I try Geul?

Browser playground at geul-web.vercel.app/playground. GitHub: github.com/wwoosshh/geul-lang. VS Code extension available.

Elena Vasquez
Written by

Senior editor and generalist covering the biggest stories with a sharp, skeptical eye.

Frequently asked questions

What is Geul programming language?
Geul is an open-source language designed for Korean SOV grammar, using particles for argument roles instead of position. Self-hosts to x86-64, rivals C speeds.
How fast is Geul compared to C?
In benchmarks on Intel Ultra 5: 1.3x slower on sieve, 1.45x on fib, 2.77x on bubble sort vs MSVC /O2 C. Crushes Python.
Where can I try Geul?
Browser playground at geul-web.vercel.app/playground. GitHub: github.com/wwoosshh/geul-lang. VS Code extension available.

Worth sharing?

Get the best AI stories of the week in your inbox — no noise, no spam.

Originally reported by Reddit r/programming

Stay in the loop

The week's most important stories from theAIcatchup, delivered once a week.