Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is the current status of this proposal? #79

Open
Becavalier opened this issue Sep 24, 2020 · 13 comments
Open

What is the current status of this proposal? #79

Becavalier opened this issue Sep 24, 2020 · 13 comments

Comments

@Becavalier
Copy link

Becavalier commented Sep 24, 2020

As titled.

Is there any progress on this proposal?

@xtuc
Copy link
Member

xtuc commented Sep 28, 2020

I can't speak for the proposal's champions but Cloudflare experimented with distributing binary AST instead of JavaScript for compatible eyeballs. We are planning to continue to work on the proposal.

@Zizzamia
Copy link

Zizzamia commented Oct 3, 2020

Where can I read more about the Cloudflare experimentation?

@xtuc
Copy link
Member

xtuc commented Oct 3, 2020

We wrote a blog post https://blog.cloudflare.com/binary-ast/.

@Zizzamia
Copy link

Zizzamia commented Oct 4, 2020

This is super interesting! Could binary AST being stored by the Service Worker in the Cache Storage as we do with JS files?
I'm def going to experiment a bit with this proposal, now that I see Cloudflare is investing on it. 😁

@Becavalier
Copy link
Author

I saw @syg is one of the champions. May I know is there anything blocking the advancing of this proposal?

@lygstate

This comment has been minimized.

@akhiljay
Copy link

akhiljay commented Jul 5, 2021

Is there interest from Chrome to implement this?

@lihugang
Copy link

lihugang commented Jan 9, 2023

So, what is the current status of this proposal? This looks abandoned.
uh.... I am not good in English, please forgive me if I offended.

@vdjeric
Copy link
Collaborator

vdjeric commented Jan 9, 2023

No one is working on it for the last several years

@RReverser
Copy link
Contributor

@vdjeric Probably would be worth to archive the repo (for whoever has the rights to do so) to avoid confusion.

@ljharb
Copy link
Member

ljharb commented Jan 9, 2023

Proposals often have no work done on them for years, and then champions pick them back up, so inactivity can't be used as a sign of withdrawal.

If the champions (which include @vdjeric and @RReverser, as well as @syg and @Yoric) wish to withdraw the proposal, or step down as champions of it, they'd need to decide that collectively and individually, respectively. Once withdrawn, it would certainly be archived.

@RReverser
Copy link
Contributor

Ah, fair enough.

@kootstra-rene
Copy link

Though it is an interesting proposal I can't help but feel this is a solution to bad practises. Keeping the bad practices alive. Having 1+MB JavaScript files are the problem and browser vendors should maybe lower the ranking of those websites or show a banner that the website may perform poorly. That will be a good incentive to fix the large JavaScript files.

For sites with < 200 Kb of JavaScript the benefit of this proposal is limited.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants