91–97 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
Earlier quoted context omitted.
I hate React, but Vue never seemed much better. What is better about it, in your opinion?
no weird rules of hook. automatic dependency tracking. no stale closure gotchas, no running hook 1000 times cause you made a mistake. Better update performance by default. definitely better dev tools
Earlier quoted context omitted.
I never "learned" react because the "create react app" would literally never install for me in the early days. There were literally so many dependencies I never got it to build as a novice, I tried svelte everything worked and I got to spend that time building. I can only speak for Svelte, in Svelte 3/4 it was so dead simple that I built my first basic webapp with 0 javascript, css or html experience in 3 days. By we…
Use Vite. It was a misstep by the React team to continue to recommend create-react-app long after it was deprecated, but Vite is what's commonly used today.
Earlier quoted context omitted.
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…
Hi do you have some examples or repos you'd be comfortable with sharing? This looks interesting.
There are some examples under: https://github.com/alshdavid/mvvm/blob/main/examples/basic/i...
Earlier quoted context omitted.
How is a viewmodel better? It's way more skipping around in the codebase to find the parts you actually care about
- Allows you to use async/await and generators (useful for pagination/infinite scroll) - You can test the view model independently of the rendering logic - Dramatically reduces the code that lives directly in the component (it's only TSX) - Allows for better abstractions and state management (services) - Clear path to leveraging threads in front end applications - Simple "visual" components (like , ) don't need view…
Earlier quoted context omitted.
Hi do you have some examples or repos you'd be comfortable with sharing? This looks interesting.
I put the library here: https://github.com/alshdavid/mvvm There are some examples under: https://github.com/alshdavid/mvvm/blob/main/examples/basic/i...
Earlier quoted context omitted.
I can only found this benchmarks https://github.com/rari-build/benchmarks
interesting, but would certainly be good to see an apples to apples benchmark of rari vs node/deno/bun for the same app, I would imagine the goals of the runtime are not to be a general runtime like those others, but it would still be good to see if it performs better