In 2026, you should be implementing MLS instead of Matrix.
Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
141–150 of 231 posts
Re: Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
#142I found the source code Jade was referring to, and it looks like the author just noticed this thread: https://github.com/nkuntz1934/matrix-workers/commit/0823b47c...
New damage control commit just came in, removing "production grade" from README, mentioning AI assistance, and fixing the misaligned ASCII diagram.
https://github.com/nkuntz1934/matrix-workers/commit/fd412f41...
Should have just nuked the whole thing to be honest, the blog post and the repo.
Re: Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
#143Earlier quoted context omitted.
Btw, after I wrote that initial article ("Cursor's latest "browser experiment" implied success without evidence"), I gave it my own try to write a browser from scratch with just one agent, using no 3rd party crates, only commonly available system libraries, and just made a Show HN about it: https://news.ycombinator.com/item?id=46779522 The end result: Me and one agent (codex) managed to build something more or less t…
Yes, this is what Ai assisted coding is good at. A poc that would usually take a team of engineers weeks to make because of lack of cross disciplinary skills can now be done by one at the cost of long term tech debt because of lack of cross disciplinary knowledge.
> Yes, this is what Ai assisted coding is good at.
This is where I wish we spent more energy, figuring out better ways to work with the AI, rather than trying replace some parts wholesale with AI. Wrote a bunch more specifically about that, while I was watching the agent work on the browser itself, here: https://emsh.cat/good-taste/ (it's like a companion-piece I guess)
Re: Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
#144“This architecture shifts the paradigm for self-hosting. It turns "running a server" from a chore into a utility. You get the sovereignty of owning your data without the burden of owning the infrastructure”
Yeah, this is just shameful. Obviously written by an LLM with zero oversight. If this engineer doesn't get fired I'll lose all trust in Cloudflare.
Re: Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
#145Ahh, so that is what "shipping at the speed of inference" means
Re: Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
#146Did they really vibe code a partial implementation and blog about it?
That's one way to destroy the CF blog credibility!
Re: Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
#147I found the source code Jade was referring to, and it looks like the author just noticed this thread: https://github.com/nkuntz1934/matrix-workers/commit/0823b47c...
New damage control commit just came in, removing "production grade" from README, mentioning AI assistance, and fixing the misaligned ASCII diagram. https://github.com/nkuntz1934/matrix-workers/commit/fd412f41... Should have just nuked the whole thing to be honest, the blog post and the repo.
Agreed. And the diagrams still lack substance, IMO.
Previously someone might sketch out a purposeful one in Monodraw or something (https://monodraw.helftone.com). But only when it adds value.
Now Claude shits out this vacuous nonsense by the bucketload———but it's some interconnected boxes in a code block in a readme, so it must be good.
Re: Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
#148Earlier quoted context omitted.
Btw, after I wrote that initial article ("Cursor's latest "browser experiment" implied success without evidence"), I gave it my own try to write a browser from scratch with just one agent, using no 3rd party crates, only commonly available system libraries, and just made a Show HN about it: https://news.ycombinator.com/item?id=46779522 The end result: Me and one agent (codex) managed to build something more or less t…
Would be interested to know what people think of the locking implementation for the net worker pool. I’m no expert but it seems like a strange choice to me - using a mutex around an MPSC receiver, so whoever locks first gets to block until they get a message. Is that not introducing unnecessary contention? It wouldn’t be that hard to just retain a sender for each worker and just round robin them
I haven’t looked at the code, but what you’re describing doesn’t sound that bad. If the queue is empty then it doesn’t matter whether a worker is waiting on the lock or waiting on the receiver itself. If the queue is non-empty then whoever has the lock will soon complete the receive and release the lock. It would be better to just use an actual MPMC channel, but if the traffic on the queue isn’t too high then it probably doesn’t make a significant difference. With round robin in contrast, the sender would risk sending a job to a worker that was already busy, unless it took additional measures to avoid that.
Re: Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
#149Bloody hell that's embarrassing, for both Cloudflare and the blog author. Did he not have anyone review it before publishing? So many failures coming out of Cloudflare these days, feels like they peaked a while ago and are slowly declining into incompetence.
> So many failures coming out of Cloudflare these days I wonder if there's a particular new fad that could be causing this
Hubris?
Re: Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
#150I'd love to see a root cause analysis post by Cloudflare for this one. The ones they do after outages are always interesting to read.
How did this make it into the blog? What is the review process for these posts and what failed this time? What measures will be taken to restore Cloudflare blog's reputation?