Why LokaScript

hyperscript's design bet is that UI code should
read like a description of what it does:

on click toggle .active on me

No build step, no callback plumbing — the code is its own documentation.
That readability is the reason people use hyperscript at all.

But it has a prerequisite: English. For the many developers who work in
another language, on click toggle .active on me is not self-describing —
it's a sentence in a foreign language that happens to be executable. The
readability advantage, the whole point, arrives with a translation tax.

LokaScript removes the prerequisite. The same behavior, running on the same
engine, written the way a sentence is actually constructed in each language:

on click toggle .active on me

クリック で 私 の .active を 切り替え     (Japanese — SOV)
al hacer clic alternar .active en mi      (Spanish — SVO)
عند النقر بدّل .active على نفسي           (Arabic — VSO)

Grammar transformation, not word substitution

Languages don't share word order. English puts the verb before the object
("toggle the class"); Japanese puts it after (「クラスを切り替え」); Arabic
often leads with it. LokaScript's parser understands SVO, SOV, and VSO
sentence structure, so each translation is idiomatic in its language rather
than English with the words swapped out. That is the difference between code
a Japanese developer reads and code they decode.

No ecosystem isolation

The obvious objection: doesn't writing code in Japanese cut you off from the
English-speaking ecosystem?

No — translation is mechanical and bidirectional. Any LokaScript program
converts to canonical English hyperscript and back. The
pattern library maintains all 164 reference patterns in 24
languages. And the adapter plugin works with
upstream _hyperscript too, so multilingual authoring doesn't even require
switching engines. The artifact stays portable; only the reading experience
changes.

Who this is for

• Learners and classrooms. Readability matters most for beginners, and
  beginners are the least likely to be fluent in English. A student in
  Jakarta or Nairobi can learn event-driven UI in the language they think in.
• Teams that work in another language. Code review, onboarding, and
  maintenance all get easier when the code reads naturally to the people
  doing them.
• Mixed-language teams. The pattern library acts as a shared reference:
  the same pattern, readable by every member in their own language.
• AI-assisted development. The docs API already translates and
  explains hyperscript across languages; code shaped like natural language —
  in any natural language — is a good substrate for working with agents.

Try it

Switch languages on any pattern in the Pattern Browser, or
write and run multilingual hyperscript in the Playground.