---
title: "Comment by Eugene Bekker on \"7 Practical Ways to Write Rich Frontends without Javascript today\" | Hashnode"
description: "I was a bit confused by your analysis of method #4 compared to #3, #2 and #1. From what you described, it sounds like #4 (Blazor Server) is fundamentally the sa"
url: "https://hashnode.com/posts/7-practical-ways-to-write-rich-frontends-without-javascript-today/61523dfecf735d72249a8ce5/comment/626988f1aedfbdb0ce1a6422"
---

[Discussion](https://hashnode.com/posts/7-practical-ways-to-write-rich-frontends-without-javascript-today/61523dfecf735d72249a8ce5)

Comment [7 Practical Ways to Write Rich Frontends without Javascript today](https://hashnode.com/posts/7-practical-ways-to-write-rich-frontends-without-javascript-today/61523dfecf735d72249a8ce5)

[Eugene Bekker](https://hashnode.com/@ebekker)

[Apr 27, 2022](https://hashnode.com/posts/7-practical-ways-to-write-rich-frontends-without-javascript-today/61523dfecf735d72249a8ce5/comment/626988f1aedfbdb0ce1a6422)

I was a bit confused by your analysis of method #4 compared to #3, #2 and #1. From what you described, it sounds like #4 (Blazor Server) is fundamentally the same as Livewire (PHP), Hotwire (Ruby) or Liveview (Elixir). The only difference I can tell is that it's the C#/.NET equivalent of all these same approaches.

They're all server-managed, HTML diffing mechanisms served over WebSockets. Did I miss something in your descriptions? Why is #4 exclusively a bad choice for public-facing apps? Wouldn't the other 3 suffer the same problem from huge resource consumption on the server-side per user connection?

[Jeremiah Chienda](https://hashnode.com/@Liwu)

[Aug 23, 2022](https://hashnode.com/posts/7-practical-ways-to-write-rich-frontends-without-javascript-today/61523dfecf735d72249a8ce5/comment/626988f1aedfbdb0ce1a6422#reply-63051921750cde48abba8cfc)

Yeah, you're absolutely right - the last 4 could be categorized as variations of the same fundamental idea: they all send HTML deltas to the browser through some _live_ connection
