search

HTTPArchive / almanac.httparchive.org

HTTP Archive's annual "State of the Web" report made by the web community
https://almanac.httparchive.org
Apache License 2.0
611 stars 170 forks source link

JavaScript 2020 #897

Closed foxdavidj closed 3 years ago

foxdavidj commented 4 years ago

Part I Chapter 2: JavaScript

Content team

Authors Reviewers Analysts Draft Queries Results
@tkadlec @ibnesayeed @jadjoubran @ahmadawais @denar90 @rviscomi @paulcalvano Doc *.sql Sheet

Content team lead: @tkadlec

Welcome chapter contributors! You'll be using this issue throughout the chapter lifecycle to coordinate on the content planning, analysis, and writing stages.

The content team is made up of the following contributors:

New contributors: If you're interested in joining the content team for this chapter, just leave a comment below and the content team lead will loop you in.

Note: To ensure that you get notifications when tagged, you must be "watching" this repository.

Milestones

0. Form the content team

1. Plan content

2. Gather data

3. Validate results

4. Draft content

5. Publication

housseindjirdeh commented 4 years ago

I can definitely help review this chapter!

Some amazing people in community that I'd like to nominate (only if they're interested in writing for the 2020 Web Almanac of course):

ibnesayeed commented 4 years ago

I should be able to review this chapter.

ahmadawais commented 4 years ago

@housseindjirdeh thanks for the mention. I've already asked to be the author of this JavaScript chapter for 2020 Almanac. I'd love more contributors. And your content from 2019 is going to be quite helpful as it laid the foundation. We might also include a heading on JAMstack this year. 😇🙌

rviscomi commented 4 years ago

@tkadlec thank you for agreeing to be the lead author for the JavaScript chapter! As the lead, you'll be responsible for driving the content planning and writing phases in collaboration with your content team, which will consist of yourself as lead, any coauthors you choose as needed, peer reviewers, and data analysts.

The immediate next steps for this chapter are:

  1. Establish the rest of your content team. Several other people were interested or nominated (see below), so that's a great place to start. The larger the scope of the chapter, the more people you'll want to have on board.
  2. Start sketching out ideas in your draft doc.
  3. Catch up on last year's chapter and the project methodology to get a sense for what's possible.

There's a ton of info in the top comment, so check that out and feel free to ping myself or @obto with any questions!

To everyone else who has been nominated:

@ahmadawais @hemanth @jadjoubran @benschwarz @thefoxis @denar90

we'd still love to have you contribute as a peer reviewer or coauthor as needed. Let us know if you're still interested!

rviscomi commented 4 years ago

Thanks @ibnesayeed I'll put you down as a reviewer!

@ahmadawais this is a big chapter so I do expect a spot for you as coauthor, but I'll leave that up to @tkadlec's discretion as the lead.

thefoxis commented 4 years ago

thank you for the shout @housseindjirdeh! I don't think I'm the best fit for JS, plus I will be contributing to the performance chapter so I'll pass on this one 😸

ahmadawais commented 4 years ago

Thank you, @rviscomi. Looking forward to contributing as an author and reviewer @tkadlec.

jadjoubran commented 4 years ago

Thank you @rviscomi, I'm still interested in peer reviewing 👍

tkadlec commented 4 years ago

Pretty excited about this (thanks for the mention @housseindjirdeh).

Looks like we've already got a solid crew of reviewers forming. Anyone keen to help with the analyst side of things?

I'm re-reading last year's chapter and will start dropping some ideas in the Google Doc for areas I think could be interesting to add this year.

tkadlec commented 4 years ago

@thefoxis We'll probably need to coordinate with you to some extent. :) I think a section here on how JS decisions impact the core trio of accessibility, security and perf would be quite interesting and could be fleshed out quite a bit more this year. I see from a comment on your performance chapter you're also thinking along those lines (great minds and all that). So I'll just want to make sure whatever we end up on here doesn't step on your toes and compliments what you end up doing.

thefoxis commented 4 years ago

@tkadlec good point! let's keep an 👀 on both chapters and coordinate to not overlap too much. I think echoing the same sentiments is important and totally fine (such as the prevalence of js + its impact on ux/security/a11y/perf) but we should probably avoid an in-depth analysis of the same data 👍

rviscomi commented 4 years ago

@developit would you have any interest in helping to plan/review this chapter, or is there anyone else you think might be interested?

foxdavidj commented 4 years ago

Hey @tkadlec, just checking in:

  1. How is the the chapter coming along? We're tying to have the outline and metrics settled on by the end of the week so we have time to configure the Web Crawler to track everything you need.
  2. Anything you need from me to keep things moving forward?
jaisanth commented 4 years ago

I'm interested in being a reviewer, not sure if this is already filled up :-)

denar90 commented 4 years ago

@housseindjirdeh thanks 🙌 @rviscomi @obto @tkadlec if you still need some help I'd be happy to help 😃

tunetheweb commented 4 years ago

@stoyan do you have any interest with helping out in this (or any other) chapter?

tkadlec commented 4 years ago

@jaisanth & @denar90 I'm always happy for more eyes on it. :) We also have zero analysts so far, if either of you would be game for that!

@jadjoubran @ahmadawais @ibnesayeed I dropped some ideas and a skeleton outline in the doc. I'd love to get your feedback! So far, I didn't stop much to consider if anything can be measured—I figured we'd deal with that as we dig through the metrics and stuff.

In particular, I'd love to hear any angles you all think are being overlooked and, specifically, anything we can do to make the "which new api's are we using" bit a bit more fleshed out. It's probably the least interesting angle to me personally, so it's also the one that feels weakest.

@obto Feeling pretty good so far, other than our lack of analysts. :)

ibnesayeed commented 4 years ago

@tkadlec the outline looks good to me. I have added a couple of quick comments in the doc.

foxdavidj commented 4 years ago

@tkadlec Haha, yeah it looks like we'll have to share analysts between chapters like last year. If we don't find one for this chapter I'm happy to be the analyst until we do :). We'll keep you posted.

jaisanth commented 4 years ago

@tkadlec I'd be happy to review 👍 . For analysis, I'm not sure if I'm the correct person to look at the correct sources, but if there are pointers there, I can take it up :-)

foxdavidj commented 4 years ago

@jaisanth Our own @bazzadp just made a great post on how to get started as an analyst that I think you'd find to be super helpful https://github.com/HTTPArchive/almanac.httparchive.org/issues/914#issuecomment-659205330.

After you check it out, let me know if you'd like to take on the analyst role for the chapter and I'll put your name down :heart:

developit commented 4 years ago

@rviscomi I can help in some capacity, not sure to what extent yet. I'll take a look at what's been done and refamiliarize myself with last year's JS section.

jaisanth commented 4 years ago

@obto Went through the Analysts' Guide. I'll sign up as an analyst then! Thanks for the great guide @bazzadp ! 👍

foxdavidj commented 4 years ago

@jaisanth awesome, i've put you down as the analyst. And now the full team has been assembled for the chapter :heart:

rviscomi commented 4 years ago

@jaisanth could you go to https://github.com/HTTPArchive to accept your invitation to the Analysts team? Also please request edit access to the doc so you can work on metrics triaging. And if you'd like to chat with or get help from other analysts you can join us in the #web-almanac-analysts Slack channel.

@developit let us know if you'll be able to contribute!

@denar90 let us know if you're interested in contributing as a reviewer and/or analyst. Both roles are especially needed for this chapter, which has a very broad scope.

(@tkadlec sorry to take command, just want to make sure the chapter stays on schedule. Feel free to drive it as you see fit.)

denar90 commented 4 years ago

@rviscomi @tkadlec will be happy to review :)

tkadlec commented 4 years ago

@rviscomi No worries! I appreciate the help!

@denar90 Sounds awesome, thanks!

max-ostapenko commented 4 years ago

@jaisanth Check out queries for Third-party chapter here: #1092 . Some part of metrics can be reused among us I believe. Feel free to reach out.

rviscomi commented 4 years ago

@jaisanth @tkadlec for the two milestones overdue on July 27 could you check the boxes if:

Keeping the milestone checklist up to date helps us to see at a glance how all of the chapters are progressing. Thanks for helping us to stay on schedule!

jaisanth commented 4 years ago

Hey @max-ostapenko and @rviscomi , Will spend time on this in the weekend.

tkadlec commented 4 years ago

@jaisanth I've started on documenting the metrics I think we'll need (and I think are feasible) in the document. Would you be able to have a look as well and help me flesh it out?

tkadlec commented 4 years ago

@rviscomi Is the deprecated API's audit running? Wondering if there's anything interesting to clean by reporting on deprecated API's in use?

rviscomi commented 4 years ago

I've updated the chapter metadata at the top of this issue to link to the public spreadsheet that will be used for this chapter's query results. The sheet serves 3 purposes:

  1. Enable authors/reviewers to analyze the results for each metric without running the queries themselves
  2. Generate data visualizations to be embedded in the chapter
  3. Serve as a public audit trail of this chapter's data collection/analysis, linked from the chapter footer
rviscomi commented 4 years ago

@rviscomi Is the deprecated API's audit running? Wondering if there's anything interesting to clean by reporting on deprecated API's in use?

@tkadlec yes, the deprecations audit is under $.audits.deprecations in the LHR.

rviscomi commented 4 years ago

@jaisanth what's the status of the analysis for this chapter?

rviscomi commented 4 years ago

@HTTPArchive/analysts this chapter is behind and could use some help on the analysis front. If anyone has the time, please comment here. I've signed myself up as a stopgap but I'd be happy to collaborate if anyone wants to join.

foxdavidj commented 4 years ago

@tkadlec in case you missed it, we've adjusted the milestones to push the launch date back from November 9 to December 9. This gives all chapters exactly 7 weeks from now to wrap up the analysis, write a draft, get it reviewed, and submit it for publication. So the next milestone will be to complete the first draft by November 12.

However if you're still on schedule to be done by the original November 9 launch date we want you to know that this change doesn't mean your hard work was wasted, and that you'll get the privilege of being part of our "Early Access" launch.

Please see the link above for more info and reach out to @rviscomi or me if you have any questions or concerns about the timeline. We hope this change gives you a bit more breathing room to finish the chapter comfortably and we're excited to see it go live!

rviscomi commented 3 years ago

@tkadlec we've completed the analysis in https://github.com/HTTPArchive/almanac.httparchive.org/pull/1352 and the results are ready for your review in this sheet. I've checked off the analysis milestone from the top of the issue. Let @paulcalvano and me know if you have any questions by @'ing us in the sheet.

tkadlec commented 3 years ago

@rviscomi @paulcalvano Thanks so much you two!!

Super excited to dig in. 👍

tkadlec commented 3 years ago

Starting to write and tease content. This is a really interesting point from Alex: https://twitter.com/slightlylate/status/1329801884949876736

Are we able to query framework usage by site popularity? I like Ilya's Head/Torso/Tail thing from this talk at performance.now() (see https://www.youtube.com/watch?v=vtIfVPtN6io&t=8m39s).

So I'm thinking, framework usage for Top 100, Top 10000 in addition to what we already have? What do you think @rviscomi and @paulcalvano?

tkadlec commented 3 years ago

Also, is there any value at all in showing how much more JS bytes we're using today versus a longer time span than just last year? Like this?

Median JS Bytes by year (Desktop)

I think it's interesting because it shows that we're not talking about a one-year trend here—we add more constantly. But at the same time, I know there have been plenty of changes in HTTP Archive that may make this kind of comparison unreliable.

rviscomi commented 3 years ago

Are we able to query framework usage by site popularity?

Not currently. Other chapters have also been interested in a popularity dimension but we don't yet have a good ranking dataset that has good coverage of the HTTP Archive dataset, so I've been advising them not to rely on site popularity at all.

Also, is there any value at all in showing how much more JS bytes we're using today versus a longer time span than just last year? Like this?

If you have a story to tell about that data, I'd be supportive of using it. You're right that there have been a few changes to the dataset, but I think the median helps to smooth that out. The growth is undeniable. It would require additional queries. Would you be interested in running them and filing a PR to merge them with the sql/2020/02_JavaScript queries? The results would also need to be saved to the public spreadsheet to be visualized and embedded in the chapter. Let me know how much of that you'd be comfortable doing. @paulcalvano and I can help out as needed.