Every time I load SydneyMusic.net I get a small rush of glee, because it's *so* *fucking* *fast*.
That's not because of anything particularly special - it's about what it doesn't have: the website is designed to ship with zero JavaScript rendering in the client. It's completely static, generated at build, and any content change trigger a build.
Static Site Generation isn't super novel, but people typically use it alongside megabytes of front-end code. SydneyMusic doesn't have any of that: in fact it only has two lines of JavaScript. And they're not minified!
SydneyMusic.net is so much simpler than the gigantic, complex, dependency-laden monstrosities that are so common in today's constantly evolving technology world.
It also makes ecological sense: the environmental footprint can easily be made close to irrelevant because of its lack of "grind" in terms of compute. No ad tech, no data platforms, no analytics platforms, no grossly inefficient chatty REST calls chirping away in the background.
The maximum amount of traffic required for the audience we need to service (the population of Sydney), could probably be hosting on extremely minimal equipment, both in terms of computing and power requirements.
It's so elegant. I love it.
With that said, it needs to be acknowledged that SMn is an incredibly simple product by design - simplicity is a core principle of the project. A lot of products require more complexity (or do they?), but nonetheless I think this comparatively extreme example points towards the impact and effectiveness of the internet at its most elemental: HTML and CSS. And hyperlinks. (And yes, no algorithms)
Do we need to start thinking about how our engineering impacts the planet? I think so. In a cloud-native world we can call a single API and have an eye-watering amount of CPU (and GPU...) power provisioned within seconds. The minerals, metals and other natural resources that feed the cloud of today is abstracted behind elegant, simple, automatable code. We don't actually "feel" how much power our code demands.
In corporate environments, our cloud bills now run into the millions. And they're only increasing (and will accelerate with AI).
I fear we've got sloppy. A casual "npm install" on a boilerplate project, a keystroke or two, and suddenly you've got 100 dependencies. Have you profiled how much data a single webpage request pulls these days? Websites of today are optimised for speed, but not for efficiency.
For example: why are Electron projects so fucking slow? Why do we need supercomputers to use chat apps and talk to our friends? Could we save the planet by using less computing power?
I really, really think so. I strongly commend giving it a moment or two's thought.