I upvoted Kenton’s post. He’s the reason Workers exists. Surprised anyone worried about him commenting. I’d only be worried if I were a competitor who pissed him off by publishing BS stats. I’d imagine there’ll be an incredibly thorough and totally unimpeachable benchmarking study that comes out of this. And, anywhere we’re not the fastest, we soon will be. Game on.

> I’d only be worried if I were a competitor who pissed him off by publishing BS stats

An unusual and excellent CEO stance. Now I like Cloudflare even more.

Cloudlfare and other CDNs like it are a scourge on the Internet destroying privacy. At this point they have better tracking hooks than Google.

No JS required, just feed all web requests directly through them where they can see all first party cookies, encrypted contents, etc.

Why would you send a CDN any cookies?

CF as a CDN is for much more than just sending static assets. Folk put whole-ass huge applications behind that infrastructure.

What do you think a CDN is? How do you think CDNs like Cloudflare works? They act as a complete proxy to all web requests, including cookies.

Truuuue. I suppose I meant cookies are normally an encrypted ID with a user salt. So what would be the harm? But you're right; my actual question was something else.

Kenton is a star and they're lucky to have him. But I don't think he was defending the company, rather defending his own work.

They seem to be one in the same.

Yep. When you're the tech lead for a significant feature in a very significant company, indeed they are one and the same. Whether you want them to be or not.

Not quite at the level of a public figure (Pres. Biden can't go around making flippant comments) but more than being just a private citizen or "I just work here". No amount of disclaimer can remove that, and for better or worse it's part and parcel with the job.

It's not the same. The lead dev is not responsible for all marketing around his work. That responsibility lies with the author and any editors of the blog post. Ultimately the CEO can be held responsible for both dev and marketing and they already did own the TOS issue here.