-
Notifications
You must be signed in to change notification settings - Fork 23
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
Comments
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. |
Where can I read more about the Cloudflare experimentation? |
We wrote a blog post https://blog.cloudflare.com/binary-ast/. |
This is super interesting! Could binary AST being stored by the Service Worker in the Cache Storage as we do with JS files? |
I saw @syg is one of the champions. May I know is there anything blocking the advancing of this proposal? |
This comment has been minimized.
This comment has been minimized.
Is there interest from Chrome to implement this? |
So, what is the current status of this proposal? This looks abandoned. |
No one is working on it for the last several years |
@vdjeric Probably would be worth to archive the repo (for whoever has the rights to do so) to avoid confusion. |
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. |
Ah, fair enough. |
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. |
As titled.
Is there any progress on this proposal?
The text was updated successfully, but these errors were encountered: