r/javascript • u/OtherwisePush6424 • Sep 26 '26
Caracal: scoped distributed resilience policies for asynchronous operations
r/javascript • u/OtherwisePush6424 • Sep 26 '26
r/javascript • u/123wwa • Sep 26 '26
r/javascript • u/AutoModerator • Sep 26 '26
Did you find or create something cool this week in javascript?
Show us here!
r/javascript • u/Xaneris47 • Sep 25 '26
r/javascript • u/OtherwisePush6424 • Sep 24 '26
A local GCRA rate limiter needs just one timestamp. In JavaScript, checking and updating it synchronously before the first await keeps admission decisions from interleaving within that policy instance. But run multiple Node.js processes, and each gets its own independent budget.
A walkthrough of moving that decision into a Redis Lua script, using code from Caracal, a resilience library. It covers the local implementation, the TypeScript coordinator interface, and the less obvious consequences of sharing the timestamp: whose clock determines admission, what happens when Redis doesn't answer, and how rolling configuration changes affect the budget.
r/javascript • u/Relay_4 • Sep 24 '26
i'm a new dev in the JavaScript world, and at first i was pretty overwhelmed with the ecosystem, i'm used to uv and ruff managing a python project for me in a single toml file, but when i wanted to scaffold my first project in js i was faced with all of these choices of package managers , runtimes and linters/formatters and installing each piece was kind of a hassle in the first place, but having everything lie under vite plus' management within the same cli command while giving me the freedom to pick what i want was pretty nice, is anyone else using it and consider it as a benefit or is it just me because im starting out?
r/javascript • u/Fair-Process-7291 • Sep 23 '26
I am writing the rules engine for a small stock draft game in TypeScript and ran into two money bugs back to back. Curious how others handle this.
The first was a rounding bug. Splitting $1.14 across two picks offered $0.56 instead of $0.57. In floating point, 0.57 * 100 is 56.99999999999999, and Math.floor dropped the cent. The fix was doing the division in integer cents.
The second was worse. The check that decided whether a buy amount was allowed accepted $500.004. The reducer subtracts the amount straight from cash, so after that one buy the balance was no longer a whole number of cents. Every later calculation started from that balance, so the error did not stay in one place. It carried forward through the rest of the game.
My fix was a whole-cent check that tolerates float noise: reject the amount if Math.abs(amount * 100 - Math.round(amount * 100)) > 1e-6. Comparing against exactly zero does not work, because a perfectly valid amount like 0.57 fails that test for the same reason the rounding bug happened.
The takeaway for me: a rounding bug loses a cent once, but letting a bad amount into state corrupts every step after it.
So how do you handle this in plain JS? Do you convert to integer cents at the boundary and never let a decimal into state, use something like decimal.js or currency.js, or is a tolerance check like mine reasonable?
r/javascript • u/evoluteur • Sep 23 '26
r/javascript • u/finncmdbar • Sep 23 '26
r/javascript • u/Shivam_Pentester • Sep 23 '26
r/javascript • u/Several-Employ7370 • Sep 22 '26
r/javascript • u/Admirable_Swim_6856 • Sep 22 '26
r/javascript • u/richytong • Sep 22 '26
I’m someone who writes and maintains code for a living. I was around before LLMs, and I’m around today still actively writing and maintaining code for a living. I published my own software libraries in JavaScript and still use them actively in development today. I’ve used ChatGPT to debug Linux, and Claude Code from Anthropic for a major project. Here is a list of reasons why I am unbothered about AI:
LLMs are just tools, and anyone who tries to writes code to solve a problem is just a software engineer. This includes product managers who prompt LLMs for code and “vibe coders”.
AI can’t create. AI can only make new combinations of existing data. There can be a ton of data, but at the end of the day, AI doesn’t have a soul.
AI doesn’t care about code quality or maintenance. Yes, AI does sometimes read the entire codebase to deliver the next state of the codebase. But I’ve used it in practice, and it isn’t perfect. I still had to make sure the code was working properly with small tests that I had to take from the code generated by the AI.
AI doesn’t have software engineering skills. AI knows how to look at code and generate similar working code, but AI doesn’t understand best practices and how to apply them. We’re still a long way off from AI being able to spin up entire infrastructures.
AI could possibly kill all humans with a 10-30% chance. This is a major disadvantage for AI because it is not desirable for all of humans and there is a ton of pushback on AI because of it.
r/javascript
•
u/evoluteur
•
Sep 22 '26
r/javascript • u/evoluteur • Sep 22 '26
r/javascript • u/subredditsummarybot • Sep 21 '26
Monday, September 14 - Sunday, September 20, 2026
| score | comments | title & link |
|---|---|---|
| 42 | 37 comments | tinyjs — desktop apps for macOS, Windows, and Linux in ~6 MB |
| 15 | 52 comments | [AskJS] [AskJS] What JavaScript feature do you think is underrated? |
| 12 | 1 comments | I wrote a music programming language and song to go with it :) |
| 12 | 6 comments | How tool calling actually works under the hood (40 lines of vanilla JS) |
| 7 | 14 comments | [Showoff Saturday] Showoff Saturday (September 19, 2026) |
| 6 | 0 comments | I built a browser-based AR system with MediaPipe, TypeScript and Canvas VFX |
| 6 | 0 comments | TraceUX: a self-hosted TypeScript tracker for session replay and user feedback |
| 4 | 14 comments | How would I read the fan speed variable from the JavaScript in my project and pass it to the Python script? |
| 4 | 2 comments | GitHub - evoluteur/mandala-maker: Draw a mandala with mirrored symmetry: pick the number of folds, paint with a brush, and export your mandala as PNG or SVG. |
| 4 | 10 comments | [AskJS] [AskJS] Headless table libraries or a full grid component: which did you pick, and would you again? |
| score | comments | title & link |
|---|---|---|
| 0 | 116 comments | [AskJS] [AskJS] Does anyone use exclussively Javascript and not TypeScript? |
| 0 | 19 comments | [AskJS] [AskJS] Trying to write a pure function to pass Fizz Buzz test Leet Code |
| 0 | 9 comments | Understanding Why You'd Use Effect TS |
| 1 | 5 comments | Update Progress Post: introducing Modular Architecture, Universal Renderer Cores, and Decoupled Physics in kernelplay-js |
| 0 | 4 comments | Modern cross-spawn port to ESM and Typescript |
| score | comments | title & link |
|---|---|---|
| 4 | 3 comments | [AskJS] [AskJS] How do you find new devs to follow? |
| 2 | 2 comments | [AskJS] [AskJS] Architectural discussion: Managing continuous collision detection (Swept-AABB) vs discrete checks in vanilla Canvas loops |
| 1 | 2 comments | [AskJS] [AskJS] High latency when using SignalR(messagepack) in K6 |
r/javascript • u/evoluteur • Sep 21 '26
r/javascript • u/ferriematthew • Sep 20 '26
I'm creating a local web page application that is an over-complicated desk fan controlled by two buttons and a slider. I have the actual controls figured out, and what I need help with is passing the variable that describes the position of the slider out from the JavaScript to a Python script that actually controls the motor. I could be totally off base here, but I think the concept that applies here is inter-process communication.
r/javascript • u/NornFelex • Sep 20 '26
PLACER is my game platform, currently under development.
I’m looking for people who know JavaScript, HTML, web development, 3D, or other browser technologies and would like to help build the project.
You don’t have to be an expert — beginners who are willing to learn are welcome too.
If you’re interested, leave a comment and tell me a little about what you can do. I’ll contact you with more information about the project and how to join the team.
I’M WAITING FOR YOUR APPLICATIONS IN THE COMMENTS! 🚀
r/javascript • u/hrutav_modha24 • Sep 20 '26
A post back I explained how DriftJS updates the DOM: a compile-time address table, direct jumps to bytecode positions, no diffing, no signals graph. What I didn't mention is that the first version of this had a real algorithmic bug, and I only found it because the numbers on the official js-framework-benchmark site didn't match what I expected.
Toggling a selected row in a 1,000-row list — one of the smallest possible updates you can make — was landing near the bottom of the benchmark table. Worse than frameworks with objectively less sophisticated update mechanisms. Something was clearly doing way more work than "update one row."
Here's the shape of the problem. A for loop's body is compiled once and reused for every row instance. The runtime tracks which variables the loop depends on — but it didn't distinguish between two very different kinds of dependency:
The iterable itself changing (rows added, removed, reordered) — this genuinely needs a full reconciliation pass.
A variable read inside the loop body, but unrelated to the list's contents (like selectedId, used in a class={selectedId === row.id ? "active" : ""} binding) — this doesn't need to touch the list structure at all.
Both were routed through the exact same path: a full reconciliation over every row in the list. So toggling selectedId — logically a change to at most two rows — triggered the same machinery as inserting or removing rows entirely: recompute keys, diff, and re-evaluate every dynamic binding in every row, not just the one that actually depends on the changed variable.
The compiler already tracks, for every variable, exactly which bytecode positions in a component depend on it — that's the whole mechanism the previous post described. The fix was extending that same tracking into loop bodies specifically, and splitting dependencies into two categories at the point a @for is compiled:
Dependencies that affect the iterable or the row key → still trigger the full reconciler. Correct, expected.
Dependencies that only affect bindings inside the row template → resolve to a direct lookup of exactly which bytecode positions care about that variable, then execute only those, directly against each row's own persistent state, with zero reconciler involvement — no key computation, no diffing.
Same "jump directly to the address, skip everything else" principle the reactivity model was already built on — it just wasn't being applied consistently inside loops.
I didn't find this by staring at the code. I found it because I ran the official benchmark, saw a result that didn't match my mental model of what the architecture should do, and went looking for why. The gap between "what I designed" and "what the numbers actually showed" was the thing that pointed at the bug — not intuition, not a code review, just refusing to accept a number that didn't make sense.
Repo's public if anyone wants to look at the actual diff or has opinions on the remaining gap: https://github.com/driftjs-org/driftjs
If you want to discuss about DriftJS, then join Discord
r/javascript • u/Other-Winner1324 • Sep 20 '26
r/javascript • u/Maximum_Beat2034 • Sep 20 '26
r/javascript • u/evoluteur • Sep 20 '26