Orinoco = @v8js garbage collection without the rubbish™
parallel
concurrent
incremental
Check out @hooraybuffer’s explanation of what that means: https://v8.dev/blog/trash-talk https://twitter.com/v8js/status/1080867305532416000 …
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Orinoco = @v8js garbage collection without the rubbish™
parallel
concurrent
incremental
Check out @hooraybuffer’s explanation of what that means: https://v8.dev/blog/trash-talk https://twitter.com/v8js/status/1080867305532416000 …
Full credit to @leszekswirski for that cheesy punchline 
Any idea if anyone is still working on getting the idle garbage collection stuff into Node.js?
Last I heard @apapirovski was going to look into it 
Awesome! I kind of wish we could explicitly tell the browser we're done with a frame though. Like if I'm calling RAF, please do whatever you want with CPU until next frame, including GC.
This is exactly what the idle time GC is about in @v8js
https://v8.dev/blog/free-garbage-collection …
I don't think parallel collection could help reduce (peak) memory usage
Ah concurrent mark sweep, caught up to Java I see
. Congrats on the implementation. Now next step is (almost) zero pause time gc. Any of these in the pipeline?
The actual pause time matters much less given that all GC is now parallel, incremental, and concurrent: https://v8.dev/blog/trash-talk#orinoco …
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.