Chen Sida 🦋

I care about languages!

[Chen Sida 🦋 @SidaChen63]

Greetings from New Haven! ☀️

[Chen Sida 🦋 @SidaChen63]

@igadii_X @MichaelThiessen No one ever deep copies elements when transforming collections. That's simply an unreasonable thing to expect.

[Chen Sida 🦋 @SidaChen63]

@KrulestwoHK @bunjavascript It gets filtered out so in the client side there's never a header called Set-Cookie inside the Headers object, but that doesn't change the fact that the method exists and does exactly advertised, which is to show a list of Set-Cookie values (of which there's none)

[Chen Sida 🦋 @SidaChen63]

@7heMech @KrulestwoHK @bunjavascript If you read https://t.co/Oc7r6LLNvj, you see that it isn't for browsers because Set-Cookie is blocked in browsers.

[Chen Sida 🦋 @SidaChen63]

@sebastienlorber @michael_timbs People keep forcing very un-JavaScript patterns onto JavaScript and they are really vocal about: "All my functions return Result<T, E>" "All my functions are wrapped in a class" "All my functions are curried"

[Chen Sida 🦋 @SidaChen63]

@codeperium @sebastienlorber Sir, teaching you how to code *is* the point of a linter

[Chen Sida 🦋 @SidaChen63]

@sebastienlorber Was quite exciting when tsc supported it https://t.co/lLFjUwo5Rb

[Chen Sida 🦋 @SidaChen63]

Long-standing parser error, only fixed in TS 4.8: https://t.co/zyM289z2c1

Should have been fixed since forever ago, but...
Can't wait to use this in production!

[Chen Sida 🦋 @SidaChen63]

@sebastienlorber JS can be "broken" too, as long as breakage is low. Unfortunately it usually isn't the case for any non-esoteric use case. They've investigated this change long enough, so it's probably proven safe.
Also broken JS makes the site unusable while broken CSS just makes it uglier.

[Chen Sida 🦋 @SidaChen63]

I might have decided to not post here but this is big enough to let y'all know: The Temporal docs are now live on @MozDevNet!

Find me on 🦋 known by my website btw

[Chen Sida 🦋 @SidaChen63]

@sebastienlorber Isn't it just a TS declaration describing the interface?

[Chen Sida 🦋 @SidaChen63]

@souporserious @WebSavi Wondering what's confusing about MDN?
What we have is:
> Async methods […] are forbidden from being called constructor.
Which seems clear that it's a syntax requirement. Happy to add this example to MDN with the caveat that it doesn't work with subclasses

[Chen Sida 🦋 @SidaChen63]

@sebastienlorber @phry @oriSomething IIRC Babel does, not sure too what extent

[Chen Sida 🦋 @SidaChen63]

@phry @oriSomething @sebastienlorber Code that runs with PTC may crash on browsers without PTC due to stack overflow

[Chen Sida 🦋 @SidaChen63]

@stefanjudis I wrote the MDN docs for it. To this day I can't conceive of a case that can't be replaced by awaiting the function in an async context. The message of the doc page is basically "there are already multiple ways to do it... Well here's one more 😅

[Chen Sida 🦋 @SidaChen63]

@sebastienlorber Not in Safari though, and if you read https://t.co/v2zzF9eQXA I think they have good reasons.

[Chen Sida 🦋 @SidaChen63]

I'm not sure how many my RT will reach compared to OP. But in the linked thread I said the same thing over 5 times and it bounced off the wall. I'm thankful that the replies got my point.

[Andrea Giammarchi 🍥 @WebReflection]

I will *not* contribute to MDN anymore as it's clear my history of contributions never meant anything to them.
https://t.co/1Qga2Vv2kg

[Chen Sida 🦋 @SidaChen63]

@NicoloRibaudo That sounds good! My hope is MDN can be part of the stage 4 checklist (even if not required), and be mentioned in the presentation requesting stage 4.

[Chen Sida 🦋 @SidaChen63]

@NicoloRibaudo I searched "is:pr in:title stage 4" and found: change-array-by-copy, regexp-v-flag, symbols-as-weakmap-keys. All because SM shipped them too late. Recently I'm more actively documenting things already implemented by V8 so it gets better.

[Chen Sida 🦋 @SidaChen63]

@NicoloRibaudo Stage 3 requires test262 and spec text. That's way too early for docs. Stage 4 checkboxes already include "two implementations" and that's a necessary condition for docs inclusion, so I think these two checkboxes can be completed in a concurrent manner.

[Chen Sida 🦋 @SidaChen63]

@NicoloRibaudo One thing I don't like about the WHATWG process though is the doc issue is often filed too early—MDN only documents implemented features. So an "MDN people are aware" checkbox for stage 4 is probably the best, considering otherwise we are often only aware if FF implements it.

[Chen Sida 🦋 @SidaChen63]

@NicoloRibaudo I had actually been meaning to ask, but I don't know where to :) It shouldn't be a hard requirement, but a WHATWG-like process would be helpful.
I'm happy to write, but it'd be great if one champion can be looped into the process for technical review, etc.