Live data from Hacker News

Viewing profile — hashseed

hashseed

HN member
Joined
Thu, Mar 19, 2015, 7:01 AM UTC
HN karma
50
Public activity
24 items

About hashseed

No profile information was provided.

Recent public activity

  1. comment
    Comment #48028893

    DevTools uses a server side model, and only after you opt in with explicit consent.

  2. comment
    Comment #45675428

    Navigate to a page, right click > inspect, open the What's New panel in DevTools.

  3. comment
    Comment #44467324

    https://developer.chrome.com/docs/devtools/ai-assistance

  4. comment
    Comment #42989514

    Hi. I'm the V8 engineer who implemented the fix and wrote the blog post. The reason the initial bug report [0] was marked as WAI but the Medium blog post got a lot more traction is…

  5. comment
    Comment #38243302

    I work on Chrome DevTools. The reason is absolutely security concerns. You don't want to leak a function that can expose a list of all objects on the JS heap.

  6. comment
    Comment #34859677

    Chrome sets navigator.webdriver to true when controlled by automation. Until now, bots could simply use headful mode to achieve the same effect that is now made available through t…

  7. comment
    Comment #30111822

    I manage the team at Google that currently owns the Puppeteer project. The previous team that developed Puppeteer indeed moved to Microsoft and have since started Playwright. While…

  8. comment
    Comment #26147382

    There is a lot of content on V8's dev blog, with different depth, all pretty well written: https://v8.dev/blog

  9. comment
    Comment #20414415

    Impressive numbers. Did you try to use startup snapshot in V8 to improve TTI? https://v8.dev/blog/custom-startup-snapshots

  10. comment
    Comment #19380547

    V8 already employs W^X, i.e. memory pages allocated for V8's heap are either writable or executable, but not both at the same time.

  11. comment
    Comment #16915936

    You were already able to do this by loading any other kind of cached resource.

  12. comment
    Comment #16578029

    In what case should this be preferred over plain old Service Workers running on the user's browser? Latter is even lower latency and for free.

  13. comment
    Comment #16577926

    There are some features in V8 to make loading a script even faster. I'd be glad to connect over these features on twitter (same username). I implemented them.

  14. comment
    Comment #15052579

    Chrome already caches compile result for previously visited pages to bypass the initial parsing/compiling.

  15. comment
    Comment #15052549

    Do you have any details on what could be improved wrt V8's snapshotting? We have recently extended the feature set a lot in order to be able to snapshot full Blink contexts, and th…

  16. comment
    Comment #14984159

    iirc JSC folks are blocking explicit tailcalls on TC39

  17. comment
    Comment #13699974

    Often enough, implementing the optimal solution is not really more time-consuming than the brute force solution. Often it's not about micro-optimizations, but a difference between …

  18. comment
    Comment #13699898

    But imagine Einstein having to look up how to derive x^2. I'd say that's a pretty close equivalent to knowing tree traversal in CS. It should just come naturally.

  19. comment
    Comment #11600269

    Yup. To some, performance is just an implementation detail, and they keep adding hooks like @@hasInstance.

  20. comment
    Comment #11598893

    Unicode properties are behind an experimental flag: --harmony-regexp-property

  21. comment
    Comment #11220047

    To clarify, this is not a real job title. Chrome and V8 blog posts are written by engineers who worked on the feature being blogged about, and can choose a funky title to go with t…

  22. comment
    Comment #11220019

    Implementing lookbehind by reading backwards is not more computationally expensive than reading forward. It adds some complexity to the regexp engine, yes, but that's manageable. T…

  23. comment
    Comment #9230901

    Not sure. If it spins up a new V8 instance every time, then no. But I don't think that happens. It probably keeps a V8 instance around, so in-memory code caching should already wor…

  24. comment
    Comment #9230572

    V8-based projects can benefit from this as well: http://www.hashseed.net/2015/03/improving-v8s-performance-us...