JavaScript Frameworks in 2025

[@MatthewSparks]

I'm here from 2026. We decided SSR wasn't the move and went for something else. Also, the JS Framework Wars escalated to real life active combat, with people pledging to newly formed nation states, such as Svelteland and Reactania. I just returned from my second deployment. It's gotten ugly. War refugees have mostly fled to the combined haven of Larastro, a new state birthed from the joining of the Astro and Laravel Nations. Rumor has it they have solved hunger, poverty, and the problems of resource allocation inherent to market economies. My partner continues to beg that we flee there, but my ego simply won't allow that to happen. Tomorrow I redeploy to the front lines. Make better choices than we did. I beg of you all.

[@rajikkali]

Come over to Nuxtonia, we have cookies and peace

[@codefork94]

This deserves more likes 👏

[@lutfiikbalmajid]

@@MatthewSparks Hi, What your method in 2026? What Framework do you use?

[@ofadiman]

You guys are not using jQuery? 😮

[@lutfiikbalmajid]

i use it. 6 years ago

[@Alexjemapplesyrup]

What's that

[@artem_egamediev]

Around 9 years ago😅

[@buildwithharshit]

Its History now 😅

[@AlnisSmidchens]

I've been developing stuff with no build system, no frameworks, minimal libraries, etc. - it's very productive and refreshing. Web components + semantic HTML5 elements make a great combination, especially with all of the JS and CSS features adopted by browsers in the past few years. IMO this is the way forward for web development, at least for high-performance web applications.

[@davidbronke5484]

11:58 BFF is pretty awesome in a lot of cases. Great being able to tailor things to what the client needs.

[@saieashwar870]

BFF is really useful. In complex applications, it lets you aggregate data from multiple apis, have a platform agnostic business logic and even enable things like server driven ui. Depending on the use cases, more features can be added to the BFF layer (cache control, streaming of widgets in sdui, priority of widgets/api calls) etc and make the application standardized across all platforms

[@LostZenith_]

This is why I love this channel. Every year he kills it and provides more value. Thanks! I'm going to be an op dev when I graduate!

[@boiserunner]

It's 2029 and we are all using zigscript but fighting the transpiler

[@abob-henry]

Lit doesn't get enough love, maybe because of its somewhat more targeted uses. But I've loved working with it for our main front-end library the past couple years.

[@grim.reaper]

21:20 is so so so true, I hope every dev understood that 😔

[@_____case]

Deno Fresh 2.0 incoming.

[@QueeeeenZ]

Nuxt has made web dev much simpler and easier

[@_y7ya]

Man your diagrams are something else.

[@Efecretion]

? They look like diagrams to me

[@_y7ya]

@@Efecretion It was a compliment

[@Efecretion]

@ Oh, a figure of speech. I get it

[@_y7ya]

I've personally worked at multiple agencies using NextJS where "senior" front end engineers just slap "use client" almost everywhere... The once senior React engineer is effectively a 0.1x developer in a server first world.

[@qwerty-or1yg]

Yeah, I’ve used to love nextjs before app router and all other changes afterwards. I was a junior back then and I had a hard time grasping their changes and still do. It’s confusing and messy imo. I don’t even know now what framework I’d go with if I had to build a full stack app solo. Probably angular and some BaaS as I’ve been working with it for past 4 years and I love it.

[@ymi_yugy3133]

I like working on backend stuff, I like working on frontend stuff, but the communication between is hell. I just hope I can continue to work on projects where SPAs are good enough. If you use a decently fast framework the overhead of transforming JS+JSON into DOM should not be too much over transforming HTML into DOM. That is of course assuming, you don't really need SEO, work with weird browsers and you build you frontend with performance in mind. I.e. be careful with what packages you bundle and how you write your code.

[@ndykman_pdx]

I am baffled by the "you need some JavaScript on the server". It's not a language that provides any real benefit over the numerous other options on the server side and has very notable limitations there (events, threading, managing OS resources and so on). Sure, Node mitigates some of that, but it's nothing compared to languages that have explicit support for those features. I can't see going to anybody that is using Java, C# and so on and saying "Oh, you need JS to make a good web site" when they have been doing that for a very long time.

[@andydataguy]

The last video really was fire 🔥

[@travisgorski245]

Can’t wait to get to the point where I can go back to these videos And have them re wire my brain too

[@ErikBongers]

Why do you need "some js on the server"? What's the benefit over other languages?

[@m-ok-6379]

80% of frontend developers only use 20% of the JS framework they are working with.

[@theshy6717]

and 99% of gamblers quit just before they're about to hit it big

[@harambeexpress]

Prisma DB looks really cool and I'd like to build something with it, but the fact that the product has no pricing worries the hell out of me. Though, it's cool and you can use their ORM for free so I'll keep it in my back pocket.

[@victor95pc]

The biggest question I would have is why, WHY I would use Next to build a simple SPA lol, host the thing in a CDN and its done

[@vikramkr382]

If you like next's DX/router etc and dont want server side stuff you can just not use the server side stuff and do a static export. If you don't, then idk what the question is. Or what Next has to do with a CDN - a static spa is a static spa whatever you use to make it.

[@gageracer]

40:48 something very similar happened yesterday with svelte 5. I made a sudoku game and wanted to reset the game when you change the size value on the parent. This change triggers infinite recalls as the prop is a signal and changing the signal retriggered the $effect rendering and filling up the memory limit of the browser tab. I ended up having another gameSize state and have to check inside the $effect if size !== gameSize then allow new render. It took me 2 hours to figure that out and it sucks. It felt really backwards to not able to use the prop as a signal and still need to have it's internal state like it's an angular app lol.

[@l3ss1sm0r3]

One horrible thing that happened to me when using a BfF is that it caused horrible race conditions in combination with (session) cookies. Also, having the BFF without a locking mechanism or sensible way of serializing operations with a remote service (especially when having to use refresh tokens and the remote server invalidates them once used) is a problem. Modeling that in BEAM processes seems one of the only nice ways to handle that. Sadly, in the project we had that problem, we used python, and collapsing the stack into a monolith was easier.

[@Luisllaboj19]

Pre-watched

[@Luisllaboj19]

on stream :p

[@feelingfun5149]

Theo! It's a second video in a row that I wanna watch from start to finish!😃👍

[@PirataEscondido]

Hey Google set reminder to watch this video in 3 years

[@CocoLui-i7l]

whats app he using for diagrams?

[@jbest84]

Excalidraw

[@kabukitheater9046]

nuxt not mentioned smh

[@mayuinc]

You're an awesome teacher 💪

[@OhDevBeard]

Svelte for 2025 🎉

[@johnnygri99]

Theo, build something with Angular 19 and review the experience!

[@pry0rity-vids]

prisma back?

[@epsilondelta-l1g]

I'm going back to jquery

[@Extjac]

I was looking for this

[@noahtah1511]

Saving for later but leaving comment for auto. Sending love and respect Theo and Theo fans

[@KevinArellano]

I work with Graphql all day everyday, and I like it. Can't understand someone not say `resolver` when working with graphql lol. I do want to learn tRPC though, it's on my to-do list

[@kocokan]

Meanwhile jquery devs with lamborghini:

[@jonnyso1]

Speaking from 2027, I'm here researching what you barbarians were up to in the past.

[@peteromano9356]

Hey man, you can't use vite or webpack compiler magic for type/javascript, and then shit on graphql codegen shenanigans. I mean you can, but would be good to recognize the double standard. From what I can tell so far, your trpc vs gql argument is like debating vanilla js vs any framework using webpack or vite

[@eduardoromaguera9707]

SRR is a mistake. They just want you to pay for cloud rendering when your users can do it 😊🤑

[@maduk22]

You don’t have to use this face with everything, it dosnt suit this topic , please make new ones

[@George-e9c2x]

React was too busy making your website slower in 2024.

[@FarqMuckerberg]

It actually causes more problems than its solves and I'm not even exaggerating.

[@vutruong4164]

Lmao dude try his best to not put Angular inside his thumbnails when videos have to do with JS frameworks.

[@Ava-x9z3n]

one of the first comments, theo pls reply to this im a big fan

[@userj-s2000]

Wait js frameworks are just react wrappers

[@FUNNYcheese0806]

definitely next js

[@hicoop]

I've been bouncing around complete stacks for a while. I feel like react is the best way to build user interfaces but meta-frameworks like nextjs are so unreasonably complicated. On the other hand, a simple express api server is easy to configure but now your api lacks typesaftey. Right now I am using a bun monorepo with a trpc backend and a react router frontend. I use drizzle for my ORM and I can directly pass types to the frontend while I have a clear abstraction of server and client. I don't use things like server actions or streaming, just react query and ssr when I need. Would love to hear others thoughts

[@miro-hristov]

I miss when your videos were 10 min long

[@t3dotgg]

My average video length is around 30 minutes long lol. It's rare I do short ones

[@miro-hristov]

​@@t3dotgg I know... was just playing the role of the "worst commenter" @6:29

[@mehdi-idham]

first

[@FarqMuckerberg]

His diagrams prove the point that Js has become way too complicated... Think about the front-end and how simple and well engineered SwiftUI is for the desktop and mobile. Javascript needs to die it's a terrible language riddled with congenital defects and its further proliferation is a cancer that is sucking the life out of a new generation of developers. You can't engineer your way out of bad design. A language created in a week or weekend is inadequate to run the web for the next 20 years. We need new solutions! You can keep slathering new coats of paint on the same piece of garbage but it doesn't change the fact that its a effing piece of garbage. Web3 is the only hope to turn shit around and hopefully move to a more decentralized language stack let us not forget that Js is still mostly controlled by big tech.

[@UnknownPerson-wg1hw]

so many words for nothing, web3 my ass

[@JLarky]

I read the article, i watched Ryan read it on his stream. I watched Theo read it on his stream. Why am i watching the recording now? 🫣