@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.

@ofadiman

You guys are not using jQuery? 😮

@DevanConrad

Corporate stack is still 10 years behind

@StingSting844

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

@_y7ya

Man your diagrams are something else.

@benbowers3613

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"

@FuwakamiMana

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

@lxn7404

There should be a framework to help you choose a framework at this point

@_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.

@davidbronke5484

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

@dennissam989

Vue vapour, knocking the door.

@QueeeeenZ

Nuxt has made web dev much simpler and easier

@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.

@rvmonprod

hey theo, awesome video you did here!

i was wondering if you could do like a complete WebDev / Build your own Stuff in 2025 Video that covers all the basics one should know

like the main tech steck you should use, tools to integrate like supabase/resend/..., best practices for deploying (with v0, netflify etc..), how to approach backend and frontend

just like a 101 to catch people like me, that use the possibilites of AI to build their own business/product but dont really understand much of the technology behind it in detail
would be so awesome!

@jsonkody

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

@_____case

Deno Fresh 2.0 incoming.

@Danielo515

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

@kamiljanowski7236

Regarding the length of videos, they're onto something. I used to be able to listen to your videos while walking my dog. Now I'm done walking half way through the video and I finish before you get to the juice.

@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.

@Prezbar

Great content, thanks !