The smaller, simpler, easiest to learn, lightweight is my first choice.

Where is htmx?

Funny I didn't think the code was beautiful. It doesn't do much so not concise and not easy to ready because it is functional

6:42 Svelte small ecosystem? In 2025? I would say it has less trash in ecosystem, but it's not that small. Above average. Svelte 5 breaking changes? Not to mention that those changes has backward compatibility??? So where are disadvantages of Svelte? That no businesses picks it? :D

Nice Video, one question; how do you create those code snippets like in 4:00? Those VScode minimap like style?

Forget all this BS and just run go

ridiculous - its a common throwaway phrase "be comfortable in all frameworks " there are only 24 hours in the day - learn 2 or 3 and learn them well and if one of them happens to be react that's enough on its own for anyone

Nothing is perfect that's why that! Anyways Thanks for your points!

So you are saying no one use nextjs??

haven't looked back from Flutter

Call me oldschool but I have a weak side for EmberJS. It’s quite complete, convention based and has a slow and steady release cycle. It’s not the shiniest thing but it’s good enough for Apple, LinkedIn and Hashicorp.

htmx emerging ajax. I'm in.

Well, I absolutely wouldn't use anything else for enterprise apps than Angular.

.. just use Vue3 + TS + composition api (script setup) + Pinia and you will have least complexity compared to most other frameworks. It was made that way for a reason. But if for some reason you want old vue2 or vue3 with oprions api there is no problem .. it's just bad with TS and too verbose for my taste.

Vue 2 is long end of life, there is no segmentation. Also the argument against Vue is the exact opposite. The whole Vue and Nuxt ecosystem has provided much more long term support than React and Next could ever dream of.

state of JS frameworks for me is that I am moving to Elixir + Phoenix + Liveview .. gbye It's technically moving to backend + frontend with superpowers

Just stay with Nuxt, it is great and the ecosystem is in contrast to React/Next focused on maintainability and longevity.

My points: * Biggest React weakness: no signal based state management (have to use third party libraries like Zustand or Jotai) and 200 kb of parsable JS (react router and/or nextjs) in a simple hello world * Biggest Angular/Vue/Svelte weakness: not using JSX and having their own "Custom Template Language" that completely changes each major version and forces you to rewrite everything

3:10 This bit is wrong. React does not use dirty checking.

Am I missing the point of why DaisyUI is considered good? Some components don't even have logic behind them; you need to implement the JS part by yourself. When you use the Toast component, you need to write setTimeout to disable it, etc. ChakraUI was much, much better. Or am I using DaisyUI wrong?

I tested vite and I love it more. At least i can escape from the complexity of nextjs which can be unnecessary for small apps.

Clay is the best UI framework.

I switched from java to go after many years of experience using java. And I think backend is backend. What exact tool are you using to build backend is not that important to be honest.

7:00 Thankfully, Svelte 4 to 5 had relatively few breaking changes that weren’t backward compatible. For example, you don’t have to use the $effect rune, you can stick with v4 syntax if you want. The backward incompatible changes that did occur of course make sense, considering it’s a major version. If you’re doing things under the hood like I was with my library, there might be some minor differences. Like, how you and instantiate a component is a little different. Everything _is_ pretty well documented though, so transition should hopefully be pretty smooth!

So apart from React, everything is fine.

drawback of GenAI is they are trained on older data so it will hallucinate and give incorrect output result of that people choosing frameworks who is supported in by the GenAIs

how does it compare to c++?

after jquery they were all shite

I went out of my comfort zone late last year, decided to try my hand at Astro, quite liked it, took one look at React and its horrible syntax for developing pages, and ran in the other direction. You will never be able to convince me that sending the entire thing to the frontend to be hydrated is the right way to do it. SSR has and will always be the right way to do the kind of software that I deal with at work, which in this case is a point of sale. Even a simple website that gets data from a database is better off as SSR.

Nice vid. My favorites are: Angular for company projects and Svelte for personal projects.

"AI advancements..." hahahaha ok this is an unserious channel for unserious people

At this point, the entire JS ecosystem feels like a marketing stunt to sell some other cloud service to host said JS. Development shouldn't be this overcomplicated.

>qwik qwik plus ai pretty good

Props....Effective clickbait

My professor when I asked him for advice in building something: "Just use PHP." Best advice I ever had.

still using old jquery .. only click the video to see the suspicious dog :p

HTMX is a joke. There are better tools if you need what HTMX does.

There is no jobs for Svelte. The maintainers don't care about your comments. They do whatever they want without consulting with the community. There are tons of unsolved issues with Svelte and SvelteKit.

3:04 -- i burst out laughing at "react is not reactive"! ...i had to explain that to my jr dev, which is why i only run sveltekit 5 now. Svelt reactivity with a $ sign will alway equal more $ signs in my bank account.

Svelte 5 has the same compatibility issues. You can't use the old packages because they are not compatible with Svelte 5, and you can't use the new packages because they are not ready yet.

Svelte template syntax is awful. React is just JavaScript. Svelte is a made-up syntax that isn't even properly tape-safe in your code editor; In Svelte, Snippets are different than components meaning you need to learn a new thing that everything about it is different. Whereas in React, you don't have a new concept to grasp. The if/else etc blocks in Svelte are super ugly and hard to write whereas Angular does this better with a more JS-like and clean syntax. If you are using an icon library in Svelte, your site will get extremely slow and to solve it you would need to import the icons individually rather than using an index file to easily import them.

The wort part of JS frameworks is that we now have Senior {pick your FW here} devs, who are junior JS dev at the same time :/ (Almost) No one cares how JS or browser works, just deep into their FW.

3:27 Dependency arrays are great. Svelte doesn't have this, and it's a big pain point; everything in the $effect automatically becomes a dependency, and you can easily find yourself in an infinite loop and not even know about it until you realize your website is acting weird.

People who are interested in learning Svelte don't; it's filled with issues, missing features, etc. Svelte maintainers are out of touch and the new reactivity system is garbage; You don't even know what is reactive and what is not without looking at the declaration; No type safety.

Absolute bloat. Why not just learn how to write vanilla css3 + js without a crutch, and in a way that is output like typescript. They are crutches for ppl that don’t even understand how the V8 Engine works in browser and c++ engine for css/animations.

the ONLY reason why react is alive is because NEXT.JS and every ecosystem plugins like tanstack query, react is absolutely dumb and every time I switch from Svelt to React I feel like going backwards and fighting with useeffect and state batching. ALSO the fact that Vercel (the literal lifeline company for react) onboarded Svelt's creator and also have free Svelt courses, tell's you that even people who know react inside and out want growth for other frameworks TL;DR: REACT DUMB, USE LITERALLY ANYTHING ELSE

great video although i should mention that "x thing would be overwhelming for new comers" is a bad excuse to downgrade angular or any other framework.

Anyone saying that React RSCs are more complex than the old SSR models doesn't understand them yet. Switching to RSCs using NextJs app router made everything in the stack so much easier. Instead of using 5 libraries for managing different complex steps of getting and syncing data between FE and BE, you can now write it all yourself using very few primitives. And I've used app router with RSCs in basically all of it's "versions" (and yes it's still very much changing and evolving) and it just keeps getting simpler with every major update (such as the "use cache" with PPR and dynamicIO).

You really don't need memes and stock footage every 5 seconds, it feels so cringy.

Thanks for video. It's a great overview. I want to mention, that all those issue of the framework arize only in specific situation - when the app is already huge. And somehowe people still are lokking for another framework to solve it. And they skip over micro-frontends. A simplest version of which is separation by pages and connection of a js file. Once app is splitted - there is no difference which framework to use. And business can safely try new tools and rollback is needed. And it doesn't require webpack module federation - it's already an optimisation. So from all this video only Astro makes sence as it suports multi-framefork solutions.