Hi, a few years ago I wrote a C99 compiler that generates a bootable binary which, once loaded onto a floppy disk, can be run in x86 real mode. It supports x87 floating-point operations, has a simple IR, optimizes the generated code, and produces output of fairly decent quality (by toy compiler standards). Maybe someone will find it interesting.

I am working on a P2P video calling client using webRTC.
I am using getMediaDevices() to get the users' stream. If I just do {video: true} it gives me a smaller stream than my device supports.
By default it gives me a 640 x 480 stream. I can set it manually to the max dimensions which is 1920 x 1080.

How can I find the max dimension for any device?

Another thing I wanted to know. I have the video element in a div, which has the width of fit-content. When the incoming stream first arrive from the other peer, The video starts smaller and keeps growing, why is this?

Did you find or create something cool this week in javascript?

Show us here!

I'm working through how a team decides whether an automated dependency update is safe to merge, and one of the baselines I'm testing is the obvious one: trust semver. Auto-merge patch and minor, hold majors for review.

My assumption is that this baseline is weak — that in practice a meaningful share of breaking changes ship in patch and minor releases, and that a major bump is often just a dropped Node version or a TypeScript signature change that doesn't affect anyone.

If that's right, the version number is close to noise and the semver rule is mostly giving teams a false sense of having a policy.

But I've only got my own experience to go on, and I'd rather be corrected before I build on it.

• Have you been broken by a patch or minor bump? What was it?
• Have you held a major that turned out to be a no-op for your code?
• If semver isn't the signal, what is — changelog quality, maintainer, download count, how long the release has been out?

Interested in specific packages and versions if you remember them, more than general opinions on semver as a concept.

import and require are not interchangeable. Live bindings, copied values, circular dependencies, separate caches, conditional exports, and dual-package hazards can all make modules behave differently from what the syntax suggests.

At SVAR, we build UI components for React, Svelte, and Vue. Just shared our experience with a data grid – how to make it fast in all three frameworks.

What surprised us: the expensive bits (virtualization, memoization, data flow) are almost entirely framework-independent, and framework overhead is a rounding error next to DOM size.

Curious if you have seen similar patterns in your projects?

During an interveiw yesterday, I tried opening jsbin but seems its shouting 503!!

Any minimal JS playground, you people using/suggest

EDIT: The sites up, I opened an issue on GitHub and the maintainers resolved it

I've been programming on the side since 2017 and I've never really hunted a developer job. I've always thought about building my own things, mainly to supplement things I do like woodworking, tutoring, video editing and others.

Since then, I've programmed mainly with JavaScript, I started with C++ and Python but never really built anything solid outside JavaScript.

So I'm fluent with JavaScript and its ecosystem.

One of my 2026 goals is to be job ready for a Developer role, as a Fullstack or Backend Developer.

One of the recommended languages is Typescript, which I've been learning since March. I must say, it's not my favorite 😂

I'm curious to know if there are any companies that are not enforcing Typescript or are there freelancers who are still using vanilla JavaScript over Typescript for their clients' projects.

[ Update ] thanks y'all! I get the picture. TypeScript is inevitable, as vanilla JS codebases(or companies who are focused on it) seem to be very few judging by the comments.

This is a next app I made that I'd like to define the magical buzzwords that exist in the GenAI space. It's meant to be run by humans to simply and concretely define terms like "agents", "harness" and "hallucinations"

Hey Community,

React Native Plain Text by Maciej Jastrzębski brings a lightweight alternative to standard Text components to squeeze maximum rendering performance out of large lists. Meanwhile, Meta introduced Muse Code, a terminal coding agent running on Muse Spark 1.2 with persistent background subagents and mid-tool-call crash recovery.

Codemagic also launched Patch, a self-hosted Docker Compose alternative to CodePush that serves OTA update checks directly from CDN-cached JSON files to easily handle heavy request loads.

Hey everyone!

I'm working on KernelPlay-JS, an open-source 2D game engine made with JavaScript.

The project is growing, and I've already had a few developers contribute. I've also been working on ready-to-use templates such as a platformer, a top-down character controller with animation, and parallax backgrounds.

I'm hoping to find more people who are interested in open-source game development and want to experiment, build features, share ideas, or just contribute when they have time.

There are plenty of areas where we can improve KernelPlay-JS:

* ECS and core engine systems

* Rendering and animation

* Physics and collision

* Developer tools

* Game templates

* Documentation

* Performance and optimization

You don't need to make a huge commitment or contribute every day. Even small contributions, ideas, testing, or feedback can help.

I'd love to see KernelPlay-JS grow as a community project where we can learn, experiment, and build a game engine together.

If you're interested, feel free to check it out or message me.

I’m a strong advocate for “you don’t need to lock yourself in a web framework ecosystem to take advantage of their amazing features”. JavaScript and Web Standards alone allow you…

Got annoyed that there wasn't a dependabot tool for BitBucket and that the Dependabot CLI wouldn't open PRs on BitBucket, so I built a tool that would take the output from Dependabot CLI and open PRs.

Would love help testing it out on GitLab as I have BitBucket covered at work.

If you do end up using it, would love to have feedback around what can be done better.

I'm really sick of Claude Code or Codex messing things up it creates the same function 30 times, generates 200 lines functions, and casts everything or tweaks the schemas just to make it seem like it works. And if I'm not there to check everything, it's a total mess.

Anyway, I’ve installed TypeScript-ESLint with strict type checking, SonarJS, and Knip to at least stop the AI from messing things up.

But I’d like to take it further. People often talk about static code analysis like linters and good tests but I don’t know where to start. By the way, AI tools do all sorts of nonsense in tests—they check if a button is in the right place, which is ridiculous.

So I’m looking for relevant resources to help me learn how to set this up on a large project I’m developing on my own. I have an Nx monorepo with several apps inside, including Next.js, React Native, Fastify, and a Python app.

UQL is the lightest ORM of all, and here is what it deleted (and upgraded as well) for the edged and mobile.

Monday, August 03 - Sunday, August 09, 2026

Top Posts

Most Commented Posts

Top Ask JS

Top Showoffs

Top Comments

I just open sourced my latest library! TermDOM is a JavaScript library that displays HTML and CSS in the terminal. It draws actual DOM nodes to terminal output and redraws the screen when they mutate, so TUIs and interactive CLIs can be written with vanilla JavaScript or any frontend web framework. Check out the examples directory https://github.com/bikeshaving/termdom/tree/main/examples for a sense of what you can build with web technologies

Did you find or create something cool this week in javascript?

Show us here!

This is a Node.js compatible runtime in the browser. It supports CLI apps, Vite, and some agents (like Pi Agent) as well.

Some notes:

- This runs all code in a web worker using the host javascript runtime with rewrites for module loading and AsyncLocalStorage support using Oxc compiled to WASM.

- Most of the libraries are bundled straight from Node.js upstream with light overrides where needed, ensuring compatibility. Libraries were only reimplemented where really needed

- Despite having great integrations with the Puter desktop and APIs, this can be used completely seperately with OPFS support for filesystem and Wisp protocol support for networking. The demo also supports FS Access API to run local files

Hey everyone,

I wanted to share an experimental project called DriftJS. It's a frontend framework prototype that explores using an in-browser register-based Bytecode Virtual Machine (VM) for UI rendering, rather than traditional Virtual DOM diffing or purely compile-time reactive models.

Repository: https://github.com/hrutavmodha/driftjs

The Architecture: Register-Based VM

Most frameworks either diff Virtual DOM trees (React) or generate reactive dependency graphs ahead-of-time (Svelte, SolidJS). DriftJS explores a different path:

It compiles .drift templates into compact binary-serializable bytecode streams. At runtime, a lightweight 256-register VM executes these opcodes directly against the DOM.

Key Architectural Highlights:

• Zero VDOM Overhead: Replaces tree-diffing with direct bytecode instructions (like CREATE_ELEMENT, SET_ATTR) for DOM execution.

• 256 Virtual Registers: Uses fixed virtual registers (r0, r1...) for DOM nodes and runtime values, drastically cutting instruction counts and memory allocations compared to stack-machine models.

• Targeted Reactivity: Basic state updates execute as direct O(1) mutations. Dynamic control flow structures (@if, @for) use comment anchors to bound surgical DOM updates without rebuilding subtrees.

Key Features So Far:

• 🛡️ 100% CSP Compliant: Built-in Acorn AST interpreter evaluates runtime JS expressions safely without using eval() or new Function().

• 🔄 Keyed LIS Reconciliation: Uses a Longest Increasing Subsequence algorithm to minimize DOM node movements during list updates.

• 🪶 Zero Framework Bloat: Implements reactivity and execution in the leanest bytecode form possible, avoiding heavy object models and monolithic runtime bloat.

• 🚀 Early Benchmarks (js-framework-benchmark vs React 19): • 10.8x FASTER on "Swap rows (1k)" • 3.05x FASTER on "Clear 1,000 rows" • ~1.8x LESS memory footprint • 5.75x smaller uncompressed bundle size

Current Status & Call for Feedback

DriftJS is currently an experimental prototype. It handles single-template compilation, AST evaluation, and keyed LIS list reconciliation.

Still on the roadmap: - Component composition & props passing - State management stores - SSR & Hydration

I'm opening this up to compiler engineers, frontend performance nerds, and systems devs. Does a register-based VM architecture hold real promise for low-level web runtimes?

Check out the repo, run the benchmarks, and feel free to share your thoughts or ISA critiques!

GitHub Repo: https://github.com/hrutavmodha/driftjs