jsvu VS dom-examples

For debugging elements kinds to figure out a given object’s “elements kind”, get a debug build of v8 (either by building from source in debug mode or by grabbing a precompiled binary using jsvu), and run: out/x64.debug/d8 --allow-natives-syntax Note that “COW” stands for copy-on-write, which is yet another internal optimization. :))

See jsvu.

There is more than one JavaScript engine besides V8 https://github.com/GoogleChromeLabs/jsvu. Frameworks are not necessary at all to master JavaScript as a whole.

Node.js is not the only option for JavaScript engines. There are several, including Deno, QuickJS, et al. https://github.com/GoogleChromeLabs/jsvu.

To get a better understanding of why our clever one-liner FizzBuzz solution is slower, we need to take a look at how V8 works. V8 is the Javascript engine that powers NodeJS, you can directly download a binary version of the engine either via JSVU instead of compiling locally.

Tangentially related: jsvu seems to be the easiest way to install most JS engines on most platforms. This can be useful comparing performance or compatibility across JS runtimes without firing up emulators.

https://github.com/GoogleChromeLabs/jsvu

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

Documentation of Web APIs and interfaces is located on the MDN (Mozilla Developer Network) website. The term "Web API" can refer to browser or server APIs. In this article, it refers to Browser APIs.

The second one was an afternoon of "boredom." I wanted to develop, but I was running out of ideas. So, I decided to explore something new. I navigated to the Web APIs page on MDN, and something caught my eye on the letter g: Gamepad API.