Script your frontend in Ring.
Not in JavaScript.

The same page, two ways

A name field, a greeting, a click counter. Below are the two versions of the very same page — line for line, same length, same order — so the only thing that differs is how the logic reads.

<input id="guest">                     // the markup, shared by both
<button>Greet</button>
<div id="hello"></div>

<script src="ringscript.js"></script>   // Ring only: once per page
<script>RingScript.boot()</script>

let clicks = 0;

document.getElementById("go")
    .addEventListener("click", function () {
        const input = document.getElementById("guest");
        let name = input.value;
        if (name === "") { name = "stranger"; }

        document.getElementById("hello").textContent =
            "Ahlan, " + name + "!";

        clicks = clicks + 1;
    });

nClicks = 0

func Greet


    cName = Page(:getvalue, [ :id = "guest" ])

    if cName = "" cName = "stranger" ok

    Page(:settext, [ :id = "hello",
        :text = "Ahlan, " + cName + "!" ])

    nClicks++

No listener to register, no node to look up twice, no closure to reason about: the button says ring.call('Greet') and the function is called Greet. That is the whole trick — and it holds as the page grows.

What you get

What people build with it

The reason this exists: business applications whose rules keep working when the connection does not. Two of them run on this site — a field-sales order pad with a switch marked Cut the connection, and a 20,000-record register measured against how a page has to feel.

The interface stays plain HTML and CSS. Your server stays in whatever language it is already written in. What moves to Ring is the part that decides — pricing, limits, validation — because that is the part that must not need a network.

Three steps, no ceremony

1. Get the two files. Easiest is the starter kit — a folder that already runs, with a launcher for your system. Or copy ringscript.js and ringscript.wasm next to your own HTML; with Ring installed, ringpm install ringscript from mayouni fetches them.
2. Boot it with one line — RingScript.boot() — which starts the VM and runs every <script type="text/ring"> block on the page.
3. Write Ring. Call functions from your markup with ring.call('Name'); read and write the page with Page(). Build an analog clock walks through all three, start to finish.

Trust, measured

"It runs Ring" is a claim worth checking, so it is checked continuously against the native interpreter — the whole official sample set and every code block in Ring's documentation.

And it races the fastest small interpreters there are

The same scenarios, run through Lua 5.4 and QuickJS — two C interpreters compiled to WebAssembly, same weight class, same architecture — under the same measurement discipline. The point was never to win; it was to find out where the headroom was. Every loss is published with its cause, and the causes became the work.

The row that matters most has no winner at all: 10,000 evaluations with errors mixed in grow nobody's heap, and 1,200 hostile inputs kill nobody — for all three engines. That parity is what a year of running unattended in a branch office actually needs.