61–70 of 97 posts
It's like beating a dead horse. React is the literal worst of all the modern JavaScript frameworks and yet that's what everybody insists on using. Vue is light years ahead of it (and will be even further ahead when the new Vapor mode is released in 3.6). Svelte is ahead. Solid is ahead. Heck, even Marko is ahead.
I am a react developer. For past few months I am working in vue and I Just dont see any benefits
It's like beating a dead horse. React is the literal worst of all the modern JavaScript frameworks and yet that's what everybody insists on using. Vue is light years ahead of it (and will be even further ahead when the new Vapor mode is released in 3.6). Svelte is ahead. Solid is ahead. Heck, even Marko is ahead.
Totally agree. It can be made better if you write it using non standard patterns - but the community is so dogmatic you'll get laughed out of the room. All of my personal react projects use the MVC/MVVM architecture and are so much easier to work with export class AppViewModel { @rx accessor message = new TextField() } export function App() { const vm = useViewModel(AppViewModel) return {vm.message.value} } Makes it…
I understand nothing of frontend, and never even saw what React looks like, what is this supposed to be? Is it compiler--written in Rust--of React whatever to actual Javacript with DOM calls?
The Rust part is the runtime engine that executes your React code on the server. Think of it as a faster alternative to Node.js for running React Server Components. You still write normal React code, but the server-side execution happens in Rust instead of Node.js, which gives it massive performance gains (46.5x higher throughput than Next.js).
It handles routing, server-side rendering, and serves both server components (rendered on the server) and client components (interactive JavaScript sent to the browser). The output is still HTML + JavaScript that runs in the browser—just generated much faster.
If anyone’s exploring Rust + React, I’ve been building something similar on the rendering side. react-vello [1] exposes Vello (a Rust GPU renderer) as a React renderer via WASM + WebGPU, so you can draw shapes and text declaratively while Rust handles the rendering in the browser. [1] https://github.com/mblode/react-vello
I've dreamed of someone taking React and making it somehow embeddable to any back-end programming language without a performance hit, so you can blend it with .NET, Go, Django, etc and it would run either natively or alongside said platform. This is impressive.
ok so I actually like this, but the description and documentation in general are terrible "rust-powered" meaning it uses rolldown to bundle the javascript, that's fine, but it's a weird thing to highlight, it's confusing for people that aren't super familiar with vite and might think this is a rust framework from the docs "one of rari's superpowers is seamless NPM package integration" this makes me think the docs are…
You're right about the messaging being confusing, I've been writing everything solo, so I'm definitely open to PRs that help with the copy. To clarify: "Rust-powered" refers to the server runtime itself, not just the bundler. The actual HTTP server, RSC renderer, and routing are all written in Rust (using an embedded V8 engine to execute your React components). It's not just Rolldown doing the bundling. On the npm in…
Earlier quoted context omitted.
You're right about the messaging being confusing, I've been writing everything solo, so I'm definitely open to PRs that help with the copy. To clarify: "Rust-powered" refers to the server runtime itself, not just the bundler. The actual HTTP server, RSC renderer, and routing are all written in Rust (using an embedded V8 engine to execute your React components). It's not just Rolldown doing the bundling. On the npm in…
[flagged]
Earlier quoted context omitted.
[flagged]
Where did I say they were rushed with an LLM? I've spent countless hours on the framework, and the docs, and have been clear that I'm open to PRs to help with the copy. This isn't something that was rushed in the past few days, I have spent over a year on this project, with it being public for ~6 months. Not sure what your deal is, but respectfully, touch grass.
Earlier quoted context omitted.
Where did I say they were rushed with an LLM? I've spent countless hours on the framework, and the docs, and have been clear that I'm open to PRs to help with the copy. This isn't something that was rushed in the past few days, I have spent over a year on this project, with it being public for ~6 months. Not sure what your deal is, but respectfully, touch grass.
What's with this 'touch grass'. Is this the new valley jargon?