I can see 15% changing daily. There's all sorts of stuff being done with dkim and other anti-spam technologies that require a txt or cname or whatever change in DNS. Companies are always whitelisting vendors and mass mailers to send as them, validating domain ownership, adding new sub-domains, changing things for Exchange/365/Google/AI stuff, changing things due to a security audit, etc.
I imagine a renewal is a change event to, at least change the expiry, and renewals are constantly happening.
There's about 360 million domains (according to Verisign as of March 31, includes inactive sites as well) and if Cloudflare manages about 1/3 to 1/2 of them, that's like 180 million domains at most.
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.
I have been wondering if the memory scarcity would lead to a desire to optimize software to be more efficient.
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).
Coincidentally, I just got angry this weekend about my Mac with 64GB of RAM going OOM because of poorly optimized applications. Use of web tech, especially Electron, was common among basically all of the offending applications. Whether Electron itself or just poor coding, I'm not sure, but there's a pattern.
Electron's more-or-less just Chrome without... erm... chrome, so it makes sense that it's bloated and uses too much RAM. Even well-constructed and efficient JavaScript executed through it will do so on top of a bunch of stuff your application might not even need.
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.
Chrome is pretty efficient, as far as per page costs go! If your architecture isn't trash!
The sin is this ridiculous era of every program shipping its own runtime. I'm headed for real down votes, but this is the same lazy culture that's taken over everywhere: go and rust both ship these huge statically compiled binaries.
When you are a company, you're only running a handful of different workloads/apps on any given box, so the statically compiled price doesn't bite you. But as users, going back to dynamically linking and making the incremental cost of loading an app not also have to carry the entire world with it is such an obvious return, and one that alas seems to not be in progress at all.
The agentic age is, I hope, going to question a lot of old assumptions & needs about what we want to run. Having lots of small resident little user agencies, compiled small scripts that are attributed to a user, is something I believe will happen, but I'm less convinced we'll recognize the face of it as it happens, that the tales will be told.
Tools like agent-substrate, ax, scion, are this interesting mix between agents, serverless, and kubernetes. I find it fascinating. (For hire on this.)
https://github.com/agent-substrate/substrate
> Chrome is pretty efficient, as far as per page costs go! If your architecture isn't trash!
> The sin is this ridiculous era of every program shipping its own runtime. I'm headed for real down votes, but this is the same lazy culture that's taken over everywhere: go and rust both ship these huge statically compiled binaries.
Go and Rust are pretty efficient too, if your architecture isn't trash. If it is, they still probably are more efficient than Electron
If we want a system like, say, sdf, it would be so much worse to make each program have to host its own world, its own runtime.
Rust and go are somewhere on the continuum, between dynlibs and chrome, for how much private world they build for themselves. It's vastly less than chrome. But it's a lot. A lot more than what Linux distributions did for years and years and years.
Especially if you think if multiuser systems with multiple people using programs, then you have some scaling factor. Then it matters a lot a lot more than each lib has to be loaded distinctly for each process.
It's not good. It's not good for Electron, there are vastly better ways to run many apps taking a more dynlib path, and it's not good for rust or go. As nice as it is to dev like that.
Of course it's another huge problem that dependency trees are rarely shared. Go look at Class Data Sharing in Java: building the libs you standardize on (your orgs stdlibs) and there's this beautiful idea here that you should just already have some common things expected to be there. That's harder to imagine since so many programs have such different dep stacks. But imagine having a Tokio or tokio+++ that everyone can use. Some common substrate. And it can grow.
https://docs.oracle.com/en/java/javase/17/vm/class-data-shar...
I'm not sure at all what you're talking about at this point. The most relevant thing I can find with the abbreviation "sdf" is https://sdf.org/, but I don't understand what hypothetical version of that you're talking about where would be entirely contained within a Chrome instance.
Sure but they can do that because they own most of the system. It's the same with e.g. Debian - all the binaries you get from the repo work with all the libraries you get from the repo because they're built as part of one big project. When a separate party wants to ship something that works on most Linux systems they have to minimize dependencies as much as possible. They don't get the luxury of being the same person who controls most of the rest of the system.
A Go binary can be scp'd as a single file to any server with the same processor architecture and just run. I've never encountered that in any other framework.
That's a conservatism that's accepted but rarely tested and that's my point. I don't think it actually is so unbearably hard to have a couple builds that cover 90% of userlands. And the remaining folk can go compile themselves, if your software is the good stuff (open source).
We've accepted this as a yes absolutely to try anything is folly excuse for decades. It was tired already and it's ridiculous today to just accept it as a hard stop wall.
The degree to which people have allowed laziness of scp anywhere to dominate reason and sense and improvement is gob smacking. Skill issue. There's more than just eternal convenience for this one extremely lazy use case at stake.
> The agentic age is, I hope, going to question a lot of old assumptions & needs about what we want to run.
There's no reason to think that "the agentic age" will bring about any runtime efficiency. It may, perhaps, reduce development time but it doesn't introduce any new incentive to make software more efficient. It may happen, in a very roundabout way, by making consumer RAM massively more expensive which might induce customers to choose more efficient software, but it's too early to tell if this effect if happening.
There's no reason to think anything might change, that process execution and what we run is going to stay the same on and on and on. Got it. Stasis forever. Let's not consider anything else!
Well its mirroring a stupid idea back so yeah I agree it is stupid. Really stupid.
It seems ridiculous, beyond imagining to me to imagine software runtimes won't change one iota as the world starts copariticpating a bit more in computing, as we have all these agentic systems spawning. You'd have to be mad to bet on stasis. I don't know why anyone would cling to such an assumption that it's just going to tick on same as ever. That's the goofiest shit.
Software has changed and evolved and shifted forms so many times already. This seems like a very big possible impact. Maybe most people don't see and remain in their disbelief for 6 months. For a year. For two years. For five years. But I think on retrospect it's going to be quite clear that software runs very differently and that we generally did change workload running, execution, runtimes massively, in direct support of the LLM age. There's some question of how long it's apparent. But on a long enough timeline all stasis leads for rebirth. And this is a pretty high dynamic energy age now. This idea that stasis is going to win. And keep winning..on and on: I am a skeptic. I already too too much contrary evidence.
I think the biggest fault in Electron is not just that it's inefficient web tech but that it has no provision for shared instances between apps, instead foricing every app to be the one which only ever wants to use the EXACT locally bundled copy of Chromium+Node which should launch in isolation of any others.
I'm sure that's sometimes the real intended case for certain apps, as it is a value in certain ways, but I'd bet at least half the Electron apps I have running now would happily be using the same shared instance of the same LTS Chromium+Node if it were the out of the box behavior to be able to do so.
Back in the Windows era... you could embed Internet Explorer as an ActiveX control in your VB6 app and interface with it, albeit very rudimentary.
Maybe, since Electron has evolved as a somewhat common standard... the major OS providers should get together and revive this idea. The OS provides, similar to say Java JRE, a base runtime of a browser and a JS interpreter with a specified set of helper APIs to use local functionality such as filesystem access, raw networking, notifications, yadda yadda, and apps just call that runtime.
But they dropped plans to support it on macOS and Linux so it's a bit useless as an Electron replacement. Not that it was exactly a drop in for Electron - it's web based but with a different set of extra APIs. I don't think things will move as fast to something else now that apps are already built on Electron and the savings is for the user rather than the developer. It really needs to be 100% Electron compatible, just with the difference in launch behavior.
That's not really any different from what Electron does with Chrome except that it includes its own copy of Chrome instead of loading it from system32.
It's a shame common frameworks like ActiveX died, and now everything you want to embed has to be embedded in a different custom way, too.
This is exactly what Palm did in the late '00s. Just like the Amiga, it was a bit too early and kneecapped by both poor hardware (and a bad acquisition by HP).
native UIs. Platforms look and work differently and it’s annoying and dumb that every app thinks they need to either reinvent the wheel with their own bespoke UI/UX bs or to use ‘native controls’ but completely ignore any actual platform conventions and make the lowest common denominator of everything.
I'd donate nails for its coffin. Sadly, making unique apps for each platform is just too hard when you're considering the minimum output to create value.
I dream of a day I can transpile a common view/controller language into executables for multiple platforms... without it sucking.
Easy to say, and probably true, but this is "armchair quarterbacking". Did you make a better one without Electron that I can use instead, or do I still have to use the Electron one?
Feels like GUI frameworks have gone downhill after Windows Forms. Probably coinciding with everyone wanting a completely custom fancy GUI.
Not sure how APIKulture, a REST API testing GUI, is in any way an alternative for Electron, which is framework for building cross-platform GUI apps. Care to explain your thought process?
This is basically the crux of what I have been thinking about. Will some of these inefficient programs start to get optimized while we are at a plateau of memory for our desktops/laptops?
Cloudflare always had a pretty strong culture around optimisation. If you go back and read the blog there are a lot of blogs about reducing CPU, latency, RAM, etc. through software. It's one of the key features of how Cloudflare has been successful and an important part of succeeding in today's world.
And Cloudflare is making money on infrastructure margins not eyeballs (ie advertising like Google), so the incentives are well aligned for this to continue.
1) This decision was made pre-AI, where human familiarity mattered. Since the devs that would've used this were familiar with JS, that was what they were stuck with.
2) You're targeting to the wrong person. Blame the managers at Netscape for pushing Brendan Eich into creating JS, rather than letting him use Scheme as the scripting language. From there, it would've made sense to allow Scheme to be compiled into bytecode.
There's a lot of native code at Cloudflare. Just go look up the optimisations we did around crypto or compression in assembly. Or every time we use a compiled language like Go or Rust or C++.
I'd also say that when you look at JITed language like Lua and JavaScript the performance is pretty damn impressive. As with so many things it depends what you're doing.
I decided to step down as CTO because I'd been at it for a long time and the board role allowed me to stay involved without being there every single day. I wrote about my "retirement" here: https://blog.cloudflare.com/three-chapters-at-cloudflare-pro...
>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).
It is a pretty small niche of companies where compute resource efficiency on the server side has a meaningful business bottom line impact.
Everybody has a few tight loops here and there that would be beneficial but that is usually a very small selection of hot paths and it usually isn't about the money to run the code.
On the client side it's about customer delight and this is terrifically hard to measure and so many companies set themselves up such that disappointed customers are locked in so well it doesn't make a huge difference how happy they are unless they're VERY unhappy.
I used to use cloudflare dns, but the same cloudflare harassed me the entire day testing if I'm a robot. The harassment ended after I switched the dns server. See you never again, clouflare
70 comments
[ 0.26 ms ] story [ 49.4 ms ] thread700 changes per second implies 15% of all domains are changing daily, which is almost certainly not the case.
I imagine a renewal is a change event to, at least change the expiry, and renewals are constantly happening.
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.
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).
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.
The sin is this ridiculous era of every program shipping its own runtime. I'm headed for real down votes, but this is the same lazy culture that's taken over everywhere: go and rust both ship these huge statically compiled binaries.
When you are a company, you're only running a handful of different workloads/apps on any given box, so the statically compiled price doesn't bite you. But as users, going back to dynamically linking and making the incremental cost of loading an app not also have to carry the entire world with it is such an obvious return, and one that alas seems to not be in progress at all.
The agentic age is, I hope, going to question a lot of old assumptions & needs about what we want to run. Having lots of small resident little user agencies, compiled small scripts that are attributed to a user, is something I believe will happen, but I'm less convinced we'll recognize the face of it as it happens, that the tales will be told.
Tools like agent-substrate, ax, scion, are this interesting mix between agents, serverless, and kubernetes. I find it fascinating. (For hire on this.) https://github.com/agent-substrate/substrate
> The sin is this ridiculous era of every program shipping its own runtime. I'm headed for real down votes, but this is the same lazy culture that's taken over everywhere: go and rust both ship these huge statically compiled binaries.
Go and Rust are pretty efficient too, if your architecture isn't trash. If it is, they still probably are more efficient than Electron
Rust and go are somewhere on the continuum, between dynlibs and chrome, for how much private world they build for themselves. It's vastly less than chrome. But it's a lot. A lot more than what Linux distributions did for years and years and years.
Especially if you think if multiuser systems with multiple people using programs, then you have some scaling factor. Then it matters a lot a lot more than each lib has to be loaded distinctly for each process.
It's not good. It's not good for Electron, there are vastly better ways to run many apps taking a more dynlib path, and it's not good for rust or go. As nice as it is to dev like that.
Of course it's another huge problem that dependency trees are rarely shared. Go look at Class Data Sharing in Java: building the libs you standardize on (your orgs stdlibs) and there's this beautiful idea here that you should just already have some common things expected to be there. That's harder to imagine since so many programs have such different dep stacks. But imagine having a Tokio or tokio+++ that everyone can use. Some common substrate. And it can grow. https://docs.oracle.com/en/java/javase/17/vm/class-data-shar...
GP is stating that on such a system, static executables are expensive (and chrome is completely out of scope)
A Go binary can be scp'd as a single file to any server with the same processor architecture and just run. I've never encountered that in any other framework.
We've accepted this as a yes absolutely to try anything is folly excuse for decades. It was tired already and it's ridiculous today to just accept it as a hard stop wall.
The degree to which people have allowed laziness of scp anywhere to dominate reason and sense and improvement is gob smacking. Skill issue. There's more than just eternal convenience for this one extremely lazy use case at stake.
There's no reason to think that "the agentic age" will bring about any runtime efficiency. It may, perhaps, reduce development time but it doesn't introduce any new incentive to make software more efficient. It may happen, in a very roundabout way, by making consumer RAM massively more expensive which might induce customers to choose more efficient software, but it's too early to tell if this effect if happening.
It seems ridiculous, beyond imagining to me to imagine software runtimes won't change one iota as the world starts copariticpating a bit more in computing, as we have all these agentic systems spawning. You'd have to be mad to bet on stasis. I don't know why anyone would cling to such an assumption that it's just going to tick on same as ever. That's the goofiest shit.
Software has changed and evolved and shifted forms so many times already. This seems like a very big possible impact. Maybe most people don't see and remain in their disbelief for 6 months. For a year. For two years. For five years. But I think on retrospect it's going to be quite clear that software runs very differently and that we generally did change workload running, execution, runtimes massively, in direct support of the LLM age. There's some question of how long it's apparent. But on a long enough timeline all stasis leads for rebirth. And this is a pretty high dynamic energy age now. This idea that stasis is going to win. And keep winning..on and on: I am a skeptic. I already too too much contrary evidence.
But it's convenient. I can't really fault people for using it.
I'm sure that's sometimes the real intended case for certain apps, as it is a value in certain ways, but I'd bet at least half the Electron apps I have running now would happily be using the same shared instance of the same LTS Chromium+Node if it were the out of the box behavior to be able to do so.
Maybe, since Electron has evolved as a somewhat common standard... the major OS providers should get together and revive this idea. The OS provides, similar to say Java JRE, a base runtime of a browser and a JS interpreter with a specified set of helper APIs to use local functionality such as filesystem access, raw networking, notifications, yadda yadda, and apps just call that runtime.
But they dropped plans to support it on macOS and Linux so it's a bit useless as an Electron replacement. Not that it was exactly a drop in for Electron - it's web based but with a different set of extra APIs. I don't think things will move as fast to something else now that apps are already built on Electron and the savings is for the user rather than the developer. It really needs to be 100% Electron compatible, just with the difference in launch behavior.
It's a shame common frameworks like ActiveX died, and now everything you want to embed has to be embedded in a different custom way, too.
This is exactly what Palm did in the late '00s. Just like the Amiga, it was a bit too early and kneecapped by both poor hardware (and a bad acquisition by HP).
We can and we should.
I dream of a day I can transpile a common view/controller language into executables for multiple platforms... without it sucking.
Feels like GUI frameworks have gone downhill after Windows Forms. Probably coinciding with everyone wanting a completely custom fancy GUI.
If it is about a Postman/Insomnia/Bruno alternative, the answer is yes.
I use it everyday now, it is called APIKulture. It may not look as pretty, but it is insanely faster than Bruno.
And Postman/Insomnia now require login to their systems which I just refuse to do.
This is basically the crux of what I have been thinking about. Will some of these inefficient programs start to get optimized while we are at a plateau of memory for our desktops/laptops?
Client-side: lol sucks to be you
Source: I was Cloudflare's CTO.
2) You're targeting to the wrong person. Blame the managers at Netscape for pushing Brendan Eich into creating JS, rather than letting him use Scheme as the scripting language. From there, it would've made sense to allow Scheme to be compiled into bytecode.
I'd also say that when you look at JITed language like Lua and JavaScript the performance is pretty damn impressive. As with so many things it depends what you're doing.
I don't know you, but you've seemed to be pretty open and honest on HN, which is appreciated.
I worked with 2 of the cofounders at their previous company and some of the original prototype was written at my apartment at the time.
It is a pretty small niche of companies where compute resource efficiency on the server side has a meaningful business bottom line impact.
Everybody has a few tight loops here and there that would be beneficial but that is usually a very small selection of hot paths and it usually isn't about the money to run the code.
On the client side it's about customer delight and this is terrifically hard to measure and so many companies set themselves up such that disappointed customers are locked in so well it doesn't make a huge difference how happy they are unless they're VERY unhappy.
(In other words, you're not Google or Cloudflare)