12 ms·
V8 release v7.2
- zimbatm 8y agoUnrelated but .dev is a new Google TLD where all the domains have HSTS enabled by default. https://shop.gandi.net/en/domain/suggest?search=hackernews.dev https://shop.gandi.net/en/domain/suggest?search=hackernews.d...
- darkhorn 8y ago.app domains have HSTS enabled by default too. I think all domains should be HSTS enabled by default in the near future.
- PunchTornado 8y agowhy focus on facebook when measuring performance? I thought they have like 10.000 websites they measure
- sjroot 8y agoThey state specifically in the article that their chart is based on measurements taken from "several popular websites." Obviously they would want to test Facebook because a lot of people use that website. I'm sure they tested many others as well.
- dana321 8y agoWell.. Facebook runs like a dog, so any improvement is great news.
- rsaarsoo 8y agoI consider dogs to be pretty fast :)
- Skunkleton 8y agoSome dogs. Most dogs even. Not my dog. He is a good boy though.
- paulddraper 8y agoThey should start testing against Gmail then :/
- mathias 8y agoWe do indeed measure improvements against more than one website. We wouldn’t want to improve website X while regressing the rest of the internet. See https://v8.dev/blog/real-world-performance https://v8.dev/blog/real-world-performance (from 2016): > We now monitor changes against a test suite of approximately 25 > websites in order to guide V8 optimization. In addition to the > aforementioned websites and others from the Alexa Top 100, we selected > sites which were implemented using common frameworks (React, Polymer, > Angular, Ember, and more), sites from a variety of different geographic > locales, and sites or libraries whose development teams have > collaborated with us, such as Wikipedia, Reddit, Twitter, and webpack. > We believe these 25 sites are representative of the web at large and > that performance improvements to these sites will be directly reflected > in similar speedups for sites being written today by JavaScript > developers.
- glenrivard 8y agoIs the third most popular site in the world behind the two Google sites. https://en.wikipedia.org/wiki/List_of_most_popular_websites https://en.wikipedia.org/wiki/List_of_most_popular_websites List of most popular websites - Wikipedia
- Bogdanp 8y agoI suppose I could look this up, but maybe someone here knows. Is cached JS re-parsed on every page load or is the AST (or some sort of bytecode) stored as a blob on disk for faster loads from cache?
- tyingq 8y agoIt looks like you can leverage this: https://v8.dev/blog/improved-code-caching https://v8.dev/blog/improved-code-caching using this: https://www.npmjs.com/package/v8-compile-cache https://www.npmjs.com/package/v8-compile-cache Or see the options with "cache" in their name, here: https://nodejs.org/api/vm.html#vm_new_vm_script_code_options https://nodejs.org/api/vm.html#vm_new_vm_script_code_options
- Bogdanp 8y agoThanks! Looks like the first link answers my question.
- drinchev 8y ago> V8 v7.2 adds support for public class [1] fields. Support for private class [2] fields is planned for a future V8 release. For those who don't know private class fields add the weird "#" character for defining them inside the `class {}` block. class IncreasingCounter { #count = 0; get value() { console.log('Getting the current value!'); return this.#count; } increment() { this.#count++; } } This looks way worse than having what TypeScript did by introducing `public` / `private` keywords. Is there any body which votes for es-next features such as this one? I wonder how the "#" private field popped up in Chrome specs. 1 : https://developers.google.com/web/updates/2018/12/class-fields https://developers.google.com/web/updates/2018/12/class-fiel... 2 : https://developers.google.com/web/updates/2018/12/class-fields#private_class_fields https://developers.google.com/web/updates/2018/12/class-fiel...
- Waterluvian 8y agoI can't find it but I remember reading through the rationale. I don't fully recall if I understood or agreed with the reasoning but I recall there was reasoning that was more than just visual preference.
- Shorel 8y agoOf course. That abomination requires as much rationale as they can produce in the given time frame. Good design doesn't require such degree of mental gymnastics.
- Vinnl 8y agoYou can't really do good design if you have to remain backwards compatible with the entire internet.
- Waterluvian 8y agoTry explaining this to my peers who just don't appreciate why JavaScript is such a mess. Is this problem found anywhere else in the programming world at this scale?
- chrismorgan 8y agoI wonder how many people will skip using Intl.ListFormat because it insists on Oxford comma in English. I know I’ll be skipping it. CLDR really missed the semantic nuance there—not that it could readily have included it. The problem is that it’s just too blunt an instrument. (Further reading: http://cldr.unicode.org/translation/lists http://cldr.unicode.org/translation/lists, https://en.wikipedia.org/wiki/Serial_comma https://en.wikipedia.org/wiki/Serial_comma .)
- narrowtux 8y agoIt's weird that the oxford comma is included in the en-US locale, but not in the en-GB one. You can check how the locales work here: https://github.com/unicode-cldr/cldr-misc-full/tree/master/main https://github.com/unicode-cldr/cldr-misc-full/tree/master/m... Go to the locale folder and then look at the listPatterns.json file
- dhritzkiv 8y agoOut of curiosity, why is the API's insistence on the Oxford comma a downside, seeing as it works for almost all lists? Is it due to overriding editorial preference - e.g. news orgs style guides?
- chrismorgan 8y agoThe linked Wikipedia article is long, but goes into some depth on reasons and situations where it may or may not be desired. In American English it seems to be mostly a matter of preference and style guide, but in Australian English there is also semantic meaning to the comma, where it is possible in a carefully crafted sentence to convey quite a different meaning by the addition or removal of a comma; and unless there is semantic or possibly parsing value to be gained by the inclusion of a comma, it is broadly (though not universally) agreed that you shouldn’t. As noted by narrowtux, not all English locales use the Oxford comma; en-AU also doesn’t, which mollifies me. The simplest style of example I can think of is nesting conjunctions: “the difference between A and B, and C and D”. (This example isn’t great because it depends on nesting and has only two items in each list; but it’s the first that springs to my mind. There are others that don’t require nesting or only two items, though normally not quite so clear-cut.) Removing the comma or shuffling things around in any way would completely change the meaning of the sentence. This is the sort of subtle thing that some will miss when writing, but in speech it’d be very clear.
- AdmiralAsshat 8y agoWhat happens when it reaches version 8.0?
- overcast 8y agoTotal protonic reversal.
- styfle 8y agoGoogle search results will be rendered useless. "V8 release v8" At least when it's spelled out like this, they always use capital V8 for the engine and a lowercase v8 for the version. I can imagine the verbal V8/v8 confusion probably forces everyone to say "version 8"
- baby 8y agoThey're going to skip a version and go straight to 9.0 maybe
- velcrovan 8y agoHeadline is hilarious
- TomMarius 8y agoNot yet. I can't wait for V8 v8.
- forgot-my-pw 8y agoSpoiler: V8 release v8.0 · V8
- deleted 8y ago[deleted]
- truth_seeker 8y agoWow. Very impressive. They are improving at very fast rate. I wonder do we still need to invest in WebAssembly ?
- Skunkleton 8y agoWhat? How are these even related?
- truth_seeker 8y agoHow are they not related ?
- deleted 8y ago[deleted]
- jerrysievert 8y agoPersonally, i’d like to see them focus less on super-rapid releases, and more on consistency of builds and stopping major breakages across platforms. It makes it much more difficult to maintain downstream builds when the build-system breaks completely for indeterminate amounts of time.