just VS dom-examples

just-diff

You can roll your own or use a utility library. A simple zero-dependency library would be something like just-group-by [1]. Although I now prefer remeda [2] as it seems to have the best typescript support, especially the strict variants such as `grouBy.strict`.

[1] https://github.com/angus-c/just#just-group-by

Tree-shaking doesn't help much when the tree-shaken implementation is so bloated.

Here's the one you referenced, lodash.chunk: https://unpkg.com/lodash.chunk – 140 lines after removing comments and whitespace.

That's pretty small compared to a lot of the lodash utilities. Try spot-checking a few on unpkg.

I prefer angus's `just` utilities: https://github.com/angus-c/just

I absolutely love this. When I need some Lodash alternative I'll usually reference angus-c/just but I am definitely bookmarking this for next time.

The just set of utility functions are really nice to use. https://github.com/angus-c/just

Just doesn't have everything but it's pretty good

One of my favourite "libraries" are the "just" packages, where each part of the library is it's own simple package with zero dependencies (https://github.com/angus-c/just) so you essentially just npm install the specific thing you want - which is generally a single function.

If the code should, as you say, be 5 lines, why take on a dependency at all? By doing so, you end up with a catch-all solution that does almost nothing other than JSON.stringify your args, which is extremely poorly optimized to handle many situations, e.g. one of your args is a primitive and the other is a large config object.

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.