52 points wondersky 3 hours ago 22 comments
InsidiousWombat 1 hour ago | parent
mvkel 1 hour ago | parent
700 changes per second implies 15% of all domains are changing daily, which is almost certainly not the case.
enedil 1 hour ago | parent
zoeysmithe 53 minutes ago | parent
I imagine a renewal is a change event to, at least change the expiry, and renewals are constantly happening.
toast0 44 minutes ago | parent
A domain renewal is an update at the registry, but there's no update in DNS at any level. If a domain expires, it would be removed (or at least changed) in the TLD DNS, but the authoritative DNS for the domain wouldn't necessarily update... it would just become orphaned.
LoganDark 17 minutes ago | parent
straygar 1 hour ago | parent
700 changes per second is 1.8 billion changes per month. I guess 10 changes per top level domain per month is quite low, which suggests a very long tail distribution, which makes sense, given that most websites are just a static page a business sets up once, with DNS changes maybe once every few years.
thephyber 1 hour ago | parent
Curious what the R&D / efficiency development ROI is on reducing memory footprint. I suppose we should both consider current ROI and near future ROI (as the price of memory will likely stay high for at least another 1-2 years).
placatedmayhem 1 hour ago | parent
lenerdenator 1 hour ago | parent
One thing that I really hope we see out of the LLM revolution: a return to native applications. You could argue that Electron cross-platform apps made sense when you had to pay a team to maintain two or three (at least) native clients; you can't make that argument anymore when the marginal cost of a line of code is $0.00.
floydnoel 58 minutes ago | parent
I guess developers really prioritize velocity or ease over everything. Or maybe it's business pressure or directives?
lenerdenator 55 minutes ago | parent
Yes, they're getting their bonus. No, we can't hire and onboard more people to deal with the insane demands being made as a result. Why do you ask?
Klonoar 48 minutes ago | parent
Platform-specific views simply aren't. For simple applications they might make sense, but at a certain point devs just want the shit to work. Electron solved that.
I do agree that LLMs & co should contribute to reversing this trend, though. I don't really see why you couldn't try to ship (true) native now.
freedomben 13 minutes ago | parent
renehsz 1 hour ago | parent
But it's convenient. I can't really fault people for using it.
Aperocky 28 minutes ago | parent
nikanj 53 minutes ago | parent
Client-side: lol sucks to be you
jgrahamc 9 minutes ago | parent
Source: I was Cloudflare's CTO.
mhovd 55 minutes ago | parent
schainks 46 minutes ago | parent
LoganDark 19 minutes ago | parent
> Why doesn't the Zone Builder just rebuild the setting that changed?
> It should, and that is where we ended up. However, proving when it was safe took most of the work. A record event identifies what changed. A zone event can come from many Cloudflare products, may not say why the zone changed, and can alter data shared by several zones with the same name. Choosing too much work wastes capacity. Choosing too little can leave stale or incorrect DNS data at the edge.
Re-reading the start of the post with that in mind, I'm fairly sure the article was generated by LLM.
With that said, curated it sure is. Aside from the smelly phrasing, the actual content is fairly dense and engaging. Not all of Cloudflare's LLM-generated posts are this good, but this one is fairly alright.
JulianPaul 23 minutes ago | parent