1 views collected around this technical thread.
This article introduces Alibaba’s open‑source LowCodeEngine, outlines its browser compatibility, core features, protocol standards, provides installation and initialization code, explains CDN integration options, and showcases the editor’s UI panels and real‑world use cases.
This article provides a comprehensive technical overview of JavaScript language standards, the architecture and optimization techniques of major JavaScript engines such as V8 and TurboFan, introduces the lightweight QuickJS engine with its features, file layout and memory management, and demonstrates how to embed QuickJS with libuv for asynchronous I/O using detailed C code examples.
This article explores the design and implementation of a portable, high‑performance JavaScript engine, covering ECMAScript basics, V8 TurboFan optimization, the QuickJS engine architecture, memory management, building and extending QuickJS, and integrating it with libuv for asynchronous I/O.
Unity introduced a new installation‑based pricing model that charges developers $0.20 per install after $200,000 revenue or 200,000 downloads, prompting widespread developer backlash, concerns over tracking and impact on mobile titles, and prompting some to consider switching to alternatives like Godot.
Page Logic Orchestration with LogicFlow solves low‑code expansion challenges by replacing rigid zero‑code property panels with a visual workflow editor that lets operators compose, debug, and execute flexible page logic using custom nodes, parallel execution, and repeatable flows, reducing development cost and complexity.
This article introduces the core components of WebAssembly engines, outlines a generic engine architecture, and compares five popular engines—wasmtime, wasm3, WasmEdge, wasm‑micro‑runtime, and V8—detailing their design, performance, standards support, and typical use cases.
This article introduces the core components of WebAssembly engines, presents a conceptual architecture model, and then examines several popular open‑source runtimes—including wasmtime, wasm3, WasmEdge, wasm‑micro‑runtime, and V8—detailing their structures, performance characteristics, standards support, and typical use‑cases.
LowCodeEngine, an open‑source low‑code engine from Alibaba’s DingTalk team, follows Alibaba’s backend‑frontend standards, supports modern browsers, offers a minimal core with rich ecosystem elements, detailed protocol specifications, multiple CDN integration options, extensive UI panels, schema editing, and real‑world case studies, all illustrated with code snippets and screenshots.
LowCodeEngine is an open‑source low‑code engine from Alibaba that follows enterprise front‑end standards, offering a minimal core, rich ecosystem, TypeScript typings, configurable CDN options, detailed UI panels, and extensible protocols for building front‑end applications.
LowCodeEngine is an open‑source low‑code engine released by Alibaba's DingTalk team that follows internal construction protocols, supports modern browsers, offers a minimal core with a rich ecosystem, provides TypeScript typings, and includes extensive UI panels, schema editing, and multiple CDN integration options for developers.
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 analyzes the business challenges of marketing automation, introduces workflow concepts and models, compares workflow engines with state machines, presents popular open‑source engines, and details the design, core modules, interfaces, and practical considerations of a self‑built lightweight workflow engine.
This article explains the fundamental principles behind JavaScript execution, covering the distinction between interpreted and compiled languages, the architecture of JavaScript engines (including V8, SpiderMonkey, and JavaScriptCore), runtime environments, the single‑threaded event loop, call‑stack processing, lexical analysis, parsing, bytecode, JIT compilation, and the role of Web Workers in off‑loading CPU‑intensive tasks.
This article presents a comprehensive, categorized collection of open‑source workflow engines and BPM tools—including complete products, SaaS solutions, and embeddable libraries—along with brief descriptions and recommendations for different orchestration scenarios.
This article explains how the V8 engine parses JavaScript source code into an AST, establishes scope rules, creates isolates, handle scopes and contexts, and manages the execution context stack during interpretation and execution, illustrated with detailed code examples and diagrams.
This article explains how PyTorch's BP Engine dynamically builds the computation graph for back‑propagation, detailing its C++ class structure, thread management, task queues, and key functions such as start_threads, compute_dependencies, execute, and evaluate_function, with illustrative code examples.
The article narrates the progressive design of a customizable workflow engine, starting from a simple linked‑list approver chain and evolving through countersign, parallel, conditional, delegation, timeout, progress‑percentage, and script‑hook features, illustrating each stage with node classifications, state definitions, and tree‑based structures.
This article explains the complete lifecycle of JavaScript execution in the V8 engine, covering language fundamentals, AST generation, bytecode compilation, interpretation, just‑in‑time optimization, hidden classes, inline caches, and other performance strategies used by both browsers and Node.js.
This article explains how the V8 engine parses JavaScript into an AST, generates bytecode, employs lazy compilation, caches machine code, and uses the TurboFan optimizing compiler with JIT techniques to balance speed and memory consumption during script execution.
The article walks through the step‑by‑step evolution of a custom workflow engine, starting with a basic linked‑list approver chain and progressively adding support for parallel, multi‑sign, conditional, timed, proxy, cancellation, pre‑/post‑conditions, progress metrics, and script hooks, illustrating a comprehensive backend design.