Top all-time · #17249
Green Vitriol
Personal blog · greenvitriol.com/postsprogrammingweb
Green Vitriol is a personal blog at greenvitriol.com about programming and web. Since 2023, 4 different Hacker News readers have linked it 14 times, most often “A Synchronization Engine for Everyone”. It is still writing: the last post was on 2026-10-30, and you can follow it by feed.
Too few sampled comments (5) to say how often HN recommends it.?
Why HN links it
HN readers link Green Vitriol for posts on JavaScript concurrency and shared memory, sync engines, lockless allocators and browser leader election. Commenters mostly cite the posts as examples.
Summarised by Claude from a sample of 5 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- A Synchronization Engine for Everyone3 people · 4 mentions · first linked 2025-03-21
- Lockless, concurrent memory allocator with SharedArrayBuffers and Atomics2 people · 3 mentions · first linked 2023-05-30
- Leader election in browser tabs, the easy way2 people · 3 mentions · first linked 2023-05-15
What Hacker News says?
With crdt implementations like y.js, writing your own synchronization engine is trivial: https://greenvitriol.com/posts/sync-engine-for-everyone
Comment linking /posts/sync-engine-for-everyone
on “Local-first software (2019)”Submitted Show HN: Fraktur, a DJ mixing app in the browser as a story · 26 points
HN discussionRelated: - https://news.ycombinator.com/item?id=43436645 - https://greenvitriol.com/posts/sync-engine-for-everyone
Comment linking /posts/sync-engine-for-everyone
on “Sync Engines Are the Future”Submitted A Synchronization Engine for Everyone as a story · 14 points
HN discussionWorth noting that javascript has had workers, shared memory and atomics for years and that you can use them today. Look at this guy writing a lockless allocator: https://greenvitriol.com/posts/lockless-allocator The only difference in this PR is that it makes threads light (workers are fat because they carry a whole v8 instance with them) and it makes shared memory default with light threads (now you need to pass a…
Comment linking /posts/lockless-allocator
on “Bun has an open PR adding shared-memory threads to JavaScriptCore”Submitted Chainable Oscillating Drones as a story · 6 points
HN discussionTo all the people saying "it's dangerous to add concurrency to javascript", javascript has already workers, shared array buffers and atomics. It's entirely possible today to start two or more workers, pass a shared array buffer via a message and then write concurrently on the same buffer forfeiting message passing and synchronizing only using atomics. You can even do lock less data structures, see for example https:…
Comment linking /posts/lockless-allocator
on “Bun has an open PR adding shared-memory threads to JavaScriptCore”Submitted Show HN: Phlebas, a live timeseries sim controlled by the console as a story · 3 points
HN discussionThanks very much for the examples ! I get your point but it does seem quite more involved to do all that management and broadcasting by hand rather than having a shared worker with a EventSource singleton for all, don't you think ? : https://stackoverflow.com/a/61636606/10469162 EDIT: Someone posted this very relevant and interesting post : https://greenvitriol.com/posts/browser-leader
Comment linking /posts/browser-leader
on “Server Sent Events”Submitted A Sync Engine for Everyone as a story · 3 points
HN discussionYou can do leader election[1] in that case [1] https://greenvitriol.com/posts/browser-leader
Comment linking /posts/browser-leader
on “Server Sent Events”Submitted Monorepo Tooling with NPM and Shell as a story · 2 points
HN discussionSubmitted Lockless, concurrent memory allocator with SharedArrayBuffers and Atomics as a story · 2 points
HN discussionSubmitted Leader election in browser tabs, the easy way as a story · 1 points
HN discussion