Hacker News new | ask | show | jobs
by wpietri 1723 days ago
I did read it, thanks.

That you can't see any short-term impact is exactly my point. Nothing significant will change, so this is not a disruptive innovation. It's a minor incremental change in the market. Might it enable something disruptive down the road? Possibly. But that's possible, not actual. If you want to more about what disruptive means in this context, I'd suggest reading one of Clay Christensen's books or the article I linked up above.

1 comments

I'm mostly talking about significant impact on AWS ( revenue) within 6 months. Which is not realistic in that time frame.

I see a way for cloudflare to innovate based on dropping egress fees. But I'm not sure if i can drop my hunch this early. I think i can wrap it up with " empowering open-source".

I'll see if the future unravels in that direction. There are additional products required for that path to fulfill and I think a 6 month timeline is kinda short for that.

I agree it's not realistic. Or even within a year. Which means this is not a disruptive change on it's own. Could there be other changes made by Cloudflare that are disruptive? Sure. Could they make use of this? Also yes. But this on its own will not cause significant customer movement.
Well, that's because no big customer will be able to change their platform within 6 months.

Not a single innovation could.