point #2 is silly. So basically your product is slower but its ok cuz its a beta only... Fine. But then cf did not mislead anyone. Your beta is slow.
Kind of? At minimum they made misleading representations. They used abbreviated explanations of how they're better and then expanded on what the test actually consisted of later on.
Fastly does not have a production-ready JavaScript product. From their blog post,
> Their tests compare JavaScript running on Cloudflare Workers, a mature, generally available product, with JavaScript running on Compute@Edge. Although the Compute@Edge platform is now available for all in production, support for JavaScript on Compute@Edge is a beta product. We clearly identify in our documentation [2] that beta products are not ready for production use. A fairer test on this point would have compared Rust on Compute@Edge with JavaScript on Cloudflare Workers, which are at more comparable stages of the product lifecycle.
Restricting any comparison isn't satisfactory since we care about both the supported languages and performance. Let there be writeups about both and allow users to make up our own minds.
I think the Cloudflare article [2] could be amended to refer to the compared product as "Fastly's JavaScript on Compute@Edge" and all would be fine. Fastly will probably still say they advise against this comparison since it's "beta". Nonetheless, we should all feel free to compare publicly available products and write about them.
[1] https://docs.fastly.com/products/fastly-product-lifecycle#:~....
[2] https://blog.cloudflare.com/network-performance-update-full-...
Beyond just those points, the whole Cloudflare blog post reads like an attempt at a performance sales kill sheet. (In other words, their sales may point to this as to why folks should choose Cloudflare Workers over Fastly Compute@Edge.)
Do you want to highlight any of those? RTT is mentioned in a post from "Cloudflare Research" which was just shared by their head of research [1].
> Beyond just those points, the whole Cloudflare blog post reads like an attempt at a performance sales kill sheet. (In other words, their sales may point to this as to why folks should choose Cloudflare Workers over Fastly Compute@Edge.)
There is nothing wrong with advertising. This comment section is just about keeping them honest.
[1] https://twitter.com/grittygrease/status/1468016152752361472
I hope Fastly stops calling things "cold starts" that aren't [1].
And, I think Cloudflare could do a quick find-and-replace on that article [2] to change "Fastly’s Compute@Edge" to "Fastly’s JavaScript on Compute@Edge". A phone call between friendly CEOs probably would have sufficed for that.
We all want to be on the same page when making these comparisons. Some may choose Fastly and write in Rust, some will choose Cloudflare and write in JavaScript.
[1] https://news.ycombinator.com/item?id=29465729#29468068
[2] https://blog.cloudflare.com/network-performance-update-full-...