Coding With David

  Every few weeks, the same argument pops up in developer forums and team meetings: "Why bother mastering Blazor when AI can just write the code for us?" It’s an understandable reaction. Tools like GitHub Copilot, Claude, and Gemini can pump out hundreds of lines of working syntax in seconds. But this perspective misses a fundamental shift: AI hasn't eliminated the need for expertise. It has just changed where that expertise delivers value. Deep knowledge of the Blazor ecosystem is actually becoming more valuable, not less. AI can handle the mechanics of writing code, but you still have to engineer the solution. The Limits of Syntax Search Engines Think of AI as a hyper-fast assistant with an encyclopedic memory for APIs and zero tolerance for boilerplate boredom. It excels at execution, but it operates in a vacuum. It doesn’t inherently understand architectural trade-offs, production telemetry, or when a quick-and-dirty fix will evolve into a technical debt nightmare. Y...

  A user opens your Blazor application in one browser tab. Then they open a second tab, perhaps to compare information or keep two parts of the application visible at the same time. They change something in the first tab. Nothing happens in the second tab. This is expected. Each browser tab has its own page, JavaScript context, and Blazor Server circuit. Even though both tabs are displaying the same application for the same user, they don’t automatically share live state. You could solve this with SignalR, a server-side notification service, or a distributed messaging system. For many applications, however, that would be far more infrastructure than the problem requires. When the communication only needs to happen between tabs from the same application in the same browser, the browser already provides a lightweight solution: the Broadcast Channel API . In this article, we will examine: What developers sometimes mean by the “Broadcast API” What the Broadcast Channel API actually is ...