Cloudflare Flagship • Hacker News Board

Re: Cloudflare Flagship

#101

Post by youre-wrong3 » Wed, May 27, 2026, 7:58 AM UTC

hn_throwaway_99 wrote: post #86

youre-wrong3 wrote: post #82

Earlier quoted context omitted.

That’s all it is. This only exists to lock you into cloudflare even more.

Then why did they deliberately make it compatible with Open Feature, explicitly making it easy to swap out a different Open Feature provider? Oh, that's right, you just spouted a "big company bad" mantra without bothering to read the article. Look, I know saying RTFA goes against the HN guidelines, but the amount of increasingly lazy spew i see from folks (or bots) who haven't bothered to read the article is so tires…

Oh look. Found the guy who’s taken it hook line and sinker.

Re: Cloudflare Flagship

#102

Post by ramon156 » Wed, May 27, 2026, 8:17 AM UTC

paulbjensen wrote: post #95

Gold-plated booleans-as-a-service

I don't mind it. I don't want to keep track of thousands of feature flags in my DB, have to create an admin dash, etc.

You could call any SaaS tool "excel-as-a-service" and it would hold the same power as your comment.

Re: Cloudflare Flagship

#103

Post by 5701652400 » Wed, May 27, 2026, 8:25 AM UTC

ramon156 wrote: post #102

paulbjensen wrote: post #95

Gold-plated booleans-as-a-service

I don't mind it. I don't want to keep track of thousands of feature flags in my DB, have to create an admin dash, etc. You could call any SaaS tool "excel-as-a-service" and it would hold the same power as your comment.

or maybe just make single JSON and commit it to git? your http server + GitHub + JSON and text editor is your admin ui, audit, etc.

Re: Cloudflare Flagship

#104

Post by 5701652400 » Wed, May 27, 2026, 8:26 AM UTC

never understood this. why follow over-engineered standard and depend on 3rd party API spec, and 3rd party vendor. if you cannot call home from your service, you having bigger problems. and once you can call home, it is just.. single json file.

Re: Cloudflare Flagship

#105

Post by jwr » Wed, May 27, 2026, 8:36 AM UTC

Am I the only one worried about Cloudflare becoming too powerful?

We went through this with E-mail: we slept through the period when Google, Microsoft and AWS were growing, and we ended up with them dictating the terms. Today I get 90% of my spam from Google, Microsoft and AWS and they don't care: they can safely ignore spam reports, because at this point they are Too Big to Block.

I have a feeling we are moving towards the same problem with Cloudflare and the web. Tomorrow Cloudflare will start dictating what we can or cannot do and we will not be able to do anything about it. This has already begun: their arbitrary "bot-filtering" for example.

Re: Cloudflare Flagship

#106

Post by tom1337 » Wed, May 27, 2026, 8:49 AM UTC

5701652400 wrote: post #103

ramon156 wrote: post #102

Earlier quoted context omitted.

I don't mind it. I don't want to keep track of thousands of feature flags in my DB, have to create an admin dash, etc. You could call any SaaS tool "excel-as-a-service" and it would hold the same power as your comment.

or maybe just make single JSON and commit it to git? your http server + GitHub + JSON and text editor is your admin ui, audit, etc.

how would a single JSON allow staged rollouts with sticky sessions?

Re: Cloudflare Flagship

#107

Post by tom1337 » Wed, May 27, 2026, 8:50 AM UTC

Hamuko wrote: post #61

roerohan wrote: post #52

Earlier quoted context omitted.

https://blog.cloudflare.com/flagship Here's why we built it!

> Agentic coding tools like OpenCode and Claude Code are shipping entire features in minutes. How many minutes do I need to wait until app-scoped tokens are live?

Sorry, just reached the weekly token limit.

Re: Cloudflare Flagship

#108

Post by tybit » Wed, May 27, 2026, 8:57 AM UTC

paulbjensen wrote: post #95

Gold-plated booleans-as-a-service

I’ve seen whole teams at companies set up fail to provide these booleans-as-a-service well. There are whole companies like LaunchDarkly for them.

If you boil it down to this, you may as well boil down every service that exists to bits-as-a-service.

Turns out theres legitimate business value in these things, and complexity in delivering them.

Re: Cloudflare Flagship

#109

Post by pavo-etc » Wed, May 27, 2026, 9:11 AM UTC

tom1337 wrote: post #106

5701652400 wrote: post #103

Earlier quoted context omitted.

or maybe just make single JSON and commit it to git? your http server + GitHub + JSON and text editor is your admin ui, audit, etc.

how would a single JSON allow staged rollouts with sticky sessions?

you pick a frequency you want, represent that as a fraction, and modulo on user id, and your 80% of the way there

Re: Cloudflare Flagship

#110

Post by xboxnolifes » Wed, May 27, 2026, 9:17 AM UTC

jwr wrote: post #105

Am I the only one worried about Cloudflare becoming too powerful? We went through this with E-mail: we slept through the period when Google, Microsoft and AWS were growing, and we ended up with them dictating the terms. Today I get 90% of my spam from Google, Microsoft and AWS and they don't care: they can safely ignore spam reports, because at this point they are Too Big to Block. I have a feeling we are moving towa…

> Am I the only one worried about Cloudflare becoming too powerful?

No, it gets brought up in every single thread about cloud flare. And if this wasnt a feature release that people seem to like, the top comment would probably be talking about how cloudflare is terrible for the internet.