Live data from Hacker News

Viewing profile — nolanl

nolanl

HN member
Joined
Tue, Aug 13, 2013, 8:52 AM UTC
HN karma
1,091
Public activity
125 items

About nolanl

[ my public key: https://keybase.io/nolanlawson; my proof: https://keybase.io/nolanlawson/sigs/5Udxhb8X1E57tmNkoMyOonOIeiVfEpGPlwm9amgvHMQ ]

Recent public activity

  1. comment
    Comment #47970954

    Welp, I fed it the first 3 paragraphs of an unpublished blog post I wrote a few years ago, and Opus 4.7 guessed right. ChatGPT guessed wrong though. My wife also got the same resul…

  2. comment
    Comment #47318444

    The concept of "AI will review AI-authored PRs" seems completely wrong to me. Why didn't the AI write the correct code in the first place? If it takes 17 rounds of review from 5 di…

  3. comment
    Comment #47293788

    This is 100% my experience. Like, reading this thread right now, I notice the ringing in my ears. But otherwise I go months without thinking about it.

  4. comment
    Comment #47293775

    I've had tinnitus for almost a decade now. It gets better. The first six months were hell because I kept focusing on how awful it was. Eventually you stop noticing it. It just beco…

  5. comment
    Comment #46648614

    I've found Bugbot to be shockingly effective at finding bugs in my PRs. Even when it's wrong, it's usually worth adding a comment, since it's the kind of mistake a human reviewer w…

  6. comment
    Comment #45948587

    Right, but you do avoid worries like "will I have to update this dependency every week and deal with breaking changes?" or "will the author be compromised in a supply-chain attack,…

  7. comment
    Comment #45860265

    As someone who has actually worked on JavaScript frameworks, I think Marko is criminally underrated. The compile-time optimizations are extremely impressive: https://markojs.com/do…

  8. comment
    Comment #44300136

    Author here. I actually did some research on CSS selector performance: https://nolanlawson.com/2023/01/17/my-talk-on-css-runtime-pe... The TL;DW is: yes, class selectors are slight…

  9. comment
    Comment #41688158

    I use shadow DOM every day, but yes, it is often the part of WCs that baffles people – probably because they don't need it. Alternative approaches that may work for your use case: …

  10. comment
    Comment #41688117

    I cover this in another post [1], but broadly: - Not every web app is perf-sensitive to every extra kB (eCommerce is, productivity tools typically aren't) - Plenty of frameworks ha…

  11. comment
    Comment #41688054

    Author here. I cover this in another post [1], but basically the interop benefits you get on the client just aren't there (yet) on the server. My north star: > Maybe in the future,…

  12. comment
    Comment #39641942

    Thanks a lot! I was just trying to highlight the cool work that browsers do under the hood, but which wasn't very well-known. So I'm really glad that folks enjoyed the talk. :)

  13. comment
  14. comment
    Comment #38514096

    Author here! I struggled with the word "modern" – I could have said "current gen" or "post-React" or even "Solid-inspired" frankly, but I thought "modern" was succinct with the rig…

  15. comment
    Comment #38512792

    Author here. Thanks for the thoughtful reply! I did indeed mix up `useMemo` and `React.memo` – fixed it in the post. You're right, I am skipping a lot of details (hence "to grossly…

  16. comment
    Comment #34784900

    Thanks for the shout-out! I think I mention this in the talk, but note that YMMV. I designed that benchmark as a kind of "worst-case scenario" where shadow DOM / scoped styles real…

  17. comment
    Comment #31468219

    Thank you! This is exactly what I had in mind. The streaming aspect of MPA pages is a great example of something you can't really do in an SPA. (Although there are hacks: https://j…

  18. comment
    Comment #31461251

    (Author here.) I totally agree and feel that Service Workers are still underexplored in this area. If your main reason for writing an SPA is speeding up navigation (e.g. the Turbol…

  19. comment
    Comment #29870332

    It depends. For elements that are removed from the DOM, then yes, the event listener should also be automatically removed: https://jakearchibald.com/2020/events-and-gc/ However, if…

  20. comment
    Comment #29870091

    That's really interesting. I wonder if this is a Chromium-only issue? It may be worth filing a bug: https://bugs.chromium.org I'm not an expert in this space, but it seems to me th…

  21. comment
    Comment #29600417

    Great point! This is exactly why fuite does a preflight iteration before the "real" iterations. One-time setup costs shouldn't count against the "leak" – only sustained memory grow…

  22. comment
    Comment #29595914

    Author here. I added support for custom scenarios, where you can define a "setup" step that logs in or does whatever you may need to do: https://github.com/nolanlawson/fuite/#exten…

  23. comment
    Comment #29595892

    Author here. I wasn't aware of your talk, but it's super interesting! Showing info about the retain chain is a great idea, but I didn't get around to doing it in fuite. IME just co…

  24. comment
    Comment #28160105

    I wrote that article 7 years ago, and FWIW I would side more with Dale these days. It's probably a good thing we didn't just slap a half-baked API on top of SQLite and call it a we…

  25. story