ficusjs-renderers VS dom-examples

I'm particularly fond of the new native JS Web Components which require no build process and are extremely fast and purely client-side. When developed well it can also reduce the bundle size because it can use dynamic imports. I played around with making a SPA out of it and only got frustrated with its lack of React-like JSX. This could be overcome with tagged literals.

This example uses the @ficusjs/renderers package which provides a browser-ready ES module using the htm library.

The hello world example creates a new custom element using the createComponent function and registers it to the hello-world tag. It uses the lit-html renderer (multiple renderers are available) for creating HTML from tagged template literals.

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

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.