Sida Chen

Bun is great
Until it OOMs

Bon courage !! Ton français rattrapera très rapidement celui de tes contemporains dès que tu seras là-bas 😃

This is a truly awesome post!

Screenshot of the HTML spec. Text: An end tag whose tag name is "sarcasm" Take a deep breath, then act as described in the "any other end tag" entry below.

The HTML spec keeps on giving

html.spec.whatwg.org/multipage/pa...

Canny machine-translates post content (written by user) to the browser's preferred language, but the UI labels remain in English—has to be the funniest l10n strategy

I don't remember if this is my first time (maybe Docusaurus 2 too?), but it's good to be involved in a news that stayed in HN#1 for so long!
(Interestingly, exactly 10 out of the 300+ comments ever mentioned or linked MDN.)

It will be in Firefox 135 behind a flag, and other browsers are still working on it. If all things go well it should be GA late this year.

Screenshot of MDN showing the landing page of Temporal

The Temporal docs are now live on MDN! After watching it evolve for ~5 years I finally sat down and wrote docs for it—one of the biggest additions to the JS docs area ever.

Isn't that what Yarn PnP does?

Screenshot of a GitHub PR page with title "Reference for stage 3 temporal" to the mdn/content repository. It has 247 files changed and 11,492 lines added.

And it starts cooking...👀

A beautifully rendered error message from LALRPOP demonstrating a particular parse path that leads to ambiguity, with an ASCII diagram showing two possible derivations.

We don't show enough appreciation for what a piece of art parser generators are. They are the ultimate forms of software design. Here I'm taking one second to appreciate this epic error message that LALRPOP produces.

You want 4. Those who can't but know how to tickle ChatGPT the right way to get a solution. They actually deliver anything you ask for.

Out of curiosity is stage 3 a sufficient condition for implementation issues? I imagine the "research phase" should start before stage 3 and stage 3 should be for "experiment phase" and "shipping phase" already?

Would be useful to have links to implementation issues too, so we know how close we are to stage 4 (and to documentation inclusion)

I just think there should be a way to customize module resolution in any env—Node or HTML or workers. What about the Worker() constructor since the type is also specified there?

Sorry too busy to write docs outside of JS lang :( Typically Web API docs are written by people tasked by either FF or Chrome, so if Google cares enough you would see it when Chrome ships it, otherwise you would definitely see it when FF ships it!

Starting to realize that "GraphQL is great" might be a hot take

Welp, time to make another pedantic MDN PR I guess

Webpack 5 release (2020-10-10) | webpack webpack is a module bundler. Its main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable of transforming, bundling, or packaging just about any resource or asset.

TIL that webpack is not capitalized! But their blog uses "Webpack" at start of sentence though: webpack.js.org/blog/2020-10...

Casing police list:
{Type,Java}Script
ESLint
typescript-eslint (even at start of sentence)
npm (even at start of sentence)
Wasm
Git
GitHub
VS Code

So I heard the sky is bluer over here...