There is a lot of confusion right now about the push to render JavaScript applications on the server-side. Part of this has to do with the awful terminology, but mostly it has to do with the fact that it's a fundamental shift in how we architect and deploy these apps, and the people peddling this idea (myself included) have not done a great job motivating the benefits.
The many, many, many JavaScript runtimes of the last decade
This last decade has seen an inundation of new JavaScript runtimes (and engines in equal measure), enabling us to run JavaScript in all manner of contexts...
2021 JavaScript Rising Stars
A complete overview of the JavaScript landscape in 2021: trends about front-end and Node.js frameworks, React and Vue.js ecosystems, build tools, state management...
Thinking about going with PreactJs for dev.to
The dev.to web application has been built on "vanilla" JavaScript for performance purposes specific...
Next.js — The Perpetual Beta Framework
Exploring 6 years of Next.js, from early days to App Router & RSC, with migrations, performance tweaks, and framework insights
State of JS 2020
The annual survey about the latest trends in the JavaScript ecosystem.
developit/htm
Hyperscript Tagged Markup: JSX alternative using standard tagged templates, with compiler support.
State of the Art JavaScript in 2016
State of the Art JavaScript in 2016 So, you’re starting a brand new JavaScript front end project or overhauling an old one, and maybe you haven’t kept up with the breakneck pace of the ecosystem …
Frontend Minimalism in Action: Do More With Less JavaScript | Peter Kröner | webinale Berlin 2026
Why JavaScript Developers Should Prefer Axios Over Fetch
Backward=compatibility, monitoring upload progress, and more
React Server Components: Do They Really Improve Performance?
A data-driven comparison of CSR, SSR, and RSC under the same app and test setup, focusing on initial-load performance and the impact of client- vs server-side data fetching (including Streaming + Suspense).
Component Party
Compare JavaScript frameworks side-by-side: React, Vue, Angular, Svelte, Solid.js, and more. See syntax differences, features, and code examples for web development frameworks.
The viability of JS frameworks on mobile
Whether I like it or not, not everyone using my web apps will be running iOS 9 on an iPhone 6S or a Nexus 6P and connecting via super-speedy wifi.
A brief history of JavaScript | Deno
In 30 years, JavaScript went from being a little scripting language to one of the world's most popular. Here are key moments to show how it has evolved and where it is headed.
The Incredible Overcomplexity of the Shadcn Radio Button
Radio buttons are built into web browsers. Why are we using a UI library that wraps another UI library that rebuilds radio buttons from scratch? Why does rendering a radio button require multiple dependencies and several kilobytes of JavaScript? How did we make a built-in browser control so complicated?
You should know this before choosing Next.js
Picking the technology stack for a project is an important and consequential decision. In the enterprise space in particular, it often involves a multi-year commitment with long-lasting implication...
State of JavaScript 2022
The 2022 edition of the annual survey about the latest trends in the JavaScript ecosystem.
