dom-examples VS libuv

If you have a moment, take a look through the Web API docs from MDN. I guarantee you will find something new that solves a problem you needed to build your own solution for in the past.

This is a problem! Ideally, your backend application should be platform-independent by following the standardized Web API. This way, you could run it across most JavaScript platforms.

Fonte: MDN web docs

References MDN Chrome Docs

> if writing a browser today is in fact easier than both writing AND maintaining a browser a decade back.

Probably not. Yeah we have web standards and some idea of how to architect it, but the total set of APIs and HTML/CSS/JS features a browser supports is probably changing faster than the Ladybird team can actively implement it. The API surface is just impossibly large compared to 10 or 15 years ago. Look at all of these: https://developer.mozilla.org/en-US/docs/Web/API

I added polyfills for the Web APIs used in the React code.

In addition to pure JavaScript, there are hundreds of Web APIs documented at MDN. These APIs cover everything from the DOM to Web Workers with great detail.

I'm reading MDN Web Docs on Web APIs. There are two basic sections, specifications and interfaces.

The biggest difference is usually found in what non-ECMAscript standard JS web apis or features are implemented in different browsers. Here's a list of typical web APIs, and for many of them there is a compatibility table at the bottom detailing which browser do or do not support it. https://developer.mozilla.org/en-US/docs/Web/API

I wound up on a different team with pre-existing Python code so temporarily shelved my use of Go for a bit, and we used Sanic (an async Python framework built on top of the excellent uvloop & libuv that also powers Node.js) to build some APIs for live channel management & operations. We hand-wrote our OpenAPI and used it to generate documentation and a CLI, which was an improvement over what was there (or not) before. Other teams used the OpenAPI document to generate SDKs to interact with our service.

In the source code of the Node.js opensource project, lib folder contains JavaScript code, mostly wrappers over C++ and function definitions. On the contrary, src folder contains C++ implementations of the functions, which pulls dependencies from the V8 project, the libuv project, the zlib project, the llhttp project, and many more - which are all placed at the deps folder.

Libuv, the C library that gives Node.js its asynchronous, non-blocking I/O capability is responsible for managing the thread pool. Node.js gives you the capability of using additional threads for computationally expensive and long-lasting operations to avoid blocking the event loop.

Node.js is written in C, C++, and JavaScript. The core components of Node.js - the V8 engine and the libuv library - are written in C++ and C, respectively, since these languages provide low-level access to system resources, making them well-suited for building high-performance and efficient applications. JavaScript is mainly used to write the application logic.

x8 apparently https://github.com/libuv/libuv/pull/3952

Notably upgrades to libuv 1.45 which has io_uring support. Faster file system access! Awhh yeah, it's on.

Remarkable what a mild & unintrusive PR adding io_uring was. https://github.com/libuv/libuv/pull/3952

Well, the single-threaded nature ultimately leads to its biggest downfall. Node.js utilizes a synchronous event loop engineered using Libuv that takes in code from the call stack and executes it.