Tag
Every modern JavaScript framework eventually runs into the same wall: the more interactive a site gets, the more JavaScript the browser has to download, parse, and execute before anything actually works. This article breaks down why that happens, walks through Qwik.js's alternative approach called resumability, and puts both ideas to the test with a real side by side performance comparison against Next.js.
Most modern frameworks start from the assumption that a website is an application. Astro starts from the opposite assumption: most websites are content, and content doesn't need a JavaScript bundle to exist. This article breaks down Astro's islands architecture, its component model, and the rendering, content, and state management choices that make "ship zero JavaScript by default" an actual, practical strategy rather than a slogan.
Hybrid rendering, headless CMS architectures, and Progressive Web Apps are usually treated as separate trends in modern web development. This post summarizes a bachelor thesis that asks whether they can instead be meaningfully combined, and tests that question by building MovieRec, a movie discovery platform using Next.js and Strapi.
This article documents a university full-stack project in which a coupon-sharing web app called Skimp was built entirely in JavaScript, using the MERN stack (MongoDB, Express, React, Node.js). It walks through the architectural decisions, the concrete implementation challenges, and an honest evaluation of what worked and what didn't.