kentonv

30 ms·

91.
by kentonv 3mo ago
That's me. Other way around -- proto2 came first.
92.
by kentonv 4mo ago
I wasn't personally involved in pricing here so I can't really say exactly why it is the way it is. However, I'd note that, in terms of our costs, it's often cheaper for us to run your Worker than to serve from cache. Co
93.
by kentonv 4mo ago
Realizing there's a more fundamental piece I'm not explaining well here. Our architecture is something like: ingress -> routing -> security -> workers -> cache -> origin That is, workers run "in front of"
94.
by kentonv 4mo ago
The honest answer is: We implemented the "standard" Cache API back in the early days because it was a standard, one which was intended to be used together with the Service Workers API, which we were also building around back then.
95.
by kentonv 4mo ago
You are saying $1.5B of AI spend would not have shown up in either of these numbers? Please do tell us how that works, I'm sure it's fascinating and would love to know more.
96.
by kentonv 4mo ago
Would you be happier if I said "non-GAAP profitable"?
97.
by kentonv 4mo ago
> (partially driven by the fact that the company was bleeding money also because of its token costs from one estimate being 500 million$ per month, don't quote me on that though) Cloudflare had 5000 employees (pre-layoff), so you ar
98.
by kentonv 4mo ago
This is really cool! Quick suggestion: When not tracking a train, the mouse wheel should zoom into / out from where the cursor is pointing, rather than the center of the window.
99.
by kentonv 4mo ago
Oh no... KV is not a distributed database and is really not intended as a database alternative at all. It's more meant for distributing bits of config globally. Cost aside, writes are way too slow for database-ish use and "eventua
100.
by kentonv 4mo ago
Part of the point of Workers is they run everywhere, not on a specific machines where they've been "deployed". We generally run a Worker in the colo where we received the HTTP request triggering it. There is a feature called
101.
by kentonv 4mo ago
I'll let you in on a sort of dirty secret: It's almost always better to use Durable Objects storage, rather than D1. Even if you only want a single global database, it's better to implement that as a singleton Durable Object,
102.
by kentonv 4mo ago
> it only makes sense to deploy small things there What makes you say that?
103.
by kentonv 5mo ago
Yes, the Cloudflare Workers Runtime is open source: https://github.com/cloudflare/workerd You can definitely run workerd in production on your own machines and some people do. The biggest catch is that workerd's i
104.
by kentonv 5mo ago
> bcryptjs reaches for crypto.randomBytes and a few other Node primitives that aren't polyfilled in Workers. crypto.randomBytes is definitely in Workers' node compat layer. Is it possible you didn't enabled the node_compat
105.
by kentonv 6mo ago
I don't care what the attack is responding to, nor do I care what services are being provided. If, when I visit your site, your site causes my browser to participate in a DDoS attack without my knowledge, your site is malicious.
106.
by kentonv 6mo ago
archive.is is malicious -- as in, uses your browser to launch DDoS attacks, and other things. Stop using it. https://arstechnica.com/tech-policy/2026/02/wikipedia-bans-a...
107.
by kentonv 6mo ago
Claude does not use the web search tool unless it thinks there's a good reason to. If you nudge it to search, it will, and then it'll tell you all about OpenClaw. You can easily go try this yourself -- I just did. It works fine. &
108.
by kentonv 6mo ago
Come on, folks. This is not a conspiracy. LLMs have a knowledge cutoff date. Opus 4.7's documented cutoff date is in January. Older Claude models are earlier than that. OpenClaw didn't have the name OpenClaw until January 30th. So
109.
by kentonv 6mo ago
> Not that you would know that the way our genius CTO talks about it... Honestly I find it bizarre that there are people at Cloudflare who have this attitude. Without Dane, the company wouldn't be half the size it is today.
110.
by kentonv 6mo ago
None of the three major Cloudflare outages in the past six months had anything to do with LLMs. They were regular old human mistakes. We did, however, determine that at least one of them (and perhaps all) would have been easily caught by AI
111.
by kentonv 6mo ago
> about 68 degrees Fahrenheit (20 degrees Celsius) Pet peeve: When the original source had only one significant figure ("20 degrees", probably the scientist rounded to the nearest 10 because it's approximate), but the repo
112.
by kentonv 6mo ago
> Not to mention the atrocious 3MB worker size limit That's for the free plan. Limits are documented here: https://developers.cloudflare.com/workers/platform/limits/#w...
113.
by kentonv 6mo ago
You can farm out the requests to a bunch of Durable Objects. Each DO will have a separate six-concurrent limit. And you can send unlimited concurrent requests to Durable Objects. (This is not an exploit, this is working as intended. The con
114.
by kentonv 6mo ago
Cloudflare's Durable Objects puts your Worker and SQLite DB on the same physical server (and lets you easily spawn millions of these pairs around the world). D1 is a simplified wrapper around DO, but D1 does not put your DB on the sa
115.
by kentonv 6mo ago
Just a heads up, the naming might be a little confusing vs: https://github.com/cloudflare/kumo
116.
by kentonv 6mo ago
Hey, sorry this has been a confusing transition. You can actually still create new Pages projects, but it is de-emphasized in the UI in favor of Workers. We've done a lot of work to make static sites on Workers just as easy to configur
117.
by kentonv 7mo ago
To clarify, there are two approaches you can take to handle large-scale databases on Cloudflare: With Durable Objects[0], you can create and orchestrate millions of sqlite databases that live directly on Cloudflare's edge machines. The
118.
by kentonv 7mo ago
I can assure you that nobody at Cloudflare ever thought that open sourcing workerd would be a way to get "free labor from the commons". On the contrary, we are wary of external contributions. The Workers Runtime is a complicated c
119.
by kentonv 7mo ago
Cloudflare Workers is a big on capabilities. The recently released Dynamic Workers directly provides an API for capability-based sandboxing: https://developers.cloudflare.com/dynamic-workers/usage/bind... But the
120.
by kentonv 7mo ago
When using Dynamic Workers, you generally don't run the AI harness inside the Dynamic Worker itself, but rather as a regular worker. But your harness would have a tool call that's like "executeCode" which runs code in th

More ›