The new wave of JavaScript web frameworks
frontendmastery.com
The new wave of JavaScript web frameworks
1–10 of 28 posts
Re: The new wave of JavaScript web frameworks
#2The article doesn’t seem to give enough weight to GraphQL: it’s only mentioned in passing even though it solves the waterfall request problem mentioned much later in another context.
Re: The new wave of JavaScript web frameworks
#3The article doesn’t seem to give enough weight to GraphQL: it’s only mentioned in passing even though it solves the waterfall request problem mentioned much later in another context.
GraphQL isn't a web framework though.
----
I wonder if GraphQL is destined for the same type of evolution; React was a revelation compared to what came before, hugely popular, with a heavy client library and runtime costs. I see some of those in GraphQL
The new wave of svelte and quik etc are faster and lighter, by pre-compiling or rethinking how and when the work is performed
Re: The new wave of JavaScript web frameworks
#4The article doesn’t seem to give enough weight to GraphQL: it’s only mentioned in passing even though it solves the waterfall request problem mentioned much later in another context.
GraphQL isn't a web framework though. ---- I wonder if GraphQL is destined for the same type of evolution; React was a revelation compared to what came before, hugely popular, with a heavy client library and runtime costs. I see some of those in GraphQL The new wave of svelte and quik etc are faster and lighter, by pre-compiling or rethinking how and when the work is performed
[deleted]
Re: The new wave of JavaScript web frameworks
#5Nice overview, especially for those of us working long term projects and locked into whatever framework the originals devs chose. I wish I had time to try all these things out, but it’s tough to keep up.
Interesting that angular, and especially angular 2, only gets a passing mention.
Re: The new wave of JavaScript web frameworks
#6This wasn't mentioned in the article but IMO belongs as the last section of the timeline -- To (one of) the points made in https://news.ycombinator.com/item?id=32959397, the latest wave of Javascript frameworks wants to answer: how can we build apps like Linear or Figma in the browser? https://replicache.dev/ is the most direct example of this, and https://cord.com/ is an example of a service to add multiplayer elements in a non-framework way without rewriting the way your app works. Also know of one that still hasn't launched yet.
IMO this newest wave is creating frameworks that have existed in the mobile app world for a while and are now showing up for productivity-oriented web apps.
Re: The new wave of JavaScript web frameworks
#7This wasn't mentioned in the article but IMO belongs as the last section of the timeline -- To (one of) the points made in https://news.ycombinator.com/item?id=32959397 , the latest wave of Javascript frameworks wants to answer: how can we build apps like Linear or Figma in the browser? https://replicache.dev/ is the most direct example of this, and https://cord.com/ is an example of a service to add multiplayer elem…
True! I would also include https://liveblocks.io to that list of services that help developers make multiplayer experiences.
Interesting to see more players in this space to help more and more developers do this.
Re: The new wave of JavaScript web frameworks
#8This wasn't mentioned in the article but IMO belongs as the last section of the timeline -- To (one of) the points made in https://news.ycombinator.com/item?id=32959397 , the latest wave of Javascript frameworks wants to answer: how can we build apps like Linear or Figma in the browser? https://replicache.dev/ is the most direct example of this, and https://cord.com/ is an example of a service to add multiplayer elem…
True! I would also include https://liveblocks.io to that list of services that help developers make multiplayer experiences. Interesting to see more players in this space to help more and more developers do this.
Liveblocks looks great, thanks for mentioning! Will try it out sometime
Re: The new wave of JavaScript web frameworks
#9Another article about web dev that fails to mention bare metal web components and Lit. How does this keep happening?
While it's true that bare metal web components don't handle routing or state for you, in many apps those are problems that you can solve yourself -- and in a way that makes sense to you, rather than to the framework developer.
In my experience with Lit and bare metal (browser standards-based) web components that you hand-craft (not from a library), there are fewer bugs and the ones that exist are ones you designed -- rather than ones that come from a misunderstanding of a framework. Without a framework to learn, your cognitive load consists of only your own inventions and abstractions -- which are far easier to remember and deal with than something designed by a committee and documented with some largess.
Re: The new wave of JavaScript web frameworks
#10Nice overview, especially for those of us working long term projects and locked into whatever framework the originals devs chose. I wish I had time to try all these things out, but it’s tough to keep up. Interesting that angular, and especially angular 2, only gets a passing mention.
Google itself has moved on from Angular. They invented Lit, the anti-framework, which has far less scaffolding and cruft and is based on browser standards.