SuperDoc is an open‑source DOCX engine that parses and renders real .docx files in the browser with full format fidelity, offers one‑click integration for major front‑end frameworks, real‑time Yjs collaboration, and AI‑driven document automation.
WasmGC introduces native garbage‑collection support to WebAssembly, enabling Kotlin and Dart to run as true native languages on the web, dramatically shrinking bundle sizes, speeding startup, eliminating memory‑leak cycles, and improving interop, with full browser support now standard across Chrome, Firefox, and Safari.
WebAssembly isn’t just a speed boost for browsers; it fills the gaps where JavaScript struggles by handling heavy computation, binary processing, cross‑language reuse, strong isolation, and multi‑platform core logic, making it a practical engineering tool for today’s complex web applications.
This article chronicles the rise and fall of Java Applets from their 1995 debut, through their golden era and technical limitations, to their eventual removal from browsers and the JDK, and shows how WebAssembly inherits the original vision of high‑performance compiled code in the browser.
This article walks developers through setting up Lighthouse to evaluate Thorium’s web performance, explains the benchmark scores, and provides concrete GN and V8 configuration tweaks, media‑codec settings, and JavaScript optimizations to achieve higher Lighthouse ratings.
WebMCP, a new browser‑level Model Context Protocol co‑developed by Google and Microsoft, replaces fragile visual scraping with a structured API that lets websites expose tools directly to AI agents, dramatically improving token efficiency, reliability, and security while raising new implementation and safety challenges.
brow6el is a terminal‑only web browser that leverages the Sixel bitmap format and the Chromium embedded framework to deliver fully rendered pages, mouse input, bookmarks, download management, ad‑blocking, and Vim‑style navigation, offering a privacy‑focused alternative to AI‑laden mainstream browsers.
This article explains how Pyodide compiles CPython to WebAssembly, allowing developers to run complete Python—including libraries like Pandas, NumPy, and Matplotlib—directly in the browser without any server, installation, or build system, and demonstrates a practical CSV‑viewer example.
A developer turned the browser’s URL bar into a 40×4 pixel playground, using Unicode Braille characters and less than 400 lines of JavaScript to create a fully playable Snake game that updates the address bar in real time.
This article explains the browser's same‑origin policy, why it exists to prevent attacks such as XSS and CSRF, how origins are defined by protocol, host and port, and how CORS, simple requests, and preflight requests enable controlled cross‑origin communication.
This article explains why traditional asynchronous requests often fail during page unload, and demonstrates two modern browser APIs—navigator.sendBeacon and fetch with keepalive:true—that reliably transmit small data without blocking the user experience.
Pest v4 introduces Playwright‑based browser testing, Laravel integration, flexible device modes, parallel execution, smoke and visual regression checks, test sharding, and new assertions, providing a comprehensive upgrade for PHP developers seeking modern, fast, and reliable test automation.
Perplexity AI has proposed a $34.5 billion cash deal to acquire Google’s Chrome browser, aiming to leverage its 3 billion‑user base for an AI‑search advantage, while Google denies any sale and faces antitrust scrutiny and security challenges.
This guide explains how to use the native MediaRecorder API to capture screen, audio, or canvas streams in the browser, walk through a three‑step implementation—getting the stream, recording it, and handling the output—and shares best practices for compatibility, MIME types, user permissions, resource cleanup, and performance.
This article explains WebRTC’s peer‑to‑peer architecture, common use cases, performance metrics, how it works with STUN/TURN/ICE, compares it to WebSockets, and outlines future trends for real‑time communication in web applications.
WebVM is a serverless, client‑side virtual environment that runs an unmodified Debian Linux distribution in the browser via WebAssembly, offering a complete Linux toolchain, graphical interface, network support, AI assistant integration, and flexible deployment options.
This article shares practical browser tricks—including switching to Edge for seamless password sync, three indispensable extensions, and key shortcut keys—to help developers work faster and more efficiently across PCs, tablets, and phones.
This article explains why the ChatGPT browser-based conversation system prefers EventSource over WebSocket, covering protocol basics, the system’s single‑direction communication model, long‑polling behavior, deployment simplicity, and includes full Node.js server and client code examples demonstrating the implementation.
This article explains the underlying browser mechanisms that cause page jank when creating millions of DOM elements, analyzes the event loop, rendering pipeline, macro‑ and micro‑tasks, and presents practical solutions such as setTimeout, requestAnimationFrame, MessageChannel, and requestIdleCallback to keep the UI responsive.
Amid a U.S. antitrust trial that could force Google to divest Chrome, OpenAI’s ChatGPT product lead says the company would consider buying the browser, while both firms navigate past negotiations and future AI‑driven search ambitions.
A teenage developer has ingeniously run a full Linux system inside a PDF by adapting the TinyEMU RISC‑V emulator to asm.js and using PDF‑embedded JavaScript, enabling interactive command‑line access via a virtual keyboard in Chromium‑based browsers.
This article introduces Playwright, explains its key features, guides readers through installing the tool and its dependencies, demonstrates how to launch Chromium, Firefox, and WebKit browsers with Python code, and shows common configuration options such as headless mode, timeouts, and proxy settings.
The article explains why browsers limit concurrent connections per domain for performance and security reasons, compares HTTP/1.1 and HTTP/2 handling of these limits, and outlines practical frontend optimization strategies such as domain sharding, CDN usage, resource bundling, and lazy loading.
This article explains why audio autoplay may fail in modern browsers, describes the role of the Media Engagement Index, shows how to diagnose the NotAllowedError, and provides a JavaScript solution that catches the error and prompts the user to enable playback.
WebVM is an open‑source project that lets you launch a complete Linux virtual machine inside a web browser, supporting multiple programming languages and enabling deployment via GitHub Pages without any local installation.
This article explains the complete browser navigation flow from URL entry to page rendering and provides practical optimization strategies for DNS resolution, HTTP protocols, CDN usage, and front‑end resources such as HTML, CSS, JavaScript, images, and fonts to improve performance and user experience.
This article explains the complete browser navigation process—from URL entry, DNS resolution, TCP and HTTP communication, to resource loading and page rendering—and presents practical optimization techniques such as DNS prefetch, HTTP/2, CDN usage, and HTML, CSS, JavaScript, and image improvements to boost frontend performance.
This article explains the complete browser rendering pipeline—from URL entry, DNS resolution, TCP/HTTP communication, resource loading, DOM/CSSOM construction, to page painting—and presents practical optimization strategies such as DNS prefetching, HTTP/2, CDN usage, and HTML/CSS/JS best practices to improve frontend performance.
This article explains the fundamentals of the same‑origin policy, its impact on DOM, web data and network requests, and provides a detailed overview of CORS, simple requests, preflight requests, and the necessary response headers to securely enable cross‑origin communication in modern browsers.
This article demystifies the JavaScript event loop, explaining how browsers and environments like Node.js manage asynchronous tasks through call stacks, macro‑ and micro‑task queues, and various implementation libraries, illustrated with clear code examples and comparisons across Chrome, Firefox, Safari, Edge, Electron, and Deno.
This article explains the mechanisms of frontend caching, covering HTTP cache headers such as Expires and Cache‑Control, browser memory and disk caches, negotiation strategies with ETag and Last‑Modified, and practical NestJS examples to improve web performance.
The newly founded non‑profit Ladybird project is building a privacy‑focused browser with its own engine, funded by industry veterans, open‑sourced under BSD‑2‑Clause, and aiming to challenge the dominance of Chromium‑based and WebKit browsers despite being in a pre‑alpha developer stage.
This article explains why developers—both frontend and backend—should understand browsers, covering user experience, compatibility, performance, security, and debugging, then traces the browser’s evolution from the early 1990s to modern multi‑process architectures, outlines core components, rendering engines, and current market share.
This article explains the importance of browsers for both front‑end and back‑end developers, outlines the historical evolution from early single‑process designs to modern multi‑process architectures, and details core components, rendering engines, and market share, providing a comprehensive technical overview.
The article walks through every step from typing a URL to final page rendering, detailing URL parsing, DNS lookup, TCP three‑way handshake and termination, HTTP request/response structure, congestion and flow control mechanisms, and the browser’s DOM, CSS, layout and painting processes.
This article explains step‑by‑step what occurs when a user types a URL and presses Enter, covering URL parsing, DNS resolution, TCP three‑way handshake and four‑way termination, HTTP request/response formation, and the browser’s rendering process, providing interview‑ready insights into web networking fundamentals.
This guide explains how to install Playwright, write Python scripts to launch a Chromium browser, locate and interact with page elements, ensure element presence using various waiting methods, and verify actions with assertions, providing practical code examples for web automation.
The new Transformers.js 2.7.0 release introduces text‑to‑speech capabilities, provides a simple browser demo, explains how to save audio with the wavefile NPM package, offers speaker selection from a large CMU Arctic dataset, and lists additional library updates.
The article explains how modern browsers let developers actively control resource loading order with Priority Hints and the fetchpriority attribute—using preload links, fetch requests, image tags, and script tags—to boost performance on limited bandwidth, while warning against overuse.
This article explains what the Back‑Forward Cache (bfcache) is, how it works across browsers, the page lifecycle events involved, common pitfalls that prevent caching, and practical testing methods to ensure optimal front‑end performance.
The article explains how StackBlitz's WebContainers, a browser‑based container environment, now fully integrates the WebAssembly System Interface (WASI), allowing near‑native speed, secure sandboxed execution of multiple languages such as Rust, Python, C/C++, and introducing new CLI tools and future language support.
JavaScript’s single‑threaded model can freeze the UI during heavy calculations, but Web Workers—dedicated or shared—run code in independent threads, communicate via postMessage, offer configurable options, follow a clear initialization‑active‑termination lifecycle, and can be debugged through Chrome’s inspection tools, enabling responsive, asynchronous processing.
Chrome’s new HTTPS‑First experiment automatically upgrades HTTP requests to HTTPS, warns about insecure downloads, and rolls out gradually, aiming to make the web safer by encrypting the majority of traffic while still handling edge cases gracefully.
This article explains the fundamentals of the Same‑Origin Policy, its security implications, and how Cross‑Origin Resource Sharing (CORS) works—including simple requests, preflight requests, and handling credentials—to help developers safely perform cross‑domain HTTP operations in browsers.
Chrome’s latest experiment aims to automatically upgrade all HTTP requests to HTTPS, detailing current HTTPS adoption rates, the new HTTPS‑First mode’s automatic upgrades, unsafe download warnings, phased rollout plans, and how users can enable the feature now for a more secure browsing experience.
Microsoft’s aggressive bundling of Edge into Windows 11—through default‑browser prompts, Outlook and Teams link handling, widget redirection, and the Windows Copilot‑Edge tie‑in—has sparked widespread criticism, prompting users to adopt workarounds like the open‑source MSEdgeRedirect tool.
This article explains the browser's critical rendering path, detailing how HTML is parsed into a DOM, how CSS is turned into a CSSOM, how the render tree is built, and how JavaScript and CSS can block or delay rendering, providing practical examples and performance testing results.
This comprehensive guide explains browser fundamentals, covering process and thread architecture, single‑ and multi‑process models, the V8 engine's data types, property ordering, memory allocation and garbage collection, compilation stages, the event loop, rendering pipeline, performance optimization techniques, and security mechanisms.
This article introduces WebAssembly, tracing its evolution from asm.js and NaCl to the modern binary format, outlines its performance, portability, and security benefits, and demonstrates its practical use by building a Mandelbrot set application with AssemblyScript and WebAssembly in the browser.
This article surveys the diverse scenarios where WebAssembly is applied—from accelerating web applications and providing sandboxed plugins to powering cloud‑native workloads, edge computing, serverless functions, mobile/IoT devices, and blockchain—while also outlining current challenges and future development directions.
This article explains how browsers handle TCP connections and SSL sessions when loading pages with many images, covering connection persistence, request multiplexing, HTTP pipelining limitations, per‑host connection limits, and the advantages of HTTP/2 multiplexing for efficient resource fetching.
This article explains how modern browsers use multi‑process architectures, detailing the evolution from single‑process models, the roles of browser, renderer, GPU, network, and plugin processes, and walks through the navigation and rendering pipelines—including DOM construction, style calculation, layout, layering, painting, rasterization, compositing, and their impact on performance.
The article details Chromium’s rendering pipeline, tracing how network bytecode becomes on‑screen pixels through 13 stages—from parsing and style calculation to layout, painting, compositing, tiling, rasterization, activation, aggregation, and final display—while explaining process models, component formulas, and synchronous versus asynchronous raster strategies.
This article explains the requestAnimationFrame API, demonstrates basic and cancelable animation examples, discusses its execution timing within the browser frame lifecycle, compares its performance to setTimeout, covers compatibility and polyfills, and shows how to wrap it in a React hook for practical use.
This article explains the fundamentals of JavaScript's event loop, covering browser asynchronous execution, macro‑ and micro‑tasks, timer inaccuracies, view rendering, and the differences in Node.js implementation, while providing code examples to illustrate execution order and practical implications for developers.
Bilibili designed a self‑built live‑streaming P2P system that uses WebRTC DataChannels and a Tracker‑mediated handshake to exchange 60 KB MessagePack‑encoded HLS segment blocks among viewers, employing a free‑market task allocation to balance seeding and consumption, thereby significantly cutting CDN bandwidth costs.
Bilibili built a browser‑native live P2P streaming system that uses WebRTC data channels to exchange 60 KB‑sized HLS segment blocks via a WebSocket tracker, employs MessagePack for efficient binary messaging, and adopts a decentralized free‑market peer‑role allocation to limit uploads, dramatically cutting bandwidth while supporting massive concurrent viewers.
This article explains the fundamentals of JavaScript's event loop, covering single‑threaded execution, the role of macro‑tasks and micro‑tasks, differences between browser and Node.js implementations, and includes code examples that illustrate task scheduling and execution order.
Ladybird, an open‑source cross‑platform browser created by SerenityOS author Andreas Kling, evolved from a LibWeb debugging tool into a full GUI browser, leveraging SerenityOS’s LibWeb, LibJS, and Qt, and currently runs on Linux, macOS, Windows (WSL) and Android, though still early‑stage.
Xterm.js is a TypeScript‑based front‑end terminal component that provides fast, GPU‑accelerated, Unicode‑rich, self‑contained terminal emulation for web applications, with detailed installation steps, ES6 imports, plugin architecture, browser and Node.js support, and extensive real‑world usage examples.
This article introduces several browser-based emulations of classic Windows and macOS systems, providing direct links to experience these nostalgic operating environments online without any installation or heavy resource consumption.
This article introduces PyScript, a framework that embeds Python code in HTML via WebAssembly, and Goscript, a Go playground that runs Go code in the browser, detailing their underlying technologies, components, and available resources for developers interested in client‑side language execution.
PyScript, announced by the creators of Anaconda, is a browser‑based Python framework that lets developers embed Python code in standard HTML, call JavaScript libraries, manage environments, and build interactive web applications using familiar Python packages.
PyScript, a new framework from Anaconda, enables developers to embed and run Python code directly in standard HTML pages, offering first‑class Python support in the browser, seamless integration with JavaScript, package management, and UI components, all built on the Pyodide WebAssembly engine.
This article introduces PyScript, a framework that lets developers embed Python in HTML via WebAssembly, and Goscript, a Go playground that runs Go code in the browser, detailing their architectures, components, and links to source repositories.
Google has opened a Gerrit code review to evaluate Qt as a UI platform for Chromium, revealing early‑stage commits, a brief overview of Qt’s capabilities, and a comparison of the UI frameworks currently used across Chrome’s various operating systems.
Chrome 100, the first three‑digit release of Google’s browser, arrives across macOS, Windows, Android and iOS with a new icon design, removal of Lite mode, a multi‑screen window placement API, and warnings that the version change may affect user‑agent parsing libraries, while Google touts lower memory and CPU usage.
This article explains how JavaScript's single‑threaded engine uses the event loop to manage synchronous and asynchronous tasks, distinguishes macro‑tasks from micro‑tasks, and compares the implementations in browsers and Node.js, including version‑specific behavior and common pitfalls.
This curated list highlights essential frontend reads covering Chrome's rendering pipeline, cross‑platform fundamentals, Vue/React hooks, Vite's architecture, Lottie camera tricks, Engine.IO mechanics, Remix vs Next.js, a hand‑written Babel tokenizer, React performance nuances, and state‑machine approaches to simplify complex UI logic.
Chrome 100 beta adds two new web APIs—the Multi‑Screen Window Placement API for managing multi‑window applications across displays, and the Digital Goods API for handling in‑app purchases—along with other updates, with the stable release expected by the end of March.
HTTP Cache‑Control defines how browsers, proxies, and origin servers coordinate caching through directives like public, private, max‑age, no‑store, and revalidation, enabling developers to control freshness, reduce server load, save bandwidth, and improve user experience while avoiding stale‑content issues.
The article highlights Huawei’s recruitment of a young ICPC champion, discusses corporate policies at Tencent and Panasonic, and introduces Chrome 97’s new WebTransport API for secure, low‑latency web communication.
Chrome 97 adds the controversial Keyboard MAP API, enabling web apps to detect users’ keyboard layouts for better input handling, but raising privacy concerns as Apple, Mozilla and Brave criticize its potential for tracking, while Google cites improved user experience.
This article explores the evolution of browsers, the layered architecture of front‑end development, the role of standardization bodies, and how understanding browser internals—from multi‑process models to JavaScript engines—helps developers write more efficient, compatible, and future‑proof web applications.
This article introduces WebTorrent, an open‑source JavaScript library that brings BitTorrent‑style peer‑to‑peer file sharing and streaming directly to browsers using WebRTC, explains its advantages over traditional download tools, and provides step‑by‑step code examples for both web and Node environments.
This article explores rendering performance optimization from a hardware viewpoint through to front‑end rendering, detailing the three stages of perception, healing, and corrosion, the critical rendering path, CRP analysis, and practical strategies such as NEON acceleration, OOPD/OOPR, and Lighthouse tooling to achieve smoother, lower‑power web experiences.
Since 2018, Firefox has lost 46 million monthly active users, dropping from 244 million to 198 million, as users favor Chromium‑based browsers for better performance, default status, and privacy concerns, prompting a call for continued support of Firefox as a vital anti‑monopoly alternative.
This article explores the essence of rendering performance optimization by examining hardware trade‑offs, rendering and computation perspectives, the critical rendering path, and practical strategies—including toolchains like Lighthouse and the Navigation Timing API—to systematically improve front‑end speed and efficiency.
This article explains the ESModule standard, compares it with CommonJS and AMD, describes how Node.js and modern browsers implement ESModules, discusses compatibility challenges with third‑party dependencies, and reviews next‑generation tools such as Snowpack and Vite that leverage native module loading.
This article explains the ESModule standard, compares its server‑side (Node.js) and browser implementations, discusses compatibility issues with CommonJS, examines the difficulties of using third‑party dependencies in browsers, and outlines emerging tools such as Snowpack and Vite that leverage native ESModules.
This article recounts a technical interview where the author explains the complete lifecycle of a browser request—from URL parsing, DNS resolution, TCP handshake, and caching strategies to DOM construction, rendering, and performance optimizations—providing concise answers and practical tips for front‑end developers.
This article walks through the complete lifecycle of a browser request—URL parsing, DNS lookup, TCP handshake, OSI‑layer transmission, caching strategies, HTML rendering, and performance optimizations—mirroring real interview questions faced by front‑end engineers.
This article provides a comprehensive overview of HTTP caching mechanisms, detailing cache‑related header fields, browser behaviors, legacy and modern directives, validation techniques, and practical tips for configuring efficient cache strategies in web applications.
This article walks through the complete journey of a URL entered in a browser, covering URL parsing, DNS lookup, TCP handshake, OSI‑layer packet transmission, caching strategies, HTML parsing, rendering pipeline, and practical performance‑optimisation tips.
The article explains the concept of locks, introduces the Web Locks API for synchronizing resource access across scripts, details its request workflow, optional parameters, potential risks such as deadlocks, and notes browser compatibility, providing code examples for practical use.
This article introduces the Python‑based WebSSH tool that lets you access Linux machines through a web browser, outlines its key features, provides step‑by‑step installation and service‑startup commands, and explains how to configure root login for seamless remote management.
This article provides a detailed, front‑end‑focused walkthrough of the complete browser request‑response lifecycle—from URL parsing and DNS lookup through TCP connection, HTTP handling, HTML/CSS parsing, JavaScript execution, to final page rendering—highlighting key concepts, common pitfalls, and optimization tips.
This article explores why JavaScript includes an event loop, explains its core mechanisms—including task and microtask queues—and compares how browsers and Node.js implement the loop, using code examples and diagrams to clarify the differences.
This article provides a detailed, step‑by‑step explanation of how a browser processes a simple HTTP request—from URL parsing, DNS lookup, and TCP connection through server handling, response reception, HTML/CSS parsing, layout, painting, reflow/repaint, and JavaScript execution—highlighting key concepts, optimizations, and common pitfalls.
This article explains how Chrome uses multiple processes, the fundamentals of TCP/IP reliability, the HTTP request lifecycle, caching mechanisms, and the step‑by‑step flow from entering a URL to rendering a page, providing essential knowledge for front‑end interviews.
The article explains JavaScript’s single‑threaded execution stack and how the event loop—using an event queue, micro‑tasks, and macro‑tasks—coordinates asynchronous operations in browsers and Node.js, detailing libuv’s stages and showing how this model enables non‑blocking, concurrent programming.
Learn how to create a browser‑compatible MNIST image classification model using TensorFlow.js, covering data preprocessing with sprite images, model construction, training, and evaluation, while providing complete JavaScript code examples and practical tips for handling ArrayBuffer, DataView, and visualization.
This article reviews Microsoft’s new open‑source portal, Google’s Chrome URL‑hiding experiment, the YAM cryptocurrency bug that locked millions, and the launch of Bootstrap’s official SVG icon library, highlighting their goals, technologies, and community impact.
Browser caching works by storing copies of web resources in memory, disk, or service‑worker caches and using HTTP headers such as Cache‑Control, Expires, ETag, and Last‑Modified to decide freshness, allowing strong (local) and negotiated (weak) cache stages, while developers can fine‑tune performance with CDN settings, IndexedDB, Service Workers, and HTML5 storage to create optimal, auditable cache strategies.
The article explains how modern browsers manage TCP connections for HTTP requests, covering persistent connections, the limits on concurrent connections per host, the behavior of HTTP/1.1 pipelining, why SSL sessions may be reused, and how HTTP/2 multiplexing improves parallel request handling.
This article explains how Alipay’s MiniProgram development tools were migrated to a browser‑based WebIDE using the Kaitian IDE framework, detailing the architecture, startup optimization, plugin system, real‑world deployments, and future plans for a lighter Playground experience.
This article provides a thorough, step‑by‑step explanation of the entire browser request‑response cycle—including URL parsing, DNS lookup, TCP connection, server handling, response processing, and the detailed rendering pipeline—offering clear insight for developers and interview preparation.
This article explores the origins and purpose of the JavaScript event loop, explains how browsers and Node.js implement it with external and internal queues, compares their differences, and illustrates the concepts through detailed code examples and visual diagrams.
This guide shows how to access Chrome’s experimental flags to enable useful features such as webpage thumbnails, media controls, tab freezing, parallel downloading, and tab grouping, providing the exact flag URLs, configuration steps, and notes on version compatibility.
This article explains the fundamentals of HTTP caching, covering forced and conditional cache strategies, key response headers like Cache-Control, Expires, ETag, and Last-Modified, and demonstrates how browsers decide when to serve cached content versus fetching fresh data.
