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

21–30 of 87 posts

Re: Workers Cache

#21

Post by geraneum »

lijok wrote: post #7
davidmurdoch wrote: post #2

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

Can you elaborate? I read it, found the concepts well explained, walked away better informed. Responding to alleged slop with more slop doesn’t decrease the total amount of slop on the internet.

Not the original commenter; but, at least for me, the idea is that when it’s written by humans we know that effort and care were put into communicating the news. Otherwise they could post a link to the docs and we could ask my flavor of LLM to summerize. No need for extra filler content. That why it’s slop and it’s different.

Re: Workers Cache

#23

Post by ignoramous »

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.

What does it mean when prompting SoTA LLMs prone to slop to be concise and precise, with respect to context at hand, not work at all? Anyone benchmarking that?

Re: Workers Cache

#25

Post by afavour »

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.

You use Cloudfront. Which you’re already doing anyway but yes, you do need to configure it.

Re: Workers Cache

#27

Post by CodesInChaos »

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…

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

Re: Workers Cache

#28

Post by vlucas »

Huge props to just sticking with the HTTP spec on this one with `Cache-Control` headers with `stale-while-revalidate` support. It's amazing how many other providers mess that up.

On top of that the cache tags are a slick way to do invalidation. This looks like a great product.

Re: Workers Cache

#29

Post by lijok »

geraneum wrote: post #21
lijok wrote: post #7

Earlier quoted context omitted.

Can you elaborate? I read it, found the concepts well explained, walked away better informed. Responding to alleged slop with more slop doesn’t decrease the total amount of slop on the internet.

Not the original commenter; but, at least for me, the idea is that when it’s written by humans we know that effort and care were put into communicating the news. Otherwise they could post a link to the docs and we could ask my flavor of LLM to summerize. No need for extra filler content. That why it’s slop and it’s different.

I don’t have access to my flavor of LLM on the train nor the time or budget to have it do the research and summary for me

Why are we all of a sudden pretending like pre-LLM era blogs were these pristinely well written pieces of art or even that effort and care was put into them? In most cases they were significantly less coherent and incomplete. Don’t get me started on the mess that was the communication of this particular company or one of their competitors like AWS.

Post reply on HN