JavaScript Frameworks in 2025

preview_player
Показать описание
2024 was kinda a slow year for JavaScript frameworks, which begs the question: what's 2025 gonna look like?

S/O Ph4se0n3 for the awesome edit 🙏
Рекомендации по теме
Комментарии
Автор

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.

MatthewSparks
Автор

13:39 "If you don't use JavaScript on the server _some_ amount, you are almost certainly making a bad website."

Too hot. Way too hot of a take. Data streaming is a fun UX win, but sites without it are not "bad"

benbowers
Автор

To everyone confused about the BFF server:
It's purpose is to act as a middleware between backend API servers and the browser.
The benefits are:
- easy to bring in performance optimisations for the UI like combining multiple API calls into one
- data manipulations can be done without touching the backend. Far easier to change and deploy JS code
- reduced JS bundle size shipped to client since only the required UI can be shipped
- reduce the number of APIs exposed to the browser.

We have a BFF server in our main product and have realised these benefits for a long time. It's pretty good and the UI team gets a lot of control to maintain quality

StingSting
Автор

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

davidbronke
Автор

When Vercel sells all its servers, we might see something new.
Vercel sells servers, Tailwind sell components, and TanStack sell courses — that’s all you need to know about modern technologies. In reality, we aren’t inventing new technologies; we’re finding more sophisticated ways to make money

_RideTheTrip
Автор

Corporate stack is still 10 years behind

DevanConrad
Автор

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

boiserunner
Автор

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.

ndykman_pdx
Автор

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.

gageracer
Автор

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.

_yya
Автор

Reminder to come back in 2028 to watch this video again.

FuwakamiMana
Автор

React is the definition of a foot gun for me. I don't really get why anyone would use it instead of vue, svelte or even lit.

grinskks
Автор

3:48 doesn’t Rust for a REST API get you like double the RPS of Go though?

owenwexler
Автор

8:55 oh that's called optimistic update

as_if
Автор

Nuxt has made web dev much simpler and easier

QueeeeenZ
Автор

13:24 To some amount I disagree with that statement, you can have a descent user experience having no BFF. On the other hand the complexity it brings is tedious, for it you need to review, build, test, deploy, cache strategies, metrics, analytics, and lets not forget that in every 300 lines of code there is a bug.

TheBoazhoch
Автор

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

johnnygri
Автор

Honestly, embedding a SPA into one of my MPA because I don't want to deploy a other proyect is something that I've done several times

Danielo
Автор

Vue + Vite won for me in JS wars.
Now I am learning Elixir + Phoenix + Liveview for fullstack stuff.

jsonkody
Автор

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.

ymi_yugy