Twitter | Search | |
V8
Google’s high-performance open source JavaScript engine. Our mission: enable developers to build a faster future web.
276
Tweets
48
Following
26,655
Followers
Tweets
V8 retweeted
Mathias Bynens Jan 3
Replying to @v8js @hooraybuffer
Orinoco = garbage collection without the rubbish™ 🚀 parallel 🏎 concurrent 🚤 incremental Check out ’s explanation of what that means:
Reply Retweet Like
V8 retweeted
V8 Jan 3
Orinoco (V8’s garbage collector) evolved from a sequential stop-the-world implementation into a mostly parallel and concurrent collector with incremental fallback. talks trash:
Reply Retweet Like
V8 Jan 3
Orinoco (V8’s garbage collector) evolved from a sequential stop-the-world implementation into a mostly parallel and concurrent collector with incremental fallback. talks trash:
Reply Retweet Like
V8 Dec 20
Replying to @abhishekkrpand1
No.
Reply Retweet Like
V8 retweeted
Mathias Bynens Dec 18
New JavaScript language features in V8 v7.2: 🌈 public class fields 📖 Intl.ListFormat ✅ well-formed JSON.stringify 📦 module namespace exports
Reply Retweet Like
V8 retweeted
Mathias Bynens Dec 18
V8 v7.2 performance boosts: 🚀 JavaScript parsing 🚤 async/await ⚡ [...spreadElements] 🏎 WebAssembly
Reply Retweet Like
V8 Dec 18
🔥 What’s new in V8 v7.2? High-speed JavaScript parsing, faster async-await, reduced memory consumption on ia32, public class fields, and much more!
Reply Retweet Like
V8 retweeted
Mathias Bynens Dec 18
🔥 New in v7.2 and Chrome 72: Intl.ListFormat 🔥 Efficiently format lists with “and” or “or” using the correct punctuation in any language!
Reply Retweet Like
V8 retweeted
Mathias Bynens Dec 14
📝 Public class fields are shipping in v7.2 and Chrome 72! ⏰ Private class fields are coming soon.
Reply Retweet Like
V8 retweeted
Chrome Developers Dec 13
🔥 Class fields are coming to JavaScript! Public class fields ship in v7.2 and Chrome 72, and work is underway to support private fields as well. explains:
Reply Retweet Like
V8 retweeted
Mathias Bynens Dec 6
🚀 v7.2 speeds up Array.from(iterable) as well as [...array], [...string], [...set], [...map.keys()], and [...map.values()] (when the spread elements are at the start of the array literal).
Reply Retweet Like
V8 Dec 5
🔥 V8 v7.2 / Chrome 72 greatly improves the performance of spread elements of the form [...x] or [...x, y, z]. Here’s how we did it:
Reply Retweet Like
V8 Dec 5
Replying to @akerfoot
Reply Retweet Like
V8 retweeted
Michael Hablich Dec 4
Simply wondering, what would be your personal, primary use case for ?
Reply Retweet Like
V8 Nov 30
Replying to @kagurazakashira
Try the v8-dev mailing list:
Reply Retweet Like
V8 retweeted
Mathias Bynens Nov 27
Need BigInt functionality today? Use JSBI! 🔙 backwards-compatible: works in today’s browsers 🤯 future-proof: once BigInts are supported everywhere, you can drop the library + use our transpiler to upgrade your code from JSBI → BigInt
Reply Retweet Like
V8 Nov 19
Replying to @targos89 @ofrobots
Reply Retweet Like
V8 Nov 12
🚀 Faster and easier-to-debug async functions and promises are coming to V8 v7.2 & Chrome 72!   and shed some light on the recent improvements:
Reply Retweet Like
V8 Nov 11
Replying to @TerrenceJLim1 @mathias
Does the output with --print-all-code contain what you’re after? See for the individual flags it enables. ^
Reply Retweet Like
V8 Nov 11
Replying to @TerrenceJLim1 @mathias
The flag you’re looking for is --print-bytecode. ^
Reply Retweet Like