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's rules in web development by integrating Server Components + Server Actions with Web Components + Signals, merging both worlds (server/client).
Can someone explain the use case for these frameworks i.e. why do I do want to render things server side.
I understand if it was the early 2010s where mobile devices had limited power but today every user's phone and computer is going to be more than capable of handling whatever Javascript you throw at it.
especially with mobile there are millions situations where your internet is bad, slow and patchy. you have A LOT of people using low-end devices in battery saving mode so also throttling the already bad performing devices – read this series if you need to understand why doing server side rendering is an exercise in accessibility https://infrequently.org/2024/08/the-landscape/
> 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.
How do you process events to server components?
Is this the same model as web forms / blazor (ss) where every interaction is streamed over a web socket to the sever?
how about when the 1mb javascript bundle failed to download because your bus entered a tunnel? labeling users idiots is really really not OK, but ultimately hurts your employe and your product bottomline. Check this article https://infrequently.org/2024/08/the-landscape/
I typically use a web application framework on the server to provide critical functionality like authentication, authorization, object relational mapping, etc. For example, I’m frequently using Django for server-side web application development due to its comprehensive features. How can Brisa integrate with a conventional server side web application framework (Rails, Laravel, etc.) to handle some of the user interface components while still leveraging the power of the web application framework?
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?
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.
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.
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's rules in web development by integrating Server Components + Server Actions with Web Components + Signals, merging both worlds (server/client).
Website: https://brisa.build GitHub: https://brisa.com/github Discord: https://brisa.build/discord X (formally Twitter): https://brisa.build/x
is this more react garbage? or what?
No, it's a new alternative to React, Solid, Svelte, etc.
Meh uses the same crap templating as react.
JSX is not a templating language. It is a functional DSL
It’s not a DSL. It’s an extension to JS to write HTML like code to describe a UI. It’s basically glorified templating.
how does it compare to primatejs?
Interesting. I'll have a look then :-D
Can someone explain the use case for these frameworks i.e. why do I do want to render things server side.
I understand if it was the early 2010s where mobile devices had limited power but today every user's phone and computer is going to be more than capable of handling whatever Javascript you throw at it.
> why do I do want to render things server side.
API key secrecy, SEO, etc
especially with mobile there are millions situations where your internet is bad, slow and patchy. you have A LOT of people using low-end devices in battery saving mode so also throttling the already bad performing devices – read this series if you need to understand why doing server side rendering is an exercise in accessibility https://infrequently.org/2024/08/the-landscape/
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?
For whatever reason, I thought this was by design.
:-) I was expecting the counter to be degrees and to change the inclination. It didn't. The disappointment.
It wasn't just me then. I thought I was going mad!
> 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.
How do you process events to server components?
Is this the same model as web forms / blazor (ss) where every interaction is streamed over a web socket to the sever?
Does Brisa have graceful fallback to still function (like how htmx works) in cases where JS isn't available?
Anyone who disables JS is probably not someone you care to have on your website. Only idiots turn it off these days.
how about when the 1mb javascript bundle failed to download because your bus entered a tunnel? labeling users idiots is really really not OK, but ultimately hurts your employe and your product bottomline. Check this article https://infrequently.org/2024/08/the-landscape/
Bad examples are bad.
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 typically use a web application framework on the server to provide critical functionality like authentication, authorization, object relational mapping, etc. For example, I’m frequently using Django for server-side web application development due to its comprehensive features. How can Brisa integrate with a conventional server side web application framework (Rails, Laravel, etc.) to handle some of the user interface components while still leveraging the power of the web application framework?
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?
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.
Where are the background jobs and the emails? Web Platforms needs those things.
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.