DEV Community

Yuki Nishikawa
Yuki Nishikawa

Posted on Edited on

What if React never needed JavaScript? Introducing NO JS 🧠

NO JS – A Syntax Operating System for the Web

What if you could build full web apps — with no JavaScript at all?

🧪 Try the Playground

🌐 GitHub Source


✨ The Idea

NO JS is a meaning-driven syntax OS.

You write .nojs files that describe structure, state,

and flow — then compile them to pure HTML using Zig.

page "home" {
  state.username = "Yuki"
  div {
    h1 { text "Welcome, {username}" }
  }
}
⭐ Must Read: yukinisihikawa/what if react never needed javascript introducing no js gp - Kapook Update 2025 ⭐ Must Read: yukinisihikawa/what if react never needed javascript introducing no js gp - Kapook Update 2025

Compile it:

nojs build examples/hello.nojs
⭐ Must Read: yukinisihikawa/what if react never needed javascript introducing no js gp - Kapook Update 2025 ⭐ Must Read: yukinisihikawa/what if react never needed javascript introducing no js gp - Kapook Update 2025

And get this:

<div><h1>Welcome, Yuki</h1></div>
⭐ Must Read: yukinisihikawa/what if react never needed javascript introducing no js gp - Kapook Update 2025 ⭐ Must Read: yukinisihikawa/what if react never needed javascript introducing no js gp - Kapook Update 2025

No JavaScript. No runtime. No framework.

💡 Why I Built It

Modern web tools are amazing — but what if we could write

the web with just meaning?

🚀 Live Demo

🧪 Try NO JS

Try editing .nojs code and see instant HTML output.

No build tools, no client-side JS.

🧠 Philosophy

Code tells machines what to do.

Syntax tells the world what you mean.

Would love thoughts, ideas, or reactions 🙌

This is still v0.1 — just the beginning!

Top comments (3)

⭐ Must Read: yukinisihikawa/what if react never needed javascript introducing no js gp - Kapook Update 2025
 
webjose profile image
José Pablo Ramírez Vargas •

You're just exchanging one language for another. Word of advice: Whenever you create a POC (proof of concept), work it a little bit more before rushing into promoting, probably thinking "I'll get 1000 stars!, this is a billion-dollar idea". Hold your horses a bit. Maybe it is a billionaire idea, but work it out first.

The repository is not even one day old. People are not going to jump on this over a repository that has no proven track.

Anyway, the bottom line is: POC's are not for the general public. Create it, then test-drive it, then kill the bugs, then repeat for increasingly complex cases, and above all: Be critic and realistic:

I am pushing a new language to developers. Will developers want to learn it? What will it take for developers to learn it? Am I really gaining something with this new language? Is it easier, or does it significantly reduce time-to-prod?

Etc. Those are the kinds of questions you should be asking before even thinking about promoting your idea. Of course, in my opinion. Feel free to differ.

⭐ Must Read: yukinisihikawa/what if react never needed javascript introducing no js gp - Kapook Update 2025
 
yukinisihikawa profile image
Yuki Nishikawa •

Thanks for this — you're 100% right that launching early has tradeoffs.
But I also believe that language ideas are meant to be tested in public, especially when they challenge norms.

I'm not claiming it's ready for production. I'm asking:
"What if we could write the web with just meaning?"

Appreciate your thoughts. This is just v0.1 — but the fire’s real.

⭐ Must Read: yukinisihikawa/what if react never needed javascript introducing no js gp - Kapook Update 2025
 
yukinisihikawa profile image
Yuki Nishikawa •

Let me know if you have thoughts or feedback — or if you’d like to see @click, if, or component syntax next!