This is missing by default in TS. So, if you look at the first example in this article, both `printUser` calls will error in Flow: www.petermekhaeil.com/til/ts-exact...

Not by default, `$ReadOnly` is enforced via lint errors and code mods.

By deafult, Flow does have some nice guarantees that objects will always be "exact", meaning you can't add additional properties: flow.org/en/docs/type...

Flow has had immutable types built-in for a while now, all prefixed with `$ReadOnly*`: flow.org/en/docs/type...

Wrong, and I'll say so to your face. Just let me get 2 buses and an infrequent Thameslink.

Developer Voices with @krisajenkins.bsky.social
Igalia Chats

Isn't it built on top of QuickJS which does have a reference counting GC?

Wtf, you pay the Apple premium not to have to deal with these kind of cheap UX dark patterns.

I appreciate that they have a very well-written spec as well: lynxjs.org/guide/spec.h...

It's interesting that they're using the strengths of different JS engines for different parts of their runtime. QuickJS for the "main-thread runtime" with it's low latency start-up times but lack of JIT, and the inverse of V8 or Hermes for the "background runtime".

I couldn't possibly confirm either way. Ninjas operate in secret...

We sing "zed" at the end of the alphabet song just to be dicks.

Chromebook of the '00s

Boyz II Gam-men

Yeah, it's a chunky one. "300 function calls" docs.google.com/document/d/1...