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

31–40 of 87 posts

Re: Workers Cache

#31

Post by nwatson »

CodesInChaos wrote: post #27
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…

I have an over-hyphenated writing-style as well. Probably my Germanness.

I opine that over-hyphenation adds clarity.

Re: Workers Cache

#32

Post by baueric »

htsh wrote: post #16

curious, how does one configure something like this for AWS Lambda? Appreciate it. I am assuming it is a bunch of manual work.

Equivalent is probably putting AWS CloudFront in front of your lambda. Has edge caching with customizable config.

Re: Workers Cache

#33

Post by Xirdus »

napsterbr wrote: post #18
topgrain2 wrote: post #17

Earlier quoted context omitted.

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.

Whether we like it or not, em dashes are effectively verboten in online discussions and blog posts if you want people to take you seriously. If the idea that excessive hyphenation is an AI tell gains traction, it too will become impossible to use without ruining your credibility.

Re: Workers Cache

#34

Post by hdz »

Does anything beat a free static site hosted with Cloudflare workers at this point, performance wise?

Re: Workers Cache

#35

Post by PUSH_AX »

ignoramous wrote: post #15

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. Incredib…

Our bandwidth is very high, we constantly get invited onto the call with their team, but after talking with them a few times it makes absolutely zero sense for us to have a committed spend, all the stuff I needed an account manager for in GCP/AWS just doesn't exist in CF. Support wise I imagine if it's broken for us it's also broken for 2 million other people so... yeah... Thanks CF!

Re: Workers Cache

#36

Post by NSUserDefaults »

Reinventing the web, one service at a time. Is it really that hard to build things like this on a per-case base, small scale, all on a bare bones VPS? Do we need a global gateway to help us not screw up the basics? Service looks nice but makes me sad somehow.

Re: Workers Cache

#37

Post by jgrahamc »

davidmurdoch wrote: post #6
dan_sbl wrote: post #5

Earlier quoted context omitted.

Billion dollar company can't afford one human copywriter. The future is great! (edit: copyrighter -> copywriter)

They could just feed an llm a small corpus of past human authored posts from their site, and have the LLM rewrite it in a style matching style, and it would likely turn out pretty great.

I've tried this with my own blog posts from blog.jgc.org and the result was... not good. It basically wrote something that read like a parody.

Re: Workers Cache

#38

Post by [deleted] »

CodesInChaos wrote: post #27
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…

I have an over-hyphenated writing-style as well. Probably my Germanness.

[deleted]

Re: Workers Cache

#39

Post by simonw »

> This is the caching API we've always wanted Workers to have. Here's why it took us this long

I was looking forward to the "why it took us this long" explanation but it wasn't explicitly spelled out. Any Cloudflare staff here able to expand on that?

(The article does a good job of showing how many different smart design decisions went into this, but given caching is core to what a Cloudflare does I'm still a little surprised it took 9 years to get here!)

Re: Workers Cache

#40

Post by swiftcoder »

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.

It does feel a bit like the LLMs have commoditised correct writing form, and all the plebs are all up in arms about it...
Post reply on HN