Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Workers Cache

blog.cloudflare.com

Post reply on HN
Print view View original

11–20 of 87 posts

Re: Workers Cache

#11

Post by napsterbr »

davidmurdoch wrote: post #2

The feature is great. The post itself is a slop grenade.

One of the recent AI tells other than em dash is the excessive usage of hyphenated words:

> multi-tenant-safe cache keys

> on a server-rendered app

> byte-for-byte identical (classic)

> gets a cache-speed response

> cached-file-extensions list

Honestly, this is terrible. I had to add a "use simple words only, don't hyphenate unnecessarily" warning to my Claude config. After a full day of work, having to read these Claudisms all the time make a noticeable difference on how tired you get. It gets even worse when Claude starts to make up its own vocabulary.

Re: Workers Cache

#13

Post by arikrahman »

napsterbr wrote: post #11
davidmurdoch wrote: post #2

The feature is great. The post itself is a slop grenade.

One of the recent AI tells other than em dash is the excessive usage of hyphenated words: > multi-tenant-safe cache keys > on a server-rendered app > byte-for-byte identical (classic) > gets a cache-speed response > cached-file-extensions list Honestly, this is terrible. I had to add a "use simple words only, don't hyphenate unnecessarily" warning to my Claude config. After a full day of work, having to read these Cl…

One of the earliest tells was the use of emdashes.

Re: Workers Cache

#15

Post by ignoramous » 

  When Workers Cache is enabled, every cacheable request to your Worker hits Cloudflare's cache first. If there's a fresh cached response, Cloudflare returns it directly — your Worker doesn't run, and you don't pay CPU time for it. On a miss, your Worker runs, and if your response is cacheable, Cloudflare stores it for the next request. The next request from anywhere on Earth can be served straight from cache.
Incredible! This is why I shoehorn all my server side usecases on to the Workers Platform. Cloudflare, since 2020 when I first went all-in, has consistently shipped features that reduce bills significantly (except for 2023 Workers usage model changes). In one case, when they shipped free Snippets (Workers but 32kb code size & 5s CPU time) for Pro accounts ($200/yr), our bills went from £15k+ to £0.

I know about the infamous "Enterprise plan" (especially, when your bandwidth is as high as ours in 100s of TBs) and know of at least one other tech shop that was required to pay for it ... but we haven't got that sales call, yet.

Re: Workers Cache

#16

Post by htsh »

curious, how does one configure something like this for AWS Lambda? Appreciate it.

I am assuming it is a bunch of manual work.

Re: Workers Cache

#17

Post by topgrain2 »

napsterbr wrote: post #11
davidmurdoch wrote: post #2

The feature is great. The post itself is a slop grenade.

One of the recent AI tells other than em dash is the excessive usage of hyphenated words: > multi-tenant-safe cache keys > on a server-rendered app > byte-for-byte identical (classic) > gets a cache-speed response > cached-file-extensions list Honestly, this is terrible. I had to add a "use simple words only, don't hyphenate unnecessarily" warning to my Claude config. After a full day of work, having to read these Cl…

Fuck, I spent all these years developing a thoughtful writing style that leaned toward clarity for the reader, even if it meant extra work to achieve precision, or adding affordances like “excessive” hyphenation, and now I guess have to learn to write worse.

Re: Workers Cache

#18

Post by napsterbr »

topgrain2 wrote: post #17
napsterbr wrote: post #11

Earlier quoted context omitted.

One of the recent AI tells other than em dash is the excessive usage of hyphenated words: > multi-tenant-safe cache keys > on a server-rendered app > byte-for-byte identical (classic) > gets a cache-speed response > cached-file-extensions list Honestly, this is terrible. I had to add a "use simple words only, don't hyphenate unnecessarily" warning to my Claude config. After a full day of work, having to read these Cl…

Fuck, I spent all these years developing a thoughtful writing style that leaned toward clarity for the reader, even if it meant extra work to achieve precision, or adding affordances like “excessive” hyphenation, and now I guess have to learn to write worse.

There is a world of difference between well-written human text and sloppy walls of AI-generated text. There's nothing wrong in using hyphenations or emdashes -- I use them myself! That's not the point of my comment.

Re: Workers Cache

#19

Post by davidmurdoch »

skrebbel wrote: post #10
davidmurdoch wrote: post #8

Earlier quoted context omitted.

You think I'm using AI to leave comments like this on HN?

"slop" doesn't mean "AI generated content", it means bad content, a waste of the reader's time. Grantparent's implication is that your comment was bad content, not that it was AI generated bad content.

I was riffing off of the meaning from https://noslopgrenade.com/ which made its way around the comments here on HN a few weeks ago.

Re: Workers Cache

#20

Post by lekevicius »

Amazing, exactly what Workers lacked, I was quite annoyed that a worker would spin up when 99% of my requests then return a cache. Waste of 3ms, times millions.
Post reply on HN