← Back to context

Comment by OptionOfT

15 hours ago

Let's think about it. This is probably something used internally at CloudFlare and someone thought I'd be interesting to make it public.

There is no way 6 months ago someone at CloudFlare thought it was a good idea to build a competitor to say LaunchDarkly.

17 comments

OptionOfT

Reply
jasonjmcghee  15 hours ago

Hmm not sure I necessarily agree. Cloudflare's strategy has been looking like "the only platform you need" for a while now.

Their recent features / announcements have been equivalent to:

(LaunchDarkly)

Resend, Firecrawl, CrewAI, Helicone, Replicate, Pinecone

-

Which like… many companies have a painful procurement process. If all you need is Cloudflare, and prices are within reason- why not use them

  • gowthamgts12  13 hours ago

    Their quality of the products they ship have already became shitty for quite a while now.

    • risyachka  7 hours ago

      they are quickly turning into a slop shop

      instead of polishing their existing products (and most of them do require a lot of work) they jump into any other niche someone thought was a good idea. My guess is that with ai being able to prototype things quickly they just started doing everything that is even a bit relevant.

      which won't end well

      1 reply →

bg24  15 hours ago

Both Cloudflare and Vercel have feature parity. Flags is a feature already in Vercel. While customer-first is a thing, it is also a no-brainer to start with: we use it, Vercel has it, let us build it.

  • pjmlp  11 hours ago

    Now waiting for Cloudflare to allow me to use Rust for serverless, real native code, not WebAssembly.

    https://vercel.com/docs/functions/runtimes/rust

    • iainmerrick  9 hours ago

      They have containers, does that count?

      If you’re specifically thinking of native ephemeral workers with very fast startup, it seems like those would have to be sandboxed somehow, and WebAssembly seems like a decent solution. Is there really a significant native code gap between WebAssembly workers and native containers?

      2 replies →