Hello HN!I&#x27;m the author of Ant, a JavaScript ecosystem built around a runtime with its own JavaScript engine. Ant also includes a package manager, the ants.land package registry, a platform for deploying and hosting applications, and Ant Desktop for building native desktop apps with web technologies, similar to Electron.The goal is for these pieces to work as one coherent platform while remaining compatible with the wider JavaScript ecosystem. It&#x27;s still early, and I&#x27;d appreciate any feedback on the overall direction or what you&#x27;d like to see from an e2e alternative to the existing JavaScript stacks.P.S. I’ve shared Ant here before as a runtime; since then, it has grown into the broader ecosystem you see today.

Show HN: Ant – A JavaScript runtime and ecosystem

The Birth and Death of JavaScript (2014)

Why Vanilla JavaScript

Bun has an open PR adding shared-memory threads to JavaScriptCore

Show HN: Kyushu – A self-hostable WASM sandbox for JavaScript workers

Show HN: Brain Frog – Can you be random enough for 11 lines of JavaScript?

Satteri: A Markdown pipeline forged in Rust for the JavaScript world

Converting colors in JavaScript at 6B operations per second

GTA 2 ported to JavaScript, with WebRTC P2P multiplayer

De‐Bloating JavaScript

Show HN: Ego lite – why our browser agent writes JavaScript not CLI commands

GSAP – A robust JavaScript animation library built for professionals

This is a model I’ve been thinking about lately. It demonstrates a pattern that I’m wondering could exist, where terminal applications, BBS-style shared user boards, and other expressions of creativity and sharing are created with web technologies but rendered into the terminal and accessed over SSH.I like that this brings back some kind of old days of the internet feeling and uses web technologies but sidesteps the public World Wide Web, even though it’s still on the internet.You can try it out too right now, and I’m thinking about making the self-hosting specialized applications part a first-class thing. But right now, the project is organized as a browser rendering engine, which I spent eight years on since the end of 2018, most of that without AI, writing all the code myself. And then a terminal renderer, which connects to that browser renderer and takes its output and bookkeeping and renders it into the terminal.And that is designed by me, including the layout algorithm, but AI wrote almost all the code. So I am basically a software designer and AI nudger in that one. My flow is essentially like one agent at a time, and I’ll monitor it, nudge it based on my intuitions if it gets stuck or needs help or whatever, and guide it towards the goal. Plus being the designer and decision maker.AI makes a lot of decisions, but I make the most of them. So that’s just describing my flow of how I created this terminal thing, which is roughly around a year old.And originally it was created with Gemini Pro 3.1, which at that time a year ago was sort of the most capable model for complex tasks. And I literally did it on the free AI Studio web application, just like pasting in code listings. Obviously, with agents now, everything is much smoother as a workflow.This demo has some kind of a cap on it, so let me know if it hits that. It probably won’t, but feel free to tell me. And you can self-host it today. Let me know if you want to do that.This text was dictated by me and then had punctuation and paragraphing added, but the wording was not changed.

Show HN: HTML, CSS and JavaScript in the Terminal

Building a plugin system without runtime, storage, or shared JavaScript context

Show HN: JavaScript Crossword – a crossword where the clue = eval(answer)

Show HN: I wrote a Libc-free AOT systems language in JavaScript with no VM

Show HN: Elemental – simple front ends in plain JavaScript

Concurrent JavaScript: It can work (2017)

Hey everyone! I&#x27;ve been working on something called Afterburner: a fast, embeddable JS&#x2F;TS runtime written in Rust, with a capability sandbox baked right in.Scripts run locked down by default: no network, no filesystem, no environment variables. You explicitly grant whatever access a script actually needs, and every call gets hard caps on CPU, memory, and time.The goal isn&#x27;t to replace your existing stack. It&#x27;s to fit cleanly into it:Embed a JS&#x2F;TS engine in your Rust app with a single crate. Run user scripts, plugins, business rules, or edge logic, each call fully sandboxed.
Wrap the tools you already use. Commands like `burn node app.js`, `burn npm test`, `burn bun`, `burn deno run`, and `burn npx tsx` run your existing toolchain under the sandbox. Take an unmodified Express, Fastify, or Hono app and run it with zero ambient I&#x2F;O and a memory ceiling. No code changes needed.
Use the built-in registry at registry.afterburner.sh. Publish with `burn publish`, install with `burn install` or `burn add` dependencies are pinned by content digest. Every package ships with a capability manifest, so installed code is sandboxed by default. It also interops with npm, so you can still pull in npm libraries as needed.
Since nothing gets ambient authority, it&#x27;s also just a clean, practical way to run untrusted code without having to cross your fingers and hope.Repo: <a href="https:&#x2F;&#x2F;github.com&#x2F;afterburner-sh&#x2F;afterburner" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;afterburner-sh&#x2F;afterburner</a> 
Site: <a href="https:&#x2F;&#x2F;afterburner.sh" rel="nofollow">https:&#x2F;&#x2F;afterburner.sh</a> 
Registry: <a href="https:&#x2F;&#x2F;registry.afterburner.sh" rel="nofollow">https:&#x2F;&#x2F;registry.afterburner.sh</a>The full walkthrough like how it works, what it can do, and benchmarks hitting up to ~16.8M rows&#x2F;sec is all in one post. It&#x27;s the best place to start: 
<a href="https:&#x2F;&#x2F;vertexclique.com&#x2F;blog&#x2F;burn-after-reading&#x2F;" rel="nofollow">https:&#x2F;&#x2F;vertexclique.com&#x2F;blog&#x2F;burn-after-reading&#x2F;</a>One licensing note: it&#x27;s source-available under BSL-1.1, which automatically converts to Apache-2.0 four years after each release. 
Free to use for your own projects so go build something.

Show HN: Afterburner – Capability-Sandboxed JavaScript/TS Runtime in Rust

There are too many JavaScript schema libraries, so support only one

JavaScript powers the web - it's **the** most important programming language you need to know as a web developer.

## Exempel 1

For example, We have an array of different objects that can weigh the same or different and are spaced apart from us.
The customer wants the lightest and closest object.

```js
object.sort((a,b)=>a.weigh - b.weigh)

 const lightest=(object[0].weigh);
 let sortDistance=(object[0].distance); 

 for (let i = 0; i< object.length; i++) { 
 if (lightest === object[i].weigh && sortDistance > object[i].distance){
 sortDistance = object[i].distance;
 sortObject.unshift(object[i]);
 }else{
 sortObject.push(object[i]);
 }
 }
```

... more comming soon

Mastering JavaScript

JavaScript News

News From: hn.algolia.com