xodn348

I had unused token in claude code so that I wanted burn that overnight.

Three agents were writing the future with 3 different perspective. It turned out that human kind did not perish but still had same problem between humans again for 200 years.

Let me have a star if you enjoy this post.

Thank you.

yes, it was flagged to LLM writing somehow. I wonder if this post can be seen others after the flag. Thank you for letting me know!

Thanks for the info!

haha thanks

Let me have fun with it. Thanks

Hope you enjoy your life and time.

I did not understood the meaning of your words.

This was what I was targeting. Thanks

haha great prose

I'm doing what people wants. Thanks!

/destiny compat <partner birth> <city> <m|f>

do it now.

Auto-run on session start (optional) added. Please check it out!

I actually did not use prompts here. It is actual calculation from the python lunar and it cast the result to LLM which you use. The LLM has the old books such as giving you your fortune following lunar year calculation. Have a fun with it!

fair points. I will take a look at it

This is my fun project! Not a profitable entity. Thanks

Just edited readme as well

That's a fascinating idea! Hangul is indeed compositional — 한 = ㅎ + ㅏ + ㄴ — so in theory you could assign meaning to individual jamo components.

But in practice, breaking syllables into jamo would make keywords less readable, which goes against Hangul's design goal. And considering how AI-assisted coding works today, fully named descriptive keywords actually reduce errors — LLMs perform better with explicit, unambiguous tokens than with cryptic symbol compositions.

So Han leans toward more descriptive Korean keywords rather than shorter symbolic ones. Readability over brevity.

Interesting direction to think about though — thanks for the question.

I agree with your opinion and I was wonder how the Korean could be used in the world with full of Eng. Thanks for your feedback!

That is a fair feedback and I have known those languages which are very reasonable and fairly designed language. But I wanted to more focused on translated into rust for english speakers first, which would make bigger user for this language. Thanks for your feedback!

I personally don't know Hanja at all, and I think that's common for most younger Koreans. Korean did borrow from Chinese characters historically, but it's similar to how English was influenced by Dutch, German, French, and Latin — each language developed independently.

Korean has its own pure Korean words (순우리말) as its foundation, and borrowed some Chinese-origin vocabulary on top of that.

Hangul was specifically created so people wouldn't need to learn Chinese characters.

So Han's keywords use native Korean words where possible — it fits the spirit of Hangul itself.

Honest answer: right now it's mostly a keyword translation with English-like syntax order. Korean is SOV (subject-object-verb) but Han follows English SVO order — 목록.추가(값) reads like "list.add(value)" not the Korean natural order. Changing that would require a fundamentally different syntax design, which is an interesting challenge for the future.

That said, a few things do lean into Korean specifically:

- Method names are real Korean verbs: .추가() (add), .삭제() (delete), .분리() (split)

- Error messages are in Korean

- The REPL prompt is 한> and exit command is 나가기 (literally "go out")

Good question — it pushed me to think about what makes this more than just s/function/함수/g.

This tons of Eng documents and contents cannot be translated once but this project is trying to use another language for future use. Thanks for the comment, though.

Haha, using Eng has been reasonable for decades. Thank you very much of your comments.

Thank you for your empathy. English has been the one of the most frequent languages for globe so that it is reasonable to Eng in many coding project, though.

Ha, neat trick. But macro substitution and a purpose-built language are very different — Han has a full pipeline (lexer → parser → AST → interpreter + LLVM codegen) designed around Korean from the ground up.

Error messages, REPL, LSP hover docs are all in Korean. You can't get that from #define 만약 if.

Force for good be with you

funny examples, though.

Good point about compactness — 실명인증계정생성 vs AbstractVerifiedIdentityAccountFactory is a real example where Korean shines.

One distinction though: Han uses actual Korean words, not transliterations. 함수 means "function" in Korean, 만약 means "if" — they're real words Korean speakers already know.

Your example uses transliterations like 펀크 and 아래이 which would look odd to a Korean reader. That difference matters for readability.

The fact that you're already thinking about it means you can do it. Go for it!

Just added that link to the README — it fits perfectly in the "Beauty of Hangul" section.