Svelte rocks man. Easy to learn and follow. It should be used more for company projects, that way its full potential can be tested, I am sure devs would love it in their company projects.
@@loopje because react main goal is rendering the ui and not other aspects such as form creation which you can use things like formik or react hook form, or for network requests you can use axios, im still kind of new to this too with only 5 months in so not too good at explaining this stuff
@@loopje its a library React is concerned only with rendering the ui which leaves many things to each project to put together.....e.g Redux for state management
@@Kinyanjui_765 but then maybe avoid Redux unless it's absolutely necessary. There's other far simpler options that get the job done just as well if not better without any esoteric terms.
Don't forget Solid. It's intentionally new and delays features in order to make sure to choose the best ones. It's like React syntactically but with changes to make it easier for beginners. It's also one of the fastest front end frameworks. It is also seemingly the fastest npm-integrated framework
Fun fact: for most of those "frameworks" you need another meta-framework to build serious apps. For example, there is Next for React, Nuxt for Vue, and Svelte Kit for Svelte. Which really raises questions about how much of a framework those things are. Angular on the other side really is very framework.
Svelte is nice, we had a very close 4 month relationship. They made a weird choice with the directory/file thing in one of the last update, but that's not really a problem.
Svelte doesn't scale. It lacks proper solutions for managing shared state and derived state. It's also not very transparent, acting like a black box. Much like vue and angular
@@lennart5738 I doubt you tested the new vue 3 composition api before saying that. Much more es6 Js oriented and typeScript friendly. And how is React is less a "black box" anyways
@@Boobouh Composition api look nice I hadn't seen that before. I last used vue in earnest when it was v2 yeah. But it still has their own non-standard templating language with pseudo-html directives like v-for and v-if. it's much less transparent what happens behind the scenes when you do that. React is less of a black box because you know exactly how the ui updates work because calling setState just triggers the function to run again. easy, simple and transparent. no proxies, no weird template processing of pseudo-html. it forces you to think correctly about your state and conditional logic. Even JSX is an extremely simple processor that doesn't do much more than simple regex replace would do. hooks make it so easy to micromanage your own component performance.
@@lennart5738Shared state in Svelte is covered by stores and contexts. Derived state is through… wait for it… derived stores. Not transparent? Go ahead and look at the code the compiler generates. It is substantially similar to the code you have written, just with some instrumentation sprinkled in, especially in Svelte 4.
Wrong! If you keep using what everyone else is using the evolution stops. Vue would not exist and it has gone past React, mainly because React is just a side project to Facebook.
Yes and think like this: if everyone learns the most popular then there will be the most people applying for those jobs while the job offers of the not so popular frameworks are more likely to get.
I really like Svelte because the code looks like HTML with some extra syntax to integrate JavaScript. It does use some JS syntax differently, for example labels (`$:`) and `export`. Seriously. All you need to do is write the layout, the CSS (you can use Tailwind if you want) and then JS to integrate with other components.
My first framework was React(library) and now I'm using Angular, And one thing I'm absolutely sure about is that React is complete garbage comparing to angular
Kinda agree, the only gripes I ever had with Angular is: 1. Its opaque tooling (build, test, dev server, etc), which caused it to fall behind in adopting things like Vite, Vitest, Jest, ESbuild, etc. 2. The unnecessary abstraction/distraction of NgModule. The only module systems should be ESModule. Luckily this is no longer the case with standalone components and simplified dependency The core part is just amazing, and will even be more amazing when you can use Signal (+ RxJS interop) for declarative state management.
My advice: choose one among most famous if you're looking for a job or if you're an indie developer, pick any one which you like and the main advice is once you choose stick to it, don't look anywhere else
After years, I gave up all frontend work and focused only on backend. I hate frontend coding. I also started my journey with iOS development, which I really appreciate.
@@alejomakevids You know frontend is known for web. I was going to type web frontend but forgot because we used to call it like this. Just check you username. 😀 It’s the JS hell you know.
The problem is that learning a new framework every single time just to incorporate it into projects will take a toll on your the organization especially if theres a tight deadline. Plus you have to go through the curves of learning it. That's one of the reasons why most companies will require people applying to have atleast have some proficiency in a particular framework
I use both react and svelte. From my experience, svelte is much much better than react and has a great developer experience than any other framework out there
I admire you for the last part. Whatever you choose is the best framework. That is absolutely true. I hate it when people say this is the best and you must use this. Because all I learned over the past few years in the industry is, there is no such thing as called silver bullet. Everything has its' pros and cons. It's all about how you make use of it.
React + anything = pain. Svelte is what Kotlin is to Java, what Go and Rust are to C++... Cleaner, easier to work with, less error prone due to higher simplicity... I'm not saying React is bad, but it's not the best, shich implies there are better frameworks. Svelte and Vue are certainly among them.
@@shapelessed While I really like a lot of ideas behind Svelte I think this comparison fails, because Svelte is not a different programming language and compiler, but Go and Rust are compared to C++. Kotlin is a bit of a special case because it also uses the JVM, but to my knowledge in normal cases, it does not compile to Java source-code.
I tried learning React... And I say "tried" because its performence, size, overcomplicated and ugly nature of JSX made me give up after just a few days... Then I found Svelte and managed to learn in a day what would take months with React... It's easier, cleaner, faster, lighter and generates smaller packages than React... I was the lucky one to pick the framework our team is working with and they're all thanking me for it to this day.
very true but i think the learning curve is what scares people away more so the ever dreaded RXJS but all i can say once you master angular there's no going back once heard a senior dev say angular is like black coffee without sugar at fiurst your taste buds will not want but as soon as they get used to it they will not want you to stop cheers
@@wilsondouglas1546 Yes. Angular comes with batteries included, this means it has a lesser ability to improve over time. Like how React and Redux used to be almost synonymous but state management has been massively improved over the years and no new project uses that. The main issue with angular is twofold: 1) They force you to use too many abstractions out of the box (typescript, rxjs, DI, etc.) 2) They hide state management away behind proxies and decorators which makes state management less transparent, resulting in people writing less performant code. Angular also uses their own weird directive system instead of just giving you javascript in your templates which is both less intuitive and less powerful. Angular also has it's own very specific tooling which means it does not benefit from the past few years of optmiizations in bundlers (vite, parcel, esbuild, swc, turbopack) resulting is a slower development workflow (see: github.com/vitejs/vite/issues/543) Angular is by design, stuck in the past. it is the modern day jQuery. My recommendation is, if you like writing your components OOP-style with custom template directives, try out vue. vue is faster, better supported by modern tooling, more modular and easier to learn If you prefer writing functional components that are self-contained though, consider using React. React with react-hook-formand react query is a nice starting point for a modern functional javascript app
@@lennart5738 thanks for the reply but firstly we can agree all that you've said is a very subjective opinion and not objective 1. in this sense that its not factual coz if it was then there ought to be a list of things by which you qualify something as legacy and in this instance you havent provided a gloabal list of univesally accepted standards to call something obsolete quick example like the versioning of ECMA there are set standards accepted to know the diffrence between ECMA versions 2.again this soildifys point one in this senses you say that angular forces you to do things in a certain way granted you wouldnt want that well to that i will say more power to you but is there a chance even in the miniutest form that there are actualy developers who like things that way and i believe you would say yes and to that i say that's a matter of prefrence and to you it seems you dont like that wich is still a good thing but is not a fact 3.again you say state management is hidden behind proxies and decorators this just gave me a smile and makes me wonder if you really have used angular state managment isnt hidden behind a stone wall that you cant access and see what is being done.we have multiple libraries by which you can have state management from simple libraries such as akita and observable-store all the way to complex things such as ngrx & ngrs you can have state mangement at component level to state managment globally depending with your needs at the time Finally you say angular is the modern day JQuery gave me a good laugh to this that i will say is just an opinion make it stick with objective reasonalbe points earn that statement let me give an example we both have cars you have a sedan and i have a truck/lorry (dont know what part of the worldyour from) they both use diesel (diesel being metaphoric for JS) your carcan do 0-60 in lets say 6 sec my track does 0-60 in 20sec but my track can carry way much weight and has more power output from the engine than your car hence different cars for different works to conclude i think we can both agree that the end user doesnt really care what tool we use as long as they get a great user experience and a real world effecient app be blessed
@@wilsondouglas1546 the exact reason why i went with angular is because every comparison just talks about how easy react is ( implies surface level features ), how many users it have ( implies high competition on the job market - you lose your uniqueness), and how its small is size and really fast (this is the best thing i agree about in react).
SolidJS is even faster than Svelte and has syntax similar to React. Also, Astro is pretty cool, it allows you to use multiple frameworks and libraries in one application
We have been using Svelte And Sveltekit the last year or so at our company and it has been amazing! I can highly recommend svelte and sveltekit. SvelteKit is also soon going 1.0!
If I use Vue for building tools today, will I be better off switching to Svelte? I don't rely on Vue specific libraries. Reactivity and data store is very important for me. Please only reply if you have tried them both.
React is a good option to understand how libraries/frameworks work (and to pay the bills). Vue is a good option if you want to learn Chinese, it has an original Chinese docs. Svelte is simply fun to use, and it combines all the goods from it's predecessor.
i actually believe that if you built you app in vanilla js , you would be more comfortable with you work than with a framework., the close you are to the source is alway better.
Yeah there's no lack of clear Documentation for Vue. It's the best. But then again all frameworks have the same weakness and that's being frameworks. They inevitably get too abstract complicated and enforce bad methodologies. It's the tradeoff between consistency and freedom.
@@wafi5576 I would say so yes but I can’t confirm as I don’t work with react as much as someone who does. I use Angular for work and I’m based out of Florida. Depends on the area too
Svelte rocks man. Easy to learn and follow. It should be used more for company projects, that way its full potential can be tested, I am sure devs would love it in their company projects.
Yes! I was going through it today and I loved it, I felt like using svelte is much easier than react
@@sreesen3159 Keep it up 👍
Any good resources in particular?
@@Antassium It's official tutorials (both Svelte and SvelteKit).
Angular: Am I a joke to you?
yes
Yes
Yes, in fact it is a joke
Yes, in fact it is a joke
Yes ,indeed it is
Hands down, svelte deserves more.
Straight up man! Easily the best framework to dive straight into from learning vanilla js.
in before "rEaCt iSnT a FrAmEwOrk"
Why not? I’m new
@@loopje because react main goal is rendering the ui and not other aspects such as form creation which you can use things like formik or react hook form, or for network requests you can use axios, im still kind of new to this too with only 5 months in so not too good at explaining this stuff
@@loopje its a library React is concerned only with rendering the ui which leaves many things to each project to put together.....e.g Redux for state management
@@Kinyanjui_765 but then maybe avoid Redux unless it's absolutely necessary. There's other far simpler options that get the job done just as well if not better without any esoteric terms.
@@Kinyanjui_765 React Hooks, Context API
"What's the best framework?"
"Every framework has pros and cons, so no metter what option you choose, its Solidjs"
Svelte is fun. Make you want to code and make things.
True. It's easy to make things.
My first experience was with react but then I discovered svelte
Same here
same, I fell in love with svelte
Which to choose? Vue or Svelte?
Astro , so you get it all :D@@theworldismine7788
@@theworldismine7788chose anything?
React pays the bills, Svelte and Vue keep you happy for personal projects.
vue pays my bills, Svelte keeps me happy
How lucky
The best library/framework is the one you can finish projects with and have fun doing it
fax
So learn all the framework and choose the one that works the best for me?
yeah ill just learn em all first lmao
the best is the one it's giving me money right now.
Nice name
Best answer
Don't forget Solid. It's intentionally new and delays features in order to make sure to choose the best ones. It's like React syntactically but with changes to make it easier for beginners. It's also one of the fastest front end frameworks. It is also seemingly the fastest npm-integrated framework
Fun fact: for most of those "frameworks" you need another meta-framework to build serious apps. For example, there is Next for React, Nuxt for Vue, and Svelte Kit for Svelte. Which really raises questions about how much of a framework those things are. Angular on the other side really is very framework.
Angular and Solid: We are too. React: I'm a library bro not a framework.
SvelteKit❤️
The one mostly used in the industry in which you reside, most in demand in your country.
I'm minding my business while learning JavaScript
Svelte is nice, we had a very close 4 month relationship. They made a weird choice with the directory/file thing in one of the last update, but that's not really a problem.
I just got started and really appreciate the positive experience.
Svelte. Svelte out of those 4. If only people were to invest in it like how they do for React..
Svelte doesn't scale. It lacks proper solutions for managing shared state and derived state. It's also not very transparent, acting like a black box. Much like vue and angular
@@lennart5738 I doubt you tested the new vue 3 composition api before saying that. Much more es6 Js oriented and typeScript friendly. And how is React is less a "black box" anyways
@@Boobouh Composition api look nice I hadn't seen that before. I last used vue in earnest when it was v2 yeah.
But it still has their own non-standard templating language with pseudo-html directives like v-for and v-if. it's much less transparent what happens behind the scenes when you do that.
React is less of a black box because you know exactly how the ui updates work because calling setState just triggers the function to run again. easy, simple and transparent. no proxies, no weird template processing of pseudo-html. it forces you to think correctly about your state and conditional logic.
Even JSX is an extremely simple processor that doesn't do much more than simple regex replace would do. hooks make it so easy to micromanage your own component performance.
@@lennart5738Shared state in Svelte is covered by stores and contexts. Derived state is through… wait for it… derived stores.
Not transparent? Go ahead and look at the code the compiler generates. It is substantially similar to the code you have written, just with some instrumentation sprinkled in, especially in Svelte 4.
I agree man. Svelte needs more attention in company projects.
It's not about you. It's about what market uses. And it's React. For your pet projects use whatever you want.
Wrong! If you keep using what everyone else is using the evolution stops. Vue would not exist and it has gone past React, mainly because React is just a side project to Facebook.
Yes and think like this: if everyone learns the most popular then there will be the most people applying for those jobs while the job offers of the not so popular frameworks are more likely to get.
How do you measure what "the market" uses and how does it matter for the next project?
We are the market
I really like Svelte because the code looks like HTML with some extra syntax to integrate JavaScript. It does use some JS syntax differently, for example labels (`$:`) and `export`.
Seriously. All you need to do is write the layout, the CSS (you can use Tailwind if you want) and then JS to integrate with other components.
My first framework was React(library) and now I'm using Angular, And one thing I'm absolutely sure about is that React is complete garbage comparing to angular
Kinda agree, the only gripes I ever had with Angular is:
1. Its opaque tooling (build, test, dev server, etc), which caused it to fall behind in adopting things like Vite, Vitest, Jest, ESbuild, etc.
2. The unnecessary abstraction/distraction of NgModule. The only module systems should be ESModule. Luckily this is no longer the case with standalone components and simplified dependency
The core part is just amazing, and will even be more amazing when you can use Signal (+ RxJS interop) for declarative state management.
u r a garbage dis mod
Choose a framework ❌
Build a new framework from scratch ✅
My advice: choose one among most famous if you're looking for a job or if you're an indie developer, pick any one which you like and the main advice is once you choose stick to it, don't look anywhere else
Angular anyday everyday
Frontend -: Next js
Backend -: Fastify js
nextjs is still react lol
@@timalk2097 it's react from another dimension
After years, I gave up all frontend work and focused only on backend. I hate frontend coding. I also started my journey with iOS development, which I really appreciate.
Isn't IOS still considered frontend as well?
@@alejomakevids You know frontend is known for web. I was going to type web frontend but forgot because we used to call it like this. Just check you username. 😀 It’s the JS hell you know.
Not mentioning Angular on this list is crazy. Especially with the Direction Angular is going currently.
Don’t learn a framework, learn how to program JavaScript… then USE a framework that suits your project
The problem is that learning a new framework every single time just to incorporate it into projects will take a toll on your the organization especially if theres a tight deadline. Plus you have to go through the curves of learning it. That's one of the reasons why most companies will require people applying to have atleast have some proficiency in a particular framework
What JavaScript framework do you use!? 🤔
@@engrsi me too!
React and Svelte
I use both react and svelte. From my experience, svelte is much much better than react and has a great developer experience than any other framework out there
ReactJS and angular 6
Vue
I admire you for the last part. Whatever you choose is the best framework.
That is absolutely true. I hate it when people say this is the best and you must use this. Because all I learned over the past few years in the industry is, there is no such thing as called silver bullet. Everything has its' pros and cons. It's all about how you make use of it.
Without angular this video hurts me 🤣
Svelte 🎉
What about Angular?
There’s too many for a single video!
@@CodingWithLewis You mean a short
Just playing mate, great video. Been using react since and it's really been fun
@@johnychinese no he actually means for a single video. Even if he was able to make one, the video would be outdated in a day
react + typescript = madness
React + anything = pain.
Svelte is what Kotlin is to Java, what Go and Rust are to C++...
Cleaner, easier to work with, less error prone due to higher simplicity...
I'm not saying React is bad, but it's not the best, shich implies there are better frameworks. Svelte and Vue are certainly among them.
@@shapelessed While I really like a lot of ideas behind Svelte I think this comparison fails, because Svelte is not a different programming language and compiler, but Go and Rust are compared to C++. Kotlin is a bit of a special case because it also uses the JVM, but to my knowledge in normal cases, it does not compile to Java source-code.
I tried learning React...
And I say "tried" because its performence, size, overcomplicated and ugly nature of JSX made me give up after just a few days...
Then I found Svelte and managed to learn in a day what would take months with React... It's easier, cleaner, faster, lighter and generates smaller packages than React...
I was the lucky one to pick the framework our team is working with and they're all thanking me for it to this day.
Reac...
Reach your own conclusions.
Been waiting for the video 🥳
Solid JS - react but faster and less popular
Qwik JS - very new, react but you have to add $ almost everywhere and it's even faster
As far as I know Qwick even allows you to use React components.
Faster in doing what?
@@TheddunTOSS updating dom
Cool
angular is really underrated
very true but i think the learning curve is what scares people away more so the ever dreaded RXJS but all i can say once you master angular there's no going back once heard a senior dev say angular is like black coffee without sugar at fiurst your taste buds will not want but as soon as they get used to it they will not want you to stop cheers
Angular is very overrated.
@@lennart5738 please explain what you mean and before you do have you used it?
@@wilsondouglas1546 Yes. Angular comes with batteries included, this means it has a lesser ability to improve over time. Like how React and Redux used to be almost synonymous but state management has been massively improved over the years and no new project uses that.
The main issue with angular is twofold:
1) They force you to use too many abstractions out of the box (typescript, rxjs, DI, etc.)
2) They hide state management away behind proxies and decorators which makes state management less transparent, resulting in people writing less performant code.
Angular also uses their own weird directive system instead of just giving you javascript in your templates which is both less intuitive and less powerful.
Angular also has it's own very specific tooling which means it does not benefit from the past few years of optmiizations in bundlers (vite, parcel, esbuild, swc, turbopack) resulting is a slower development workflow (see: github.com/vitejs/vite/issues/543)
Angular is by design, stuck in the past. it is the modern day jQuery.
My recommendation is, if you like writing your components OOP-style with custom template directives, try out vue. vue is faster, better supported by modern tooling, more modular and easier to learn
If you prefer writing functional components that are self-contained though, consider using React. React with react-hook-formand react query is a nice starting point for a modern functional javascript app
@@lennart5738 thanks for the reply but firstly we can agree all that you've said is a very subjective opinion and not objective
1. in this sense that its not factual coz if it was then there ought to be a list of things by which you qualify something as legacy and in this instance you havent provided a gloabal list of univesally accepted standards to call something obsolete quick example like the versioning of ECMA there are set standards accepted to know the diffrence between ECMA versions
2.again this soildifys point one in this senses you say that angular forces you to do things in a certain way granted you wouldnt want that well to that i will say more power to you but is there a chance even in the miniutest form that there are actualy developers who like things that way and i believe you would say yes and to that i say that's a matter of prefrence and to you it seems you dont like that wich is still a good thing but is not a fact
3.again you say state management is hidden behind proxies and decorators this just gave me a smile and makes me wonder if you really have used angular state managment isnt hidden behind a stone wall that you cant access and see what is being done.we have multiple libraries by which you can have state management from simple libraries such as akita and observable-store all the way to complex things such as ngrx & ngrs you can have state mangement at component level to state managment globally depending with your needs at the time
Finally you say angular is the modern day JQuery gave me a good laugh to this that i will say is just an opinion make it stick with objective reasonalbe points earn that statement
let me give an example we both have cars you have a sedan and i have a truck/lorry (dont know what part of the worldyour from) they both use diesel (diesel being metaphoric for JS) your carcan do 0-60 in lets say 6 sec my track does 0-60 in 20sec but my track can carry way much weight and has more power output from the engine than your car hence different cars for different works
to conclude i think we can both agree that the end user doesnt really care what tool we use as long as they get a great user experience and a real world effecient app
be blessed
Only SvelteKit... forever!
Svelte > Next > everything else
what is the best framework for 2024?
I think astro should be added to the list
What's that?
This guy never know how good is angular.
the learning curve is what scares most away but once you get around it you apprecite the power angular brings to the table
@@wilsondouglas1546 the exact reason why i went with angular is because every comparison just talks about how easy react is ( implies surface level features ), how many users it have ( implies high competition on the job market - you lose your uniqueness), and how its small is size and really fast (this is the best thing i agree about in react).
There’s no language barrier with Vue docs
JS echosystem is a cluster f
Justise for Angular
SolidJS is even faster than Svelte and has syntax similar to React. Also, Astro is pretty cool, it allows you to use multiple frameworks and libraries in one application
Which is an approach not recommended. Always try to use one framework for a single project
Svelte!
2 things are infinite: the world and js libs
Actually none of those are infinite.
@@skywalkersohan8656 world is literally infinite and still expanding even now what do you mean it's not?
@@aldi_nh Infinite can't expand only finite things can.
@@skywalkersohan8656 what rule is that? If it can't expand, then it has limit, does that count as infinite?
@@skywalkersohan8656 does infinite loop can't expand as well?
I would disagree that Svelte is immature. The ecosystem is the only thing that needs to grow, but you can use Vanilla JS libs out of the box
React with MillionJS is good as native javascript performance.
By ignoring bundling size.
I have heard that React is not a framework, it's a library made by fb. What do you guys think?
Yes because you need to install a lot of third party libraries and hence it's a library unlike Angular for example.
React is very frustrating to work with... not sure what the point really is
I personally think that Astro is the best framework!
Svelte is so much better than React because it is so similar to Vanilla JS....but better
I have yet to run into any language barrier with vue
We have been using Svelte And Sveltekit the last year or so at our company and it has been amazing! I can highly recommend svelte and sveltekit. SvelteKit is also soon going 1.0!
SolidJS.
Svelte is bliss
I like 5js if that counts. Not really sure what a framework is. I just assume it's like a c++ library
Urmmm.. Angular?
If I use Vue for building tools today, will I be better off switching to Svelte? I don't rely on Vue specific libraries. Reactivity and data store is very important for me. Please only reply if you have tried them both.
vue has a great documentation, also vue language barrier in documentation ...WTF.
Nextjs no competition
A framework to do what? Modern JS isn't only about rendering UI and adding functionality to triggered UI events.
I prefer vanilla lol
React is a good option to understand how libraries/frameworks work (and to pay the bills).
Vue is a good option if you want to learn Chinese, it has an original Chinese docs.
Svelte is simply fun to use, and it combines all the goods from it's predecessor.
React is library
I don't know why but I find Vue very easy the react .
Does svelte being a compiler even matter if a website is static/ssr?
Javascript and "insane performance" in the same sentence seems a bit weird to me 😝
I don't get the language barrier concern for a framework documented in English. Is there a particular non English speaking country it's popular in?
Ima still find out for myself, but how well is Bun doing?
what is a javascript
Well, it's not Java.
And for the back ?
You missed NextJS
jQuery for the oldschool OGs yo'
Remember when we didn’t over think everything and just used vanilla js?
i actually believe that if you built you app in vanilla js , you would be more comfortable with you work than with a framework., the close you are to the source is alway better.
I'm not sure exactly how much this guy knows about anything remember his Tier List
Yeah there's no lack of clear Documentation for Vue. It's the best. But then again all frameworks have the same weakness and that's being frameworks. They inevitably get too abstract complicated and enforce bad methodologies. It's the tradeoff between consistency and freedom.
Hey! what about qwik?!?!
There is no language barrier for vue documentation??? 😅
What about Solid!
Mean while the op watching this meme: qwik , angular+wiz
Please youtube stop showing random tiktok shorts instead show this kind of shorts
And what about angular
Is Angular dying?
Nope, heavily used in enterprises.
Not at all. I use Angular myself there’s just more of a demand for React in the market.
NO, infact it is a reliable js framework with nice features like reactive forms etc
@@rojaachan do you think there is a lot competition with the demand that react have.
@@wafi5576 I would say so yes but I can’t confirm as I don’t work with react as much as someone who does. I use Angular for work and I’m based out of Florida. Depends on the area too
Learn react and angular if you want to get a job
How about astro?
React is a UI library not a framework.
Me still noob about this
react is framework or library? or both?
Is a library
Next and only next
How about Qwik ?
No.
Vanilla guy (or kid [13]) here
Vanilla will win in the long run but that is probably 20 years in the future.
@@jenstornell hopefully
Next
Angular > React
Angular is the good javascript framework.🅰️