This article details the process of adapting the V8 JavaScript engine for HarmonyOS, covering engine selection, cross‑compilation using CMake and Ninja, toolchain configuration, building builtins and snapshots, and integrating the resulting library into native HarmonyOS applications.
This article explains why the Roma framework needs a JavaScript engine on HarmonyOS, compares mainstream JS engines, details V8's architecture and JIT pipeline, and provides a step‑by‑step process for cross‑compiling V8 with CMake, GN, Ninja and the HarmonyOS SDK, including code examples and tooling tips.
By replacing the default JavaScriptCore engine with Hermes for Hippy’s UI rendering in QQ Browser, the team cut module load time by 70‑80 %, lowered first‑frame latency and crash rate, kept memory usage comparable, and leveraged Hermes’s bytecode support and React‑Native ecosystem to dramatically improve startup performance.
The article explains the urgency of cross‑platform dynamic development for mobile apps, compares native and React Native approaches, details the role of JavaScript engines like V8 and JSI, and provides basic React Native code examples for building and styling components.
Thresh is a Flutter-based cross-platform dynamic solution for frontend developers that integrates the JavaScript Engine Interface (JSI) to streamline communication between JavaScript and Dart, reducing serialization overhead and thread switching, thereby improving startup and rendering performance on mobile devices.
The article surveys how major JavaScript engines represent the dynamic JSValue type—using QuickJS’s tagged unions, JavaScriptCore’s NaN‑boxing, SpiderMonkey’s nun‑/pun‑boxing, V8’s tagged pointers with compression, and iOS’s Objective‑C pointer tags—explaining each scheme’s memory layout, performance trade‑offs, and design rationale.
This article explains V8's internal object representation, pointer tagging, the three property storage modes (inobject, fast, slow), how constructors and literals allocate space, the rules that trigger mode switches, and the slack‑tracking technique that refines memory usage.
This article explores V8’s architecture—from its host integration and bytecode compilation to hidden classes, inline caches, and garbage collection—providing interview‑ready insights, performance optimization techniques, and practical code examples that illuminate how JavaScript executes efficiently in browsers and Node.js.
This article explains the architecture of browser engines, the distinction between stack and heap memory, V8's generational garbage collection strategies—including the Scavenge algorithm for the young generation and mark‑sweep/mark‑compact for the old generation—along with optimizations such as write barriers, incremental marking, and parallel/concurrent collection.
The Youzan retail team built a cross‑platform order discount calculation framework, evolving from JavaScript to a TypeScript‑based design that unifies online and offline scenarios, employs domain models, activity‑mutual‑exclusion graphs, and performance optimizations, delivering up to four‑fold productivity gains and consistent, high‑accuracy discount processing across all client platforms.
The article introduces V8’s architecture, tracing its shift from the memory‑heavy Full‑Codegen and Crankshaft compilers to the modern Ignition bytecode interpreter and TurboFan optimizing compiler, and explains how lexical analysis, AST parsing, bytecode generation, and runtime feedback together boost startup speed and reduce memory usage.
V8 Lite, introduced by the V8 team in late 2018, implements a series of memory‑saving techniques—such as lazy feedback allocation, delayed source positions, and bytecode flushing—that together can reduce heap usage by roughly 22% in memory‑constrained scenarios while maintaining acceptable execution performance.
This article introduces Facebook's Hermes JavaScript engine, details its integration into React Native Android projects, explains its bytecode precompilation and JIT‑free design, presents performance benchmarks versus JavaScriptCore and V8, and discusses current limitations and future considerations.
The article outlines a cross‑platform receipt‑printing solution for retail apps that uses JavaScript‑based parsing, server‑editable templates, and native JS engines on iOS and Android to dynamically manage diverse printer models, reduce maintenance, and enable fast template updates across iOS, Android, and web.
This article chronicles the ten‑year history of Google’s V8 JavaScript engine—from its secretive beginnings and open‑source launch to major performance improvements, benchmark trends, security challenges, and its expanding role in browsers, Node.js, and WebAssembly—highlighting key milestones and future directions.
