# Reshaping the Extensions proposal

**URL:** <https://es.discourse.group/t/reshaping-the-extensions-proposal/2439>\
**Category:** 🦋 Proposals\
**Created:** [September 30, 2025, 3:24pm UTC](https://es.discourse.group/t/reshaping-the-extensions-proposal/2439 "2025-09-30T15:24:30Z")\
**Posts on this page:** 1\
**Showing post:** 24

<div class="post-metadata">

**Author:** ![ewinslow](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/ewinslow/32/2604_2.png) [@ewinslow](https://es.discourse.group/u/ewinslow)\
**Post date:** [January 24, 2026, 11:39am UTC](https://es.discourse.group/t/reshaping-the-extensions-proposal/2439/24 "2026-01-24T11:39:39Z")

</div>

> [@jschoi](#):
>
> members of the Committee perceive such convenience syntaxes as less beneficial for a still-high cost, compared to syntaxes that do bring new behaviors

Do you think this situation could be helped if the rationale for a proposal were more anchored to the end-user benefits? From what I can tell, most of the motivation for the pipeline and call-this proposals is framed as “make clunky code more readable” but it’s not immediately obvious why that benefits end-users.

Here is my basic line of thinking:

1. Dead code is a big problem slowing down the web (Gemini claims 30-70% of JS on the web is dead code).
2. prototype-based functions are particularly hard to tree-shake, resulting in more dead code.
3. prototype-based functions are also _very popular_ because of how convenient they are for devs to define (class syntax) and invoke (method call, method-chaining, etc).
4. To get people to write more tree-shakable code, we need to offer a tree-shakable option that is as convenient as method-chaining. Then, developers will be willing to use that instead.
5. More tree-shaking == faster, lighter web == happier end users.

I’m sure there are holes and many details or other rationale I could fill out, but the main point is that “developer convenience” in this context is really just a means to the end of a faster user-experience for everyone.

---

_[View the full topic](https://es.discourse.group/t/reshaping-the-extensions-proposal/2439)._