5 ms·

I think the next major change will be unified hybrid rendering. Render the initial view via SSR for speed, framework automatically injects more and more of the

I think the next major change will be unified hybrid rendering. Render the initial view via SSR for speed, framework automatically injects more and more of the page transparently as user-driven events happen. All of this will be transparent and you only write the app once.

pathartl 3y ago
I have been using Blazor for the past year and I've got to say it's pretty incredible. It has some downsides and .NET 8 with Blazor United is going to be a very welcome change, but I can have my cake and eat it too. I finally get to use components, write some client-side stuff in C#, and I don't have to touch a lick of JavaScript or TypeScript. I get how irritating it is for people to beat the "JS IS BAD" drum, but man, it's nice to use proper typing in a language that has some pretty damn good syntax.
xu_ituairo 3y ago
Do you mean something similar to Svelte becoming dominant?
- sanderjd 3y ago
  I think from the comments here: probably? I don't know anything about Svelte, so I can't really say, but you're the third person I've seen say "this sounds like Svelte", so I'm inclined to think you're all right :) So has it taken off / is it taking off? If not, why not? Or more to the point of my original comment: Why is something like this just now taking off? Has something new enabled this in the last few years? It's not a new idea was my point in my comment, so I'm curious why the idea never seemed to take off in the past, and why it might be poised to now.
- dinoreic 3y ago
  I can't understand how Svelte is not more popular. From first time I saw it 4y ago I thought it was game changer, did not change opinion.
sanderjd 3y ago
So, I was trying to do this literally a decade ago (as in, I remember it being 2013 when I started trying to make an angularjs site work this way). I haven't been doing front-end or "full stack" for awhile, so I'm a bit out of the loop. Why has this seemingly failed to progress in the last decade?
- PhoenixReborn 3y ago
  Most of the more modern Javascript SSR frameworks support hybrid in some capacity (Remix, Next, Svelte). I can't speak for Angular as I've never used it.
  - sanderjd 3y ago
    Oh, I didn't mean to focus the discussion on angularjs; that "angularjs" that I was using was essentially a totally different and now-deprecated framework from today's angular. I just meant it as an example of why I don't see this as an up-and-coming idea, but rather something that has been the clear best path for a very long time, but doesn't seem to have taken off. I don't know enough about any of the frameworks you mentioned to evaluate whether the "hybrid in some capacity" actually does mean this approach has become widely used, but I guess from my experience of using the web, it doesn't seem like it is common, it seems like most applications are still sending a skeleton and then filling the data in client-side, rather than rendering the initial page load server-side.
- badestrand 3y ago
  This is already here and in use. See Next.js using React.js for example. Server-side rendering out of the box and small next needed pieces are loaded continuously when they are needed.
  - sanderjd 3y ago
    Nice! Anecdotally this still doesn't seem to be the dominant way that web apps I use are implemented. Is this just taking awhile to get mindshare, or are there some drawbacks keeping most people from using it?
europeanNyan 3y ago
https://en.m.wikipedia.org/wiki/Hydration_(web_development) https://en.m.wikipedia.org/wiki/Hydration_(web_development)
tommy_axle 3y ago
That's what frameworks like NextJS do.
- eddd-ddde 3y ago
  No, I think it's more like qwik, no hydration, just html. SSR plus client logic when needed.
- deleted 3y ago
  [deleted]
Joeri 3y ago
This is what react server components is: the component tree renders on the server and is sent over a chunked http connection, gradually filling the page. The code is not sent to the client because events that necessitate a rerender go back to the server in a new request.

pathartl 3y ago

I have been using Blazor for the past year and I've got to say it's pretty incredible. It has some downsides and .NET 8 with Blazor United is going to be a very welcome change, but I can have my cake and eat it too. I finally get to use components, write some client-side stuff in C#, and I don't have to touch a lick of JavaScript or TypeScript. I get how irritating it is for people to beat the "JS IS BAD" drum, but man, it's nice to use proper typing in a language that has some pretty damn good syntax.

xu_ituairo 3y ago

Do you mean something similar to Svelte becoming dominant?

sanderjd 3y ago
I think from the comments here: probably? I don't know anything about Svelte, so I can't really say, but you're the third person I've seen say "this sounds like Svelte", so I'm inclined to think you're all right :) So has it taken off / is it taking off? If not, why not? Or more to the point of my original comment: Why is something like this just now taking off? Has something new enabled this in the last few years? It's not a new idea was my point in my comment, so I'm curious why the idea never seemed to take off in the past, and why it might be poised to now.
dinoreic 3y ago
I can't understand how Svelte is not more popular. From first time I saw it 4y ago I thought it was game changer, did not change opinion.

sanderjd 3y ago

So, I was trying to do this literally a decade ago (as in, I remember it being 2013 when I started trying to make an angularjs site work this way). I haven't been doing front-end or "full stack" for awhile, so I'm a bit out of the loop. Why has this seemingly failed to progress in the last decade?

PhoenixReborn 3y ago
Most of the more modern Javascript SSR frameworks support hybrid in some capacity (Remix, Next, Svelte). I can't speak for Angular as I've never used it.
- sanderjd 3y ago
  Oh, I didn't mean to focus the discussion on angularjs; that "angularjs" that I was using was essentially a totally different and now-deprecated framework from today's angular. I just meant it as an example of why I don't see this as an up-and-coming idea, but rather something that has been the clear best path for a very long time, but doesn't seem to have taken off. I don't know enough about any of the frameworks you mentioned to evaluate whether the "hybrid in some capacity" actually does mean this approach has become widely used, but I guess from my experience of using the web, it doesn't seem like it is common, it seems like most applications are still sending a skeleton and then filling the data in client-side, rather than rendering the initial page load server-side.
badestrand 3y ago
This is already here and in use. See Next.js using React.js for example. Server-side rendering out of the box and small next needed pieces are loaded continuously when they are needed.
- sanderjd 3y ago
  Nice! Anecdotally this still doesn't seem to be the dominant way that web apps I use are implemented. Is this just taking awhile to get mindshare, or are there some drawbacks keeping most people from using it?

europeanNyan 3y ago

https://en.m.wikipedia.org/wiki/Hydration_(web_development) https://en.m.wikipedia.org/wiki/Hydration_(web_development)

tommy_axle 3y ago

That's what frameworks like NextJS do.

eddd-ddde 3y ago
No, I think it's more like qwik, no hydration, just html. SSR plus client logic when needed.
deleted 3y ago
[deleted]

Joeri 3y ago

This is what react server components is: the component tree renders on the server and is sent over a chunked http connection, gradually filling the page. The code is not sent to the client because events that necessitate a rerender go back to the server in a new request.