Why JavaScript Developers Should Prefer Axios Over Fetch

Fetch Is Not Enough

The Fetch API gave JavaScript runtimes a shared vocabulary for HTTP. But HTTP has capabilities that Fetch can't express, and every runtime has diverged trying to work around the gaps.

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

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

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

You’re Missing the Point of Server-Side Rendered JavaScript Apps

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.

Thinking about going with PreactJs for dev.to

The dev.to web application has been built on "vanilla" JavaScript for performance purposes specific...

State of JS 2020

The annual survey about the latest trends in the JavaScript ecosystem.

Real-World React: Designing Frontend Architectures That Survive Production | Workshops | Faris Aziz

Most React workshops focus on building features. This one focuses on keeping them alive. In production, React applications fail in ways that local environments never show: partial outages, slow dependencies, silent errors, broken rollouts, and performance regressions that only appear under real traffic. This workshop is a practical, architecture-first walkthrough of how experienced teams design React systems that stay resilient, observable, and scalable long after the first release. We will explore how component architecture, reconciliation in practice, and runtime failure patterns shape performance and operability far more than memoization tricks or framework features. Using React and Next.js as shared reference points, we will work through concrete patterns for failure recovery, error containment, safe rollouts, and post-deployment confidence. This is a hands-on, experience-driven workshop based on real production constraints, tradeoffs, and lessons learned from operating large React applications at scale. Attendees will leave with a mental model for building frontend systems that can fail safely, recover quickly, and ship continuously without fear. Most of the workshop is framework and library-agnostic, but we'll use React and Next.js as our common ground for communication and examples. This is not an exhaustive masterclass; it's a conversation starter and experience share to jumpstart your journey toward battle-tested software architecture.

Progressive enhancement and JavaScript failure

Can progressive enhancement help to build JavaScript web apps that handle errors gracefully?

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

Stop Ignoring the Browser: The Biggest Frontend Shift in a Decade

Native browser APIs now provide powerful alternatives for routing, state management, and components. Never mind the frameworks, use the browser.

Developing with ReactJS: An Interview with Gatsby's Kyle Mathews | Netlify

Realize the speed, agility and performance of a scalable, composable web architecture with Netlify. Explore the composable web platform now!

Datastar: Modern web dev, simplified

You love building web apps with Python, and HTMX got you excited about the hypermedia approach -- let the server drive the HTML, skip the JavaScript build step, keep things simple. But then you hit that last 10%: You need Alpine.js for interactivity, your state gets out of sync, and suddenly you're juggling two unrelated libraries that weren't designed to work together. What if there was a single 11-kilobyte framework that gave you everything HTMX and Alpine do, and more, with real-time updates, multiplayer collaboration out of the box, and performance so fast you're actually bottlenecked by the monitor's refresh rate? That's Datastar. On this episode, I sit down with its creator Delaney Gillilan, core maintainer Ben Croker, and Datastar convert Chris May to explore how this backend-driven, server-sent-events-first framework is changing the way full-stack developers think about the modern web.

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 …