You’ve probably noticed that building a simple web app today requires a 400MB Node install, a Kubernetes cluster, and three AWS buckets just to render a button. We’ve been sold a lie that scale requires suffering.
Then someone dropped a project called Radio Balkan. It aggregates 500 live radio stations into a single HTML file. No backend. No API. No React. No ads. Just a guy, a curated list of public stream URLs, and the browser’s native <audio> tag.
The web wasn’t broken. We just forgot how to use it.
If a Silicon Valley startup tried to build this today, they’d raise $5 million to construct a ‘cloud-native audio aggregation pipeline.’ They’d hire a team of ten engineers to manage microservices, handle stream caching, and optimize the CDN. And it would still go down on a Tuesday because someone misconfigured a Docker container.
Radio Balkan doesn’t do any of that. As the creator noted, the streams are the stations’ own public broadcasts. The file simply plays them client-side, making the exact same request your browser would make if you visited the station’s website directly. There is no rehosting, no recording, no proxying. It is pure, unadulterated client-side execution.
We don’t have a scaling problem. We have an over-engineering problem.
We’ve been conditioned to believe that if an app doesn’t have a dedicated server, it isn’t ‘real’ software. But the browser is an incredibly powerful runtime. It can parse JSON, render canvas, play audio, and connect to WebSockets natively. Yet, we insist on wrapping every native capability in three layers of JavaScript abstraction.
Strip away the tech-bro bullshit, and look at what this single file actually accomplishes. A kid in Toronto can instantly tune into a station in Belgrade. A grandfather in New York can hear the local news from Sarajevo. No login walls. No premium subscriptions. No tracking pixels. Just the music, instantly.
Simplicity isn’t a lack of features. It’s a lack of arrogance.
The next time you’re about to npm install a massive framework to solve a basic content delivery problem, look at Radio Balkan. The web is already capable of magic. We just have to stop getting in its way.
FAQ
Q: Isn't relying on the stations' infrastructure unreliable?
A: Yes, if a station's server crashes, the stream dies. But that's the exact same reliability you get visiting their website directly. No middleman caching means pure, unmediated audio.
Q: What's the practical implication for developers?
A: Stop reaching for frameworks by default. If a project only needs to aggregate public links and play them client-side, a static HTML file is infinitely more scalable and cheaper than a cloud architecture.
Q: Is this approach legally risky?
A: Since the file doesn't rehost, proxy, or cache the streams—and simply uses the same public URLs the stations broadcast on their own sites—it sidesteps the massive legal headaches of traditional aggregators.