The big thing is that it's an hybrid type of framework which can handle front reactivity directly, so it's a bit different than, for example, a Symfony website. But it's surely not new, the Phoenix framework does this for several years. And there's also Astro for Javascript.
(Sorry, acting a bit like a Ryan Carniato deadhead but his enthusiasm for these kind of topics is kind of infectious.)
Hydration is one solution to a problem that Paul Lewis raised way back in 2016
Paul Lewis
@aerotwist
This is why I prefer Progressive Rendering + Bootstrapping. I’d love to see more frameworks support this approach:
16:39 PM - 09 May 2016
Phoenix LiveView (2018) is essentially a means of building a server-side-VDOM-based SPA implemented in Elixir (backed by the Erlang VM to handle client state on the server side) mostly in an attempt to decouple application development from the unstable nature of the JavaScript ecosystem.
As such LiveView is very clear about the constraints that it operates under.
And Astro drives the point home about how Node currently predominates.
Nate Moore
@n_moore
Fun fact—Preact plays a huge role in the history of Astro!
Oh boy... You clearly expanded my understanding on frontend frameworks 😅 Very interesting articles, thanks a lot for that !
It handles hydration which is entirely different from reactivity.
Indeed. Instead of talking about reactivity I should have said "interactivity" which was more what I have in mind.
Sorry, acting a bit like a Ryan Carniato deadhead but his enthusiasm for these kind of topics is kind of infectious.
Well... click Followed too.
Perhaps sometime in the future they'll expand to the edge and perhaps it is then that Deno will become relevant to them.
In fact, that was my point earlier, I'll try to explain it a bit. I think that there are a whole bunch of different frameworks out there and only the most knowns (or should I say: the most trendy) will be used. But TypeScript takes more and more space into companies' stacks. And adopting Deno instead of Node seems to be the fair suite to this. And then... Fresh. It would take some years for that but... I'm willing to take a gamble 😄
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The big thing is that it's an hybrid type of framework which can handle front reactivity directly, so it's a bit different than, for example, a Symfony website. But it's surely not new, the Phoenix framework does this for several years. And there's also Astro for Javascript.
Ok, primed myself with
and running with it.
It handles hydration which is entirely different from reactivity.
Why Efficient Hydration in JavaScript Frameworks is so Challenging
Ryan Carniato for This is Learning ・ Feb 3 ・ 9 min read
How React isn't reactive, and why you shouldn't care
Ryan Carniato for This is Learning ・ Mar 18 '21 ・ 6 min read
(Sorry, acting a bit like a Ryan Carniato deadhead but his enthusiasm for these kind of topics is kind of infectious.)
Hydration is one solution to a problem that Paul Lewis raised way back in 2016
Phoenix LiveView (2018) is essentially a means of building a server-side-VDOM-based SPA implemented in Elixir (backed by the Erlang VM to handle client state on the server side) mostly in an attempt to decouple application development from the unstable nature of the JavaScript ecosystem.
As such LiveView is very clear about the constraints that it operates under.
And Astro drives the point home about how Node currently predominates.
However Astro supports a number of other client side frameworks as well. So anybody adopting Astro will stick to Node.js.
Perhaps sometime in the future they'll expand to the edge and perhaps it is then that Deno will become relevant to them.
Patterns for Building JavaScript Websites in 2022
Ryan Carniato for This is Learning ・ Jun 8 ・ 9 min read
Oh boy... You clearly expanded my understanding on frontend frameworks 😅 Very interesting articles, thanks a lot for that !
Indeed. Instead of talking about reactivity I should have said "interactivity" which was more what I have in mind.
Well... click Followed too.
In fact, that was my point earlier, I'll try to explain it a bit. I think that there are a whole bunch of different frameworks out there and only the most knowns (or should I say: the most trendy) will be used. But TypeScript takes more and more space into companies' stacks. And adopting Deno instead of Node seems to be the fair suite to this. And then... Fresh. It would take some years for that but... I'm willing to take a gamble 😄