I'd like to champion this proposal and reshape it

[hax]

I'd like to ask current champions @bterlson @zenparsing @mattpodwysocki whether I can take over this repo and reshape the proposal?

[michaelficarra]

@hax I'd recommend starting fresh, as this proposal will come with a lot of baggage.

[hax]

@michaelficarra Two reasons I prefer continue the work in this repo instead a new repo:

• We already have a lot of valuable discussions in this repo, which helps all participants to more easily check the history and understand where we are starting from. Starting fresh may cause repetition and reduce efficiency.
• Although there may be significant changes, I hope to continue some core use cases and reuse the basic syntax of the original proposal. From the developer's perspective, it may look close to the original proposal. So it could be seen as a new iteration of the proposal (like what happened on decorators proposal). Reusing this repo could decrease the potential confusion.

[MrXploder]

I really dont understand why such "wall" for this proposal to go on.... is such an amazing feature to manipulate DOM list without boilerplate and a perfect companion for "lodash"-like libraries.... The syntax itself its amazing "::"

I was using it for a long time with babel but I really like that this would be the "standard".... gosh even decorators that are stage 2 are widely implemented in babel/typescript and this proposal that seems really easy to do, is not 👎🏼 .

[hax]

The new proposal Extensions which is the reshape of the "virtual method" part of this proposal has advanced to stage 1!

[lake2]

The new proposal Extensions which is the reshape of the "virtual method" part of this proposal has advanced to stage 1!

nice!