matt_oriordan

Joined 14 years ago

Karma
196
Submissions
133
Member since
Nov 9
View on Hacker News

Recent submissions

Comment · 1 month ago
Author here, and I'll declare my bias so I'm upfront. I am co-founder of Ably, a realtime infrastructure company, so I wanted Jev to be a low-latency story.

Two weeks ago I built Jev Pong and thought it was.

Then I tried to find a use our customers would ship and couldn't, so I sorted the whole first week of Jev posts instead of guessing. The data is on a separate page linked from the piece (see https://mattheworiordan.github.io/jev-landscape/ and https://github.com/mattheworiordan/jev-landscape/, which scanned ~6k posts and looked at the data from two public gateways and twenty rapidly emerging rivals).

The short version. Adoption is very real (a quarter of Vercel's AI Gateway requests, 2% of its tokens), but the 100x claim is against frontier models. In practie, Jev is more like 7x and 5x against small models you'd have likely used.

So my conclusion is Jev is a great model, unblocks things you could not do before when you're in builder mode, but when you move into production and definitely do things at scale, you're unlikely to be on Jev. We have solutions already for the things Jev does, just with some friction.

Comment · 1 month ago
Hi HN, Matt here, co-founder of Ably. I built this after Jev landed on Vercel's AI Gateway: https://github.com/ably-labs/jev-pong

It's pong where the ball moves one step per model decision.

Four lanes, one model each, same serve, same rules.

Every step the model gets the same tiny JSON state (ball, paddle, predicted intercept) and the same question: up, down or stay. One answer moves the ball one segment; eight segments cross the court. No speed up / adjustments for real play, so a lane's speed is that model's decision latency.

Numbers, recorded on Vercel (iad1) next to the gateway, 45 seconds per lane: Jev averaged 227 ms (p95 400 ms). Gemini 3.2 s, Haiku 2.5 s, GPT-5.6 Sol 3.5 s.

In the first 12 seconds: 47 decisions vs 3, 2 and 2.

Bit of fun! Enjoy

Comment · 9 months ago
Nice. I have spoken to literally 30+ developers who have hit these exact problems. I would have though, I am the co-founder of Ably and we were doing product validation
Comment · 1 year ago
Oh, I'll take a look :/
Comment · 1 year ago
An illustrated WebSocket history by the author of WebSocket.org
Comment · 2 years ago
Ably’s LiveSync (https://ably.com/livesync) is conceptually designed to solve exactly this problem by providing a database connector that subscribes to changes committed using the outbox pattern, and a models SDK to subscribe to those changes in your app. It’s early days as it’s just been released, but at the core the team’s goal in designing that was to solve this exact problem. Interested if this is meets your needs? Disclaimer. I am the co-founder of Ably.
Comment · 2 years ago
Wow, that didn't last long! This can only be an acquihire given Sunil worked at Cloudflare before.
Comment · 3 years ago
Quite frankly whilst I have no love for Meta, if they are willing to spend stupendous amounts of money to open source their AI models, yet prevent use of this by companies who reach 700 million MAUs from benefiting from this investment, then they’re doing a service to the community and ultimately finding a way to commercialise their investment. Tldr; they’ve invested a lot of money and time to help the community benefit from AI. If you then go onto build a billion dollar business servicing near one a billion users, then they expect a thank you in currency. How is that not reasonable?
Comment · 4 years ago
I am one of the co-founders of https://ably.com. We have built a Serverless websockets platform that is near infinitely scalable and designed to handle the complexity you’re describing such as cluster resizing, connection failures, automatic sharding and reallocations using hash rings across our global edge service etc. I’d be really interested to hear why you wouldn’t consider offloading this to a service like ours which powers the likes of HubSpot, Expedia, Spotify etc. Feel free to contact me directly @mattheworiordan if you’d prefer not to comment here. I’m really keen to hear different perspectives on what we’re doing right and where we can improve!
Comment · 4 years ago
Been using this site for years, it's a far better way of consuming HN IMHO

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton