Yang Guo @[email protected]

Googler. Chrome tooling, including @ChromeDevTools. Previously @v8js. 郭扬.

[Sarah Drasner @sarah_edo]

💥 Game changer for Web Development announced at GoogleIO- Modern Web Guidance! It’s expert-vetted skills for web development based on best practices of latest specs and APIs.

It ensures your agent/coding harness doesn’t default to older and out of date patterns to build sites.

[Chrome DevTools @ChromeDevTools]

We’ve identified and fixed a bug that caused considerable lag for some users of Chrome DevTools when trying to inspect elements. A fix is being rolled out with Chrome 143.0.7499.109 and later. 🐢➡️🐰 We are sorry about any interruptions to your workflows.

[Michael Hablich @MHablich]

We just released version 0.5.1 for the @ChromeDevTools #MCP server , and it's a big one for compatibility: we've added *Node.js 20 support*!

We saw that many of you were running into issues with older Node.js versions.

https://t.co/gg3r0piN5L

[Chrome for Developers @ChromiumDev]

We may have mentioned DevTools at #GoogleIO ... just a few times → https://t.co/3cOnalzxGJ

[Chrome DevTools @ChromeDevTools]

✨ More Gemini is coming to DevTools! ✨ Try the new experimental AI assistance panel in Chrome Canary 131 and later to get help understanding layouts and debugging your CSS. Learn more at https://t.co/TWJ01bJKkY

[Yang Guo @[email protected] @hashseed]

@JoyeeCheung @fabiospampinato @43081j @_gsathya @marvinhagemeist @bmeurer 😂

[Yang Guo @[email protected] @hashseed]

@JoyeeCheung @fabiospampinato @43081j @_gsathya @marvinhagemeist @bmeurer I think we disable the Debugger domain when profiling.

[Yang Guo @[email protected] @hashseed]

@Jack_Franklin drinking some Scottish whiskey right now 🥃

[Ergün Erdoğmuş @ergunsh]

DevTools united at @CSSDayConf! It was wonderful to collaborate and discuss web debugging together, cheers to the future of open web 🥂 @nicolaschevobbe @razvancaliman

[Yang Guo @[email protected] @hashseed]

@rauchg I agree with the general sentiment, but in case of the English language... Wasn't it mostly gunboats and redcoats?

[Yang Guo @[email protected] @hashseed]

@cramforce @v8js Thanks for the gesture.

I no longer work on the V8 team, and I think the V8 team deserves that cake :)

[Yang Guo @[email protected] @hashseed]

@cramforce @v8js You are right. The startup snapshot has more constraints.

For snapthsotting next.js after boot Node.js should already have implemented support iirc. Might still be worth it.

[Yang Guo @[email protected] @hashseed]

@fabiospampinato @erikcorry Yup. Benchmarks.

[Yang Guo @[email protected] @hashseed]

@robpalmer2 @fabiospampinato @addyosmani @ChromeDevTools Wouldn't the allocation sampling profile do the trick?

[Yang Guo @[email protected] @hashseed]

@tunetheweb Well here you are, still alive :)

[Yang Guo @[email protected] @hashseed]

@robpalmer2 @fabiospampinato @addyosmani @ChromeDevTools Trying to allocate objects to get the right GC timing seems like a bad idea though?

[Yang Guo @[email protected] @hashseed]

@fabiospampinato @addyosmani @ChromeDevTools Yes, this could be implemented.

Do you have a use case for knowing which objects die?