Show HN: Brisa Framework – Unifying server and client using the Web Platform

This looks very smart, it’s like a SolidJS that is web-component native first and foremost. I like this framework substantially more than the previous web component systems I’ve seen that feel much more like “library” and it’s a bit choose your own adventure. I am a fan of React/Solid so I appreciate that Brisa has a lot of nice React things like tree of function components and taking care attribute vs property difference. I’m not sure how I feel about the signal implementation, it’s really unclear to me how this magic works and after reading a few pages of the docs I’ve encountered many times “doing X may break reactivity, so do Y instead”. I maintain Notion’s reactivity framework so I’m not new to this overall, but the use of Proxy magicks is always hard to understand. Perhaps with use it will become second nature and I certainly like avoiding dependency arrays but I’m left uneasy.

We are going to present Brisa 0.1, the new full-stack JSX web framework that changes the game&#x27;s rules in web development by integrating Server Components + Server Actions with Web Components + Signals, merging both worlds (server&#x2F;client).<p>Website: <a href="https:&#x2F;&#x2F;brisa.build" rel="nofollow">https:&#x2F;&#x2F;brisa.build</a> GitHub: <a href="https:&#x2F;&#x2F;brisa.com&#x2F;github" rel="nofollow">https:&#x2F;&#x2F;brisa.com&#x2F;github</a> Discord: <a href="https:&#x2F;&#x2F;brisa.build&#x2F;discord" rel="nofollow">https:&#x2F;&#x2F;brisa.build&#x2F;discord</a> X (formally Twitter): <a href="https:&#x2F;&#x2F;brisa.build&#x2F;x" rel="nofollow">https:&#x2F;&#x2F;brisa.build&#x2F;x</a>

I’m confused about server actions, what if I want to do something on the front end when a form is submitted before it’s passed to the server action (in the context of a server component)? Like frontend validation of the form, then call the server action afterwards on success. It seems like unlike the NextJS approach it just automatically knows that click handlers and form submissions are to be serialized and handled as a RPC on the backend always. So is there a way to trigger that behavior from web components? Would you pass a server action function as a prop to a web component or something and it would be translated into an RPC somehow? If so that’s pretty magical.<p>Nice stuff, looks very simple and cool in a lot of ways!

This looks really interesting, congrats! It checks a few key boxes I was always hoping to see solved in Astro, namely first-party support for web components and a clean option for HTML-partials and tools like HTMX. I&#x27;m guessing a bit on the second one, bases on the site I&#x27;m assuming routes that ship raw HTML partials works out of the box.<p>My main hesitation is RPC event handlers. That&#x27;s been the trend for a couple years now, for me its always a bit too much magic. I always prefer controlling the API URL being called, both for clarity and to ensure that URLs being called are always stable and more easily testable and reusable.

&gt; Brisa pages are dynamically server-rendered JSX components, so there&#x27;s zero JavaScript shipped to the browser by default.<p>Why is this good, why not let the client hardware do the client logic?

Congrats on the launch! Just a quick heads-up - have you noticed that the increment and decrement buttons on the main page are slightly inclined?

Here the framework author. Feel free to ask any questions about Brisa. At 15:30 GTM we will announce what it is and make it fully public.

I&#x27;m fully on board for this trend of frameworks made to be Tauri-compatible out of the box. This era of truly cross-platform app development via the web stack and is looking very promising!

Reloading that page causes content shifting. Or when on Mac the search bar also switches the displayed shortcut from the Mac version to the Windows version as it&#x27;s presumedly done on the client side. Maybe not a good look for a demo site.<p>Here&#x27;s a recording in case it&#x27;s helpful (Safari, macOS): <a href="https:&#x2F;&#x2F;img.notmyhostna.me&#x2F;Sn347jhnsgVlFwc4PZWs" rel="nofollow">https:&#x2F;&#x2F;img.notmyhostna.me&#x2F;Sn347jhnsgVlFwc4PZWs</a>

I have nothing against web components with jsx, but I really don&#x27;t like the API that defines web component as just a function, and exposes a bunch of magic effectful hooks (React&#x27;s brilliant idea). What is the point of web component if I can interface with it like a normal element aka having access to the instance?

Can someone explain the use case for these frameworks i.e. why do I do want to render things server side.<p>I understand if it was the early 2010s where mobile devices had limited power but today every user&#x27;s phone and computer is going to be more than capable of handling whatever Javascript you throw at it.

Does is support any kind of caching for server side rendering? Without caching running JS framework based SSR is slow and hard to scale in my experience.

&gt; You can capture browser events on the server, such as forms, click events, Web Components events, etc. And you can propagate them through your server components.<p>How do you process events to server components?<p>Is this the same model as web forms &#x2F; blazor (ss) where every interaction is streamed over a web socket to the sever?

Where are the background jobs and the emails? Web Platforms needs those things.

interesting idea! It seems like it uses Proxy-based reactivity for dynamic content&#x2F;updates on the client side - but can it update the reactive state from the backend or read the state on the backend?<p>Also, there are a few typos on your site you might want to fix: <a href="https:&#x2F;&#x2F;triplechecker.com&#x2F;s&#x2F;Nc9Gu4&#x2F;brisa.build?v=NUtEc" rel="nofollow">https:&#x2F;&#x2F;triplechecker.com&#x2F;s&#x2F;Nc9Gu4&#x2F;brisa.build?v=NUtEc</a>

Hi, I guess at version 0.1, Brisa is not ready for production yet. If this is the case, any idea when it would be?

Does Brisa have graceful fallback to still function (like how htmx works) in cases where JS isn&#x27;t available?

Really nice, exactly what I try to find

This looks really cool! Congrats on launching. How does Brisa compare to, say Remix? Can they be used together or are they competing technologies? Can I use Brisa with React code or just Web Components?<p>I am an old Polymer fan and so I love to see any developments in that space. The site is nice and worked well for me on mobile.

So is this Remix (React Router) without using React?

YAJF - Yet another Javascript Framework.

Awesome 0.1 release. Brisa simplifies the SSR complexity with a focus on Web Components. Defines server and client data flows using the power of signals. With minimal overhead and a straightforward structure. Brisa has a short learning curve, high efficiency, and a clear approach to data management.