Comments (18)
Hello! @zcorpan shared this project with me and suggested that I might be interested in reviewing the JavaScript chapter—he was right, I am interested!
from almanac.httparchive.org.
Hello @rwaldron glad to have you on board! I've added you as a reviewer.
from almanac.httparchive.org.
Hello! I'd be happy to join as a peer reviewer too if you need any more eyes.
from almanac.httparchive.org.
@RReverser that would be great thanks! Adding you as a reviewer and sending you an invitation to the Reviewers team.
from almanac.httparchive.org.
Thinking about possible metrics, but not sure what the limitations are, so anything that's easily dismissed, please do so...
- Appearance of new ECMAScript features, adoption growth over time
- Some areas of particular interest for me are:
Proxy
objectsWeakSet
&WeakMap
objects- Module code
async
/await
Atomics
/SharedArrayBuffer
Intl.*
APIs
- Some areas of particular interest for me are:
- Use of Generic Sensor API suite (this may be better left for future editions)
- Measuring the move away from the old APIs in favor of new (not sure if this is even possible?)
- Emergence of new occurrences of sensory APIs in the wild
from almanac.httparchive.org.
Sorry for the delay.
I had added some suggestions to the brainstorming doc previously, and have just now added another round of items (and I've updated the top post here accordingly).
@rwaldron and @moos had some great ideas! Unfortunately for lots of JS language features (especially syntactic features) it's hard to get accurate metrics just by querying the HTTP Archive. We can't just grep all JS responses for async
or await
, for example, as they're contextual keywords, and so we might potentially hit lots of false positives. To a lesser degree, this is true for non-syntax features (i.e. APIs, such as SharedArrayBuffer
) as well.
from almanac.httparchive.org.
Such counters would need to live behind a build-time flag to not incur any cost to users. (Even adding it behind a run-time flag would mean having to check for the flag all over the place.) It definitely sounds possible, it’s just not something we have in V8/Chromium right now.
from almanac.httparchive.org.
@addyosmani @housseindjirdeh @mathiasbynens can you think of anyone who might be interested in peer reviewing this chapter?
from almanac.httparchive.org.
Excellent!
from almanac.httparchive.org.
@rwaldron: been thinking the same. I'd add arrow functions, spread operator, classes, generators. I've seen the JavaScript language improve but also become a bit bloated over the years. It's be nice to see the adoption trends of these new language features.
from almanac.httparchive.org.
@addyosmani @housseindjirdeh @mathiasbynens hoping to have the metrics for this chapter finalized today. We have a scant 3 metrics so far, not counting the suggestions in #3 (comment). Aiming for 10 metrics per chapter, but I think JS is such a big/important topic that it could easily be 20 or 30 metrics (not so bad with 3 coauthors). Could you all brainstorm metrics and add them to the doc or edit this issue at your earliest convenience?
@rwaldron @RReverser if there are any other metrics you can think of that belong in this chapter, feel free to suggest them in either place.
from almanac.httparchive.org.
@addyosmani @housseindjirdeh @mathiasbynens reminder to please close this out today ❤️
from almanac.httparchive.org.
🛎 @addyosmani @housseindjirdeh @mathiasbynens this is one week overdue, please close it out as soon as possible.
from almanac.httparchive.org.
Updated the first comment with the list from brainstorming doc.
Everything LGTM. Will defer to @mathiasbynens in case there's anything else worth considering
from almanac.httparchive.org.
@mathiasbynens would it be feasible to add new use counters in chromium?
from almanac.httparchive.org.
@zcorpan It depends on the feature, since use counters come at a performance cost. We probably wouldn't want to incur a perf hit for every single arrow function, for example.
from almanac.httparchive.org.
Yes, I agree with that. Would it be possible to enable use counters on-demand for the purpose of collecting information in an HTTP Archive run, without having the use counter enabled for all users?
from almanac.httparchive.org.
FYI https://stateofjs.com/ (2018 is the latest survey)
Similar research project into the state of JS, the biggest difference being that one is a survey of developers while this is a survey of websites. Might be interesting to see if any of those results help inform some of the trends we see in HTTP Archive, if so feel free to cite that project in your chapter as needed.
from almanac.httparchive.org.
Related Issues (20)
- Write 2022 foreword
- Credit contributors of closed chapters
- "2022" hangs off the edge on the home hero
- Put class name in `code`
- (nit) Issue with the 2022 seo chapter HOT 1
- Provide 2022 social sharing image HOT 1
- Hosting HOT 4
- Broken query link in 2022 JS fig 2.7 HOT 2
- Search results page lists years out of order HOT 3
- webassembly - @luckybai HOT 1
- Jamstack chapter: Netlify’s conflict of interest should be clearer HOT 4
- Investigate 0 web mentions HOT 6
- Update Lighthouse methodology to include desktop testing HOT 1
- Multiline blockquotes have different font sizes HOT 2
- Center align featured stats HOT 2
- Clean up stale branches HOT 1
- Feedback about dynamic `import()` in JS chapter HOT 3
- Publication dates are relative to client's timezone
- Accessibility 2022: "Half of all web searches are performed by voice" doesn’t fact-check
- Issue with the 2022 sustainability chapter Figure 20.6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from almanac.httparchive.org.