← @bgSponge

If by threads with shared objects, you mean threads with shared *mutable* objects, that will be…

Summary

José Valim argues that introducing shared mutable objects to JavaScript's event loop would create unmaintainable code that even AI coding agents struggle to manage.

  1. Shared mutable objects create nightmares.

    Valim claims that allowing concurrent access to ordinary objects would make writing, maintaining, and debugging code impossible on the JavaScript event loop.

    a nightmare to write, maintain, and debug

  2. Concurrency breaks synchronous assumptions.

    If objects become concurrently accessible, two handlers on different threads could mutate the same object, requiring new synchronization logic for previously safe code.

  3. Rust's safety is difficult.

    Even with an ownership and type system designed for shared-memory concurrency, Valim observes that coding agents still struggle with Rust.

    coding agents still struggle with it

  4. Language changes may degrade quality.

    Valim suggests that altering fundamental language properties to allow shared mutability effectively makes JavaScript worse rather than better.

  5. Sound types improve engines.

    While opposing shared mutability, Valim views sound types and ahead-of-time compilation as positive additions to the language.

Read the original ↗Save to your Sponge

Summarized with Sponge. Quotes are the author’s own words.

More from @bg

All readings →