Kweb: A new approach to building rich webapps, in Kotlin
I&#x27;ve been lucky to observe KWeb since its earliest days and some of the missing context on the website, I think, is that the author takes the position that the way we build webapps is fundamentally wrong.<p>From his perspective it seems that the &quot;division&quot; between frontend and backend are an implementation detail that accidentally became of defining feature of how we write software for the web.  Websockets are a way to correct this by making the delivery channel dumb and universal while focusing application development in a single software architecture.<p>It reminds me of the principle of brutalist web design (<a href="https:&#x2F;&#x2F;brutalist-web.design&#x2F;" rel="nofollow">https:&#x2F;&#x2F;brutalist-web.design&#x2F;</a>).  Brutalist design, while not completely beautiful, makes me ask, &quot;What were we trying for when we first made HTML?  Does the tool really fit those goals anymore?&quot;  While I hope that KWeb grows up to be something big, at a minimum it asks a lot of questions about why applications for the web are architected the way they are.