JavaScript Frameworks in 2023

This diagram was getting some controversy so I rushed out the video
/ 1612980211393638401
#t3stack #fullstack #webdevelopment
ALL MY VIDEOS ARE POSTED EARLY ON PATREON / t3dotgg
Everything else (Twitch, Twitter, Discord & my blog): t3.gg/links
S/O FlipMedia for the awesome edit 🙏

[@t3dotgg]

Link to chart: twitter.com/t3dotgg/status/1612980211393638401 Also quick note on Vue - goal was to highlight that EVEN I, A BIG REACT BRO, WOULD MOVE TO VUE FOR IT'S I18N COMMUNITY EFFORTS IF I HAD A TEAM THAT BENEFITTED FROM IT. Good framework, not my thing

[@jasonrooney1368]

I do think you should give it another go sometime in the future. It's a pretty different thing to what it was a year or two ago, and vastly different to what it was 3 years ago. It's now taken a bit of the best of everything: - React hooks allowing for composable stateful logic - Solidjs reactivity (well, Vue did it first) allowing for reactivity that just works with good precision reducing the overhead of having to optimize for performance - Svelte compiled script allowing for terse code - Typescript support is pretty much ~99% now with the exception of the occasional Volar issue since the tooling isn't as mature as JSX tooling I'd still choose React for the ecosystem. Vue's ecosystem has been especially shaky when it comes to component libraries, with the leading Vue 2 library dragging its feet (Vuetify). But I would still consider it one of the top dogs because it still is right behind React in terms of ecosystem and solves a lot of the reactivity issues that React has today.

[@swaggitypigfig8413]

How dare you choose one framework over another? Have you no concern for the other one's feelings?

[@zombiefacesupreme]

This video may have eclipsed the unit testing video in terms of controversy before it was even released. 😅

[@DoctorSoulis]

Lmfao

[@hsuyuting1993]

I have this fear that if I choose one path for a project, I'll be stuck with it forever and regret it in the future. So I'm constantly searching for the 'optimal' stack. This is hell.

[@igetpaidtocode]

There’s none. Just pick the most fun to you. 🎉

[@omarkarim9298]

And rewrite it if you need, much easier to convert than writing from scratch

[@butterfly7562]

svelte

[@benyamin4634]

dude this concept and video can be expanded on so many other technology. so please continue digging around this subject because it made me aware of other technologies too. thanks alot theo

[@hsider]

Exactly, we all know how it's frustrating to choose a stack for a website/app.

[@GBlunted]

Loved to hear all these recommendations! Never heard of any of these companies but your enthusiasm has me intrigued. Especially since I can relate to the frustrating infrastructure experiences! I'm still surprised how confusing some of this cloud stuff can be and when it's like that just lining everything up, it ends up feeling fragile once you get everything working which is not how I wanna think of my production environment! Like walking on eggshells around a terrible roommate or mad girlfriend... 😆

[@codybishop7526]

I think the main issue, aside from choice paralysis, is that after you learn some basics in JavaScript and react, there is a huge, empty Valley that you have to trek through before you get to the other side as a confident developer. Plus, it’s hard to know what to actually focus on when studying and learning react, even before you’re attempting to create a fun side project.

[@TomoFromEarth]

I’m so grateful for these videos. I’m learning how to ask better questions and how to make good choices when learning new tech. 2023 is gonna be a dope year for me as a baby dev. Watch out mofos. 🤓❤️

[@mirkosedda3196]

As beginners we are on the right channel! Mo more how to learn to code and js array videos 😂😂😂🥰🥰🥰 thx @theo ❤️

[@coolemur976]

In React everything is in beta. Documentation, nextjs13 features. Sveltekit delivered all those things. But yeah, pick React not because it’s better, but because it’s popular. 😅 And who doesn’t like hooks hell?

[@theanswer1993]

I use Angular for everything. Web, mobile, desktop. It can do anything.

[@jon1867]

The only thing I really didn't like about this is that I work in remix all the time and it feels extremely well suited for very interactive data. Does it streamline the non-heavily interactive parts? Yes. But nowadays you can still use all the goodies you would use on t3 stack (except next-auth) with remix. I've seen trpc adapters, useQuery, tailwind, etc... It doesn't block you from using those things. I have to imagine the same (or similar) would go for sveltekit, solid-start, or qwik. The thing I'll give T3 stack over any of the others I mentioned is that because you are using NextJS, and way more people code in NextJS, you get the benefits of being a part of that massive community.

[@suspendedchaos]

Remix has remix-auth though

[@scigama71]

really great and practical video. thank you

[@grantwilliams630]

I’m really considering picking Phoenix + liveview. I like the idea of the bundled backend and scaling seems pretty easy too

[@Voidstroyer]

Agreed. A while ago I did the "todo app tutorial" for angular, react, and vue and I liked vue the most since it was easiest to get into. I think it was back in 2020 that I learned about Elixir and Phoenix and I loved it immediately. The syntax was hard to get used to at first since I came from OOP languages and still use OOP languages in my work, but I just like the features that Elixir has to offer. And I also wanted to get more into websockets and phoenix just makes that super easy. Javascript is still going to be very relevant for the near future, but I do like seeing non-javascript frameworks entering the FE space

[@BosonCollider]

@@Voidstroyer If you use Phoenix and liked Vue you may be interested in Petite-Vue or Alpine for when you just need a tiny bit of reactivity and want it in the frontend, and want to express it entirely in HTML and without loading a huge framework. (Personally I like preact for that usecase, but that is more in the app & react direction)

[@Voidstroyer]

@@BosonCollider I guess, but the phoenix liveview eco system is also growing and it kind of makes using a frontend framework useless. There is already a lot of interop between liveview and javascript so not everything client-side has to communicate with the server.

[@doxed64]

Been programming in Python for ~6 years. Wanted to Full-stack. Saw your videos. I'm now learning Vue AND React. Thank you.

[@m3hdim3hdi]

why both at same time?

[@doxed64]

@@m3hdim3hdi vue for smaller personal projects, and react+next for production. The question is "Why not learn both?"

[@bravethomasyt]

I think you've missed out Nuxt as an option here. I'm a React and Vue dev, and Nuxt has the best DX so far for me. Especially now that Nuxt 3 is (finally) released.

[@JasonAtallah]

It’s in his diagram on Twitter

[@bravethomasyt]

@@JasonAtallah nice one, thanks will take a look.

[@nightshade427]

I've been using astro with combo of htmx and alpinejs with great success. Gives me lots of features I can opt into. Eg, server components, suspense, streaming, resumability, ssr, client side interactions, targeted client side updates via micro reactivity, and much more.

[@whatplan4335]

This seems like a pretty neat and simple stack, I think many things are over engineered these days. I’m currently building a project with the T3 stack that doesn’t really have a lot of interactivity. However, it does require a backend, and tRPC + prisma is just awesome to work with.

[@bayrock1337]

Astro seems particularly great because it is framework agnostic.

[@dandogamer]

Just from a quick read up, it seems a very simple yet elegant stack. Have you had any issues with it?

[@nightshade427]

@@dandogamer no real issues, but, things aren't auto magically done for you. Eg. For resumability qwik handles a lot for you, but, in this stack I attach my data and logic to component as alpinejs/htmx server side so when it gets to client it can resume. Which is nice because I can opt in to how I want each part of the site/app to behave. I like the simplicity, control, and the ability to opt in and do only what I need, that this stack gives me. Basically all the primitives are there, so I can use plain html by default and sprinkle in more features on an as needed basis.

[@josesantillan732]

Ridiculously Excellent! Congrats man

[@Lundito]

I have a side project I've been working on for a long time using Nuxt 3 and there have been so many times where I've stopped working and really reflected on if I've made the right choice or not. Testing out SvelteKit after a long time I almost considered redoing all of my (likely 200+ hours) work just because I felt like I would have a different experience. It's so easy to fall into these thoughts and I'm glad they do exist, because it kind of makes me want to test out new frameworks in other projects, but at the same time it can really make me anxious sometimes. Now I didn't swap to SvelteKit and I'm still happy with my choice, especially now that Nuxt 3 had it's stable release and things are progressing well, but I'm sure this will be a recurring theme for future projects as well.

[@YuriG03042]

it's always like this. another framework will fix a problem the current framework has, but then it will later introduce other different problems. it's always gonna keep happening because there will always be knowledge gaps in all frameworks you use

[@yamyam263]

@@YuriG03042 While that's true, we shouldn't just lose motivation and stay on one framework either - otherwise we'd all be still coding jQuery.

[@BosonCollider]

Imho I would reach for preact earlier and only pick react if I need fancy react features or libraries that preact is incompatible with. It makes the app faster by default, it makes you adopt signals for state management from the beginning, and it keeps things simple without distracting you with a huge set of things. And unlike something like Svelte you are still essentially practicing a react skillset.

[@seanbruceful]

For anyone dont know. Vue2 is really really popular in China. Like when someone plan to become a front-end dev, all most all online tutorial suggest that you should learn Vue as your framework. and 90% + of the job oppotunity is for Vue. I have experience of both 3 front-end framework(React [library actually], Vue and angular) and React is my farorite. I dont like Vue because I have to use it to get a job. Glad to see Vue2 get the same popularity in the rest of the world

[@danielochoja8507]

How about 3....Vue 3

[@danielochoja8507]

How about 3....Vue 3

[@bravethomasyt]

No one should be using Vue 2 anymore and instead use Vue 3...

[@Go_with-Christ]

who the fuck cares about what happens in china

[@pjf7044]

Interesting how geography makes such a big difference …

[@Iturner72]

Incredible, very helpful :)

[@RemotHuman]

You should make a vid on differences between create t3 app and competitors (redwood, blitz, bison, choosing your own stack) (I got these from the tweet you retweeted from ajcwebdev)

[@davidrobertson6371]

Theo misses out, Vue have been remade recently probably should have a 10/10. Lol. So many people are different in opinions etc. but Nuxt 3 for dev experience is insane, even Ryan C, was smiling like a school girl talking about it. It’s so quick and easy to fire up anything, it’s faster than if I just wanted Vue only. I get it, this is a React channel and American to boot. But Nuxt gets no love over here. Great channel BTW, you saved my bacon I was gonna use firebase on a project until I saw one of your rants, picked supabase for the built in features and boy I’m happy I did, the project is getting more and more complex and firebase would have been a nightmare.

[@zzzyyyxxx]

I switched from Vue to React. Vue has like 3 different ways of doing stuff, options API, composition API, reactive $$ usage etc, it's all very confusing actually for beginners. And also I've dealt with so much templating, you couldn't pay me to write another v-for.

[@Voidstroyer]

@@zzzyyyxxx I agree that vue3 made things a lot more confusing and complicated. I liked it alot back in version 2 though. Nowadays I would probably pick svelte.

[@davidrobertson6371]

@@zzzyyyxxx I found the exact same thing, too many ways of doing the same thing. However I picked composition api, script setup and ts, but the kicker for me is Nuxt 3. I would never start a project with just Vue. I honestly have no idea what advantage there would be to a plain Vue project. I picked vue only because i barely knew any JS at the time, and it seemed less complicated than react. End of they day they all accomplish the same shit. Lol.

[@lucabaxter4002]

@@zzzyyyxxx Wait until you start to have bugs because of immutability, and you will be back on Vue. I used React for many years and the fun i still have with Vue is not comparable. A lot easier for beginners in my opinion.

[@zzzyyyxxx]

@@lucabaxter4002 Immutability bugs? Not sure what you mean

[@bashbunni]

ALMOST AT 100K LET'S GO!! ❤‍🔥

[@simonhartley9158]

Perhaps ecosystem size should be factored in here. This might change how you decide on Vue vs. e.g. Solid.

[@DanielBergholz]

Why not just use Ruby on Rails? Or any other MVC framework? They are much simpler and get the job done twice as fast

[@riceymix4688]

there is also a much simple solution which is to choose what you like and what your team likes the most. It is 2023 and most frameworks are capable of doing what other frameworks could achieve. Unless you really need that extra performance this is how would I go with choosing a framework for my appliations.

[@pjf7044]

Yes but u forgot people are sheeple and like to follow the others advice even if it’s pointless

[@YuriG03042]

most people asking for advice haven't even tried a framework yet, so they really don't even have enough experience to have a favorite

[@Mitsunee_]

one unique problem I have with my portfolio site is that I *have* to do a static deployment to an apache webserver (I guess I could put some PHP stuff in public for some basic api routes) due to some limitations (TL;DR www needs to be the apache server or my emails stop working) with my provider that I'm otherwise super happy with. Right now I got some hacky workflow with preact in vite-ssr, rehype and cheerio. I'd really like something more ergonomic so I guess I'll look at Astro? Laravel is probably overkill for the two things I might do with PHP.

[@hamzahmd_]

Please create a video on picking web frameworks on the types of applications (Portals, eCommerce, Dashboards, etc.)

[@asdfjackal]

According to this chart I made the right call with Redwood, so I'm on board with it.

[@luispichardo7617]

@t3dotgg How do you find out about these technologies and frameworks?, and how do you find/plan the time to learn how to use them?

[@allyc0des972]

Im using sveltekit and I love it. It also has a built in API so its an all in one

[@unowenwasholo]

banger thumbnail

[@anasouardini]

what do you mean by start simple in the site branch? astro is already very simple by default. I mean learning JSX can be done in an hour or less.

[@sadDota]

can you give one react docs example where I absolutely need to be a native English speaker to understand it? even tho I'm not a native speaker, I'm confident that I can understand all of it with no significant problems at all.

[@Leto2ndAtreides]

How is SSR in Astro? I haven't used it but it sounds like it should be usable in similar ways to Next.

[@armi2n]

I may be wrong here, but isn't Next.js also great when NOT using SSR or NOT needing an API. Can't it be deployed to a CDN by using "next export"? Maybe the diagram would also have a branch into "I need a meta-framework with file-based routing".

[@aldogutierrez8240]

Great video thanks

[@wynton921]

Hello, thank you for your video. Can you point me in the right direction? I’d like to build a streaming content site and give creators the ability to set what percentage of the streaming revenue generated that each member of a band or film crew will receive every month from that specifically published content. Can you tell me what frameworks you would need to build that type of feature? Thanks so much.

[@catoberge]

Interesting and quite overwhelming as a pure amateur/hobbyist. Still fun though :) Side note: what canvas/drawing board-app is that you are using?

[@bartosz.holubowicz]

That tool he's using is called Excalidraw. Glad you can still enjoy the content!

[@JoaoAlves-ce1fi]

I have one question, does it makes sense to use Next w create t3 app whilst using Strapi as the CMS?

[@jaredsmith5826]

Import question not on there: how many developers are going to be concurrently working on this thing? Because it's waaaay easier to coordinate 100+ devs in a biggish monorepo with some of these (*cough React) than it is with others...

[@IbrahimAbdallah-tr4wq]

Vue beats react in both the technical and the innovation aspects, not in the job postings and community though

[@SivicIsntFat]

Isn't starting React with Vite a problem due to faetures that arne't supported on vite (for example svgr doesn't work well with vite)

[@panchcw]

I just watched the video and it was awsome

[@MARKOTHEDEV]

Nice video mr theo 🎉

[@ducta2229]

Hi, What tool you are using for drawing?

[@Chillycloth]

Bro got the rizz 💯

[@ra-dro]

Hey, could you help me with mobile dev? Do decide on React Native, PWA, Flutter, ionic and web way to go?

[@OhDevBeard]

I’ve been stuck between nextJS, angular and Astro for a project I’m building. It’s been 3 weeks :rip:

[@HankF12]

Curious where Phoenix LiveView could fit on this chart (if at all).

[@Voidstroyer]

You would most likely never see it since he hates Elixir (due to the lack of strict typing. But Jose Valim has already explained why the traditional type system of other languages would not fit into Elixir because Elixir doesn't have the problems that those languages solve with their type systems in the first place).

[@TON-vz3pe]

What if I don't want to use JS at all, then I recommend Actixweb and Rocket for Rust.

[@DanielFisaha12]

Is there really no reason to have a separate backend? What if the service on the API you’re hitting is much faster/only possible in another language like ML models? Would you just implement them as a micro-service connected to your next backend?

[@BosonCollider]

There are plenty of reasons to have a separate backend, especially if the frontend is just a trivial part of the thing you are building instead of being the whole implementation. Frontend devs are inherently biased towards node, but it is not at all a good option unless you very specifically need advanced SSR for an application that cannot be done at compile time, on a page that *also* needs app like functionality. If you don't need that (true for a very large fraction apps), there are alternatives to node that rack up a much smaller cloud bill. Also, get good at using CSS, you can use it to avoid having any actual JS in many controls.

[@aristide_F]

Thank you Leo

[@aristide_F]

I’ve really learnt a lot from you this past year and this new year even seems more promising.

[@davidhavl]

Thank you for the video and your effort. Before making the "there is not much innovation in Vue community" statement, however... please have a look at Nuxt 3 released end of last year. It is a complete rewrite with several amazing features things such as auto imports, top level await, edge deployment, typed api routes and much much more.

[@Voidstroyer]

Yeah but you kinda learn not to take Theo's opinion too seriously lol. He himself admits that he doesn't know that much about vue because he doesn't use it himself, so obviously I would take his opinions on vue with a grain of salt. I'm not saying that he is automatically wrong, but rather that there is a higher chance that he doesn't know what he's talking about.

[@davidhavl]

@@Voidstroyer Fair enough ;), although I believe in a bit more responsibility when it comes to addressing/influencing this many followers, making a full research about a subject/item before mentioning it.

[@davidhavl]

Saying that, I do appreciate how much work goes into making these videos and yeah, no-one is perfect.

[@Voidstroyer]

​@@davidhavl True. He is so deep into the react world that he is even unwilling to try things outside of react (not saying that he doesn't do it at all, but he rarely does so). That's why I personally like ThePrimeagen a lot more because he is a lot more humble in his opinions. Theo can be quite arrogant in the way he delivers his opinions, even if there is merit to them. People are just less likely to really listen to someone who comes across as arrogant.

[@fkw0k3t4rd5]

Wait why do you hate sveltkit? I must have missed this video and im genuinely curious.

[@_Aarius_]

One of the biggest problems in tech these days is evangelising a single technology for broad swathes of problem spaces and being unwilling to think about specific strengths or community-side considerations for long term support. I don't know much about frontend, but this is absolutely the sort of information i would want if i ever was to get into it.

[@emmanuelcastillo6954]

I'm wondering what framework would be the most ideal for freelancers in 2023. I'd love to know what your opinions are on the framework that has the most raw potential for making money in the freelancing world.

[@abdu5822]

as a freelancer, i think RedwoodJs would help build projects faster it gives you graphql backend api + Prisma and react on the client. if you come from Ruby on Rails, this feels home.

[@nexxel]

t3 stack

[@malenalucero6473]

You are underestimating the English level of non-native English speakers. Ya estamos curtidos.

[@whoislewys3546]

The SEO benefit of SSR is overbllown

[@VinniePazo]

@Theo on a different note. What the brand of your shirt? I like

[@hanes2]

I'm into vue, so my thing in 2023 is to learn Nuxt3. (yeah good point, English is my/our team secondary language)

[@fa33727]

i love how angular is not in there

[@SkywalkerWroc]

Angular is dying out. There's no future for that framework.

[@moitp2]

@@SkywalkerWroc says who ? The fact that nobody talks about it doesn't mean it's dying, especially with those numbers. It's still today the second most used framework with Vue (both are more or less ex aequo right now). I'll tell you why nobody is talking angular while milions of apps are still running with it. Because Angular provide you everything you need, you don't have to search for a 10th way to write your router, or else. So less "hype phenomenum". Look how many hype trains were taken the past years. How many succeed ? A large minority. See ? That's the diff between hype and being relevant. Angular is. Hype isn't.

[@hugazo]

Last three years i've been working with vue, so i'll keep vue

[@wantedsavage7776]

Bro your very based coder. I don't even code a lot. But like. Your way of thinking is based.

[@okage_]

really liked this video

[@tombarber654]

We've had an agnostic approach for years and have moved away. doesn't make commerical sense for approach outside in house. Jump into a new framework and we're absorbing or charging learning on a very different scale to specifying one the team is familiar with.

[@polioann]

Love astro, however it has less than 50% support in my country. I will not using it till it will have JS transformation. Also if thinking about browsers support (which may be critical for many businesses) - there are mush fewer frameworks options.

[@v01d_r34l1ty]

Like 90% of companies are going to be only primarily worried about Chrome and Firefox because damn near every single consumer browser is going to be Chromium based (Chrome still the most popular) or a Firefox rebrand.

[@polioann]

@@v01d_r34l1ty yep, but we still have chrome 61, 62, 63, 64, 65, 66, 67, 68, 69 (unfortunately)

[@v01d_r34l1ty]

@@polioann I don’t know how out of date that is, I use Firefox 😬

[@nigeldasilvalima4568]

The definition you used to differentiate site and app would make KZbin an app instead of website. Great video btw

[@Utsuhoagie]

Yeah that part didn't sound right to me either. There's plenty of interactions on YT: liking/disliking the video or comments, saving to playlists, opening comments or replies, not to mention the video player itself

[@phendan]

Agreed. I think my issue with this definition is that those terms have pre-existing meanings and it feels a bit late to redefine them.

[@wlockuz4467]

Agreed, KZbin was a terrible example because its a complex hybrid of both a site and an app.

[@kieranhaycock3338]

What are your thoughts on Blazor C#?

[@BenjaminWeeb]

What is that diagram app? Edit: Found it, Excalidraw.

[@meghnathpillay463]

A tangential question, would a JS full stack developer benefit from learning Rust for specifically wasm and Ui reasons? Is Rust going to be a practical way to write UIs soon?

[@jon1867]

Yes! Every auxiliary language you tinker with will give you some perspective on the language you work in every day and how it fits into the broader picture.

[@IvanRandomDude]

Soon? Lol, no. Probably never. You can learn it for fun if you want but it will never be used to make frontend no matter how much rust bros want it to be. It's not even the most popular wasm solution, C# and it's Blazor WASM is already miles ahead of Rust in terms of popularity and adoption.

[@jon1867]

​@@IvanRandomDude Agreed

[@zzzyyyxxx]

For UIs? No, but I use it for my backend API, miles better than NodeJS.

[@rod6722]

@@zzzyyyxxx What makes it better than Node for an API?

[@whyneet]

Why u didn't put Angular on the table?

[@RobertoOrtis]

Let's get Qwik! ;)

[@rizkiaprita]

because theo mention t3-stack, please anyone help me understand trpc better. tprc isnt api right? i mean, the procedure isnt exposed to the public, the is no endpoint. why does theo recommend t3 stack if i need api?

[@mojt_ba]

what is that app or web site he used in site or App chapter

[@mihaibalan8481]

what about Angular? :D

[@krikayassine340]

What is that canva that you using ?

[@1998goodboy]

Idk man....learning go pretty much magically got me hired then doubled my salary in a year 🤷‍♂️

[@dot4636]

Vue can also be your choice if you don't like/hate JSX

[@ojvribeiro]

My case. As a person who works with React I personally hate it. My side projects are all in Vue + Nuxt 3.

[@dot4636]

@@ojvribeiro We also use mostly React at work, although I'm trying to move our team away from it slowly... Preact was the first step, its signals are really great and very close to vue's ref from how you use them. I also only use Vue for my sideprojects.

[@kedusyared6589]

What app are you using to draw this?

[@Linkplay9]

shouldn't the default be something performant in the first place?

[@blazed-space]

I basically use a different framework for every one of my ten million apps distributed amongst twelve domains.

[@Zzznmop]

Distinguishes site or app based on site 🤔

[@magne6049]

Not even a mention of Qwik City? 😕

[@volimsir]

Why pick Eleventy over Astro if you have thousands of pages?

[@JoshuaClancy12]

Where would Qwik fall in your chart?

[@felkan]

Damn, Richard Hendricks from Silicon Valley started making youtube-videos now?

[@kiryls1207]

what about quik, is it worth it?

[@dHue_52]

*in a crazy charlie voice* Can we talk about the frameworks?! Ive been dying to talk about the frameworks all day! I've got folders full of frameworks!

[@SuperMBARutgers2013]

Hi. What tool do you use for the "blackboard"?

[@Dev-Siri]

he uses excalidraw

[@edwinwong9033]

The title should be "How I'm Picking React Frameworks in 2023"

[@jetpack_joe]

🚀

[@raihan7422]

this make my confusing and doubting life gone

[@zzzyyyxxx]

What was the drama with the Vue creator on Twitter? What are the technical pros and cons of Vue beyond simply the docs language?

[@kevinsieger4523]

If you want a eco system with more aligned best practices, Thad also a big plus for Vue.

[@zzzyyyxxx]

@@kevinsieger4523 lol best practices? They have like 3 different ways of doing things, options API, composition API, reactive references with $$. Personally you also couldn't pay me to write another v-for again

[@kevinsieger4523]

@@zzzyyyxxx that’s like criticizing React for having Class based Components.

[@zzzyyyxxx]

@@kevinsieger4523 not really because class components are basically deprecated now, the preferred way is always hooks. One way of doing things. Not so in Vue, they present all the ways as almost equally good.

[@kevinsieger4523]

@@zzzyyyxxx The docs make it very clear that the composition API is the preferred way of writing things in no-nonsense circumstances. The transition for React class to React function components also wasn't instant.

[@andreyyastrebtsov4367]

What about Angular??????

[@curtisflaming8625]

I'm offended

[@swaggitypigfig8413]

Same! He should delete his channel for this offence, I think. I'm not willing to accept anything else at this point. He crossed the line.

[@curtisflaming8625]

@@swaggitypigfig8413 my thoughts exactly. have correct tech opinions or gtfo off of the internet.

[@cultoftranquility9616]

Sveltekit and Astro + Rust for crazy stuff ... (only React when forced to...)

[@EduardoSanchez-un2hh]

Or just avoid all this pain, use Angular!

[@echoptic775]

What about deno fresh?