Top all-time · #12560
Aaron Klotz
Personal blog · dblohm7.ca/blogprogrammingsystems
Aaron Klotz's personal blog at dblohm7.ca covers programming and systems. Since 2014, 6 different Hacker News readers have linked it 19 times, most often “"Mozilla cannot fix 100% of the bugs that we do not know about."”. The last post was in 2022, but the archive is still widely read.
Too few sampled comments (3) to say how often HN recommends it.?
Why HN links it
HN commenters link this blog for a 2015 post on interesting Win32 APIs and for a Mozilla engineer's explanation of Mozilla's direction. Comments also cite it on Firefox memory issues, without judging the writing.
Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Recently I’ve been doing some work with DnsQueryEx, but unfortunately this has been less than pleasant. Not only are there errors in its …
Most-linked posts?
- "Mozilla cannot fix 100% of the bugs that we do not know about."2 people · 3 mentions · first linked 2014-08-14
- /blog/2017/11/16/legacy-firefox-extensions-and-userspace/2 people · 2 mentions · first linked 2020-08-15
What Hacker News says?
Legacy extensions were not an API: http://dblohm7.ca/blog/2015/08/30/on-webextensions/ Nor were they userspace: http://dblohm7.ca/blog/2017/11/16/legacy-firefox-extensions-...
Comment linking /blog/2017/11/16/legacy-firefox-extensions-and-userspace/
on “Firefox 57.0 Released”Submitted Bugs from Hell: Injected Third-Party Code and Detours Equals a Bad Time as a story · 36 points
HN discussionIf Firefox is using an unexpected amount of RAM, report a bug by following the steps below: 1. Open about:memory?verbose in a new tab. 2. Click Measure and save... 3. Attach the memory report to a new bug: https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&comp... 4. Paste your about:support info (Click "Copy text to clipboard") to your bug. > If you are experiencing a bug, the best way to ensure that something…
Comment linking /blog/2014/08/14/diffusion-of-responsibility
on “Give Firefox a chance”Submitted "Mozilla cannot fix 100% of the bugs that we do not know about." as a story · 4 points
HN discussionhttps://dblohm7.ca/blog/2015/07/28/interesting-win32-apis/ notes that Windows has the required APIs, and that Firefox already supports handling memory pressure notifications on non-Windows platforms. Not sure how up-to-date this information is.
Comment linking /blog/2015/07/28/interesting-win32-apis/
on “Firefox 73”Submitted Legacy Firefox Extensions and “Userspace” as a story · 3 points
HN discussionHere are a couple of links that outline the design and contain some notes: https://wiki.mozilla.org/Electrolysis/Accessibility#Windows http://dblohm7.ca/blog/2016/04/06/new-team-new-project/ Note that the approach we are taking on Windows is different from the way that Chrome works. They cache the entire a11y tree in the parent process so that the DLLs injected by assistive technologies may quickly enumerate the a11…
Comment linking /blog/2016/04/06/new-team-new-project/
on “Update on Multi-Process Firefox”Submitted Legacy Firefox Exensions and “Userspace” as a story · 3 points
HN discussion>The XBL document mentions more systemic problem but I maintain that they could have been fixed iteratively ... >Significant problems that could have been fixed It is not like the Firefox developers do not understand the value of iterative change. That was after all the basis for Project Quantum. If this were true, they would have done it. But I'll let a Mozilla engineer explain this instead: https://dblohm7.ca/blog…
Comment linking /blog/2017/11/16/legacy-firefox-extensions-and-userspace/
on “Mozilla’s Uncertain Future”Submitted Bugs from Hell: Injected Third-Party Code and Detours Equals a Bad Time as a story · 2 points
HN discussionI did write a little bit! Here's an oldie but a goodie: https://dblohm7.ca/blog/2016/01/11/bugs-from-hell-injected-t...
Comment linking /blog/2016/01/11/bugs-from-hell-injected-third-party-code-plus-detours-equals-a-bad-time/
on “Please restore our registers when you’re done with them”Submitted Diffusion of Responsibility as a story · 1 points
HN discussionI did write a little bit! Here's an oldie but a goodie: https://dblohm7.ca/blog/2016/01/11/bugs-from-hell-injected-t...
Comment linking /blog/2016/01/11/bugs-from-hell-injected-third-party-code-plus-detours-equals-a-bad-time/
on “Please restore our registers when you’re done with them”You can help: http://dblohm7.ca/blog/2014/08/14/diffusion-of-responsibilit...
Comment linking /blog/2014/08/14/diffusion-of-responsibility/
on “Please grow your buffers exponentially”> Mozilla, for example, completely destroyed a lot of Firefox functionality, even to the point of destroying bookmarks. Relevant: https://dblohm7.ca/blog/2015/08/30/on-webextensions/ https://dblohm7.ca/blog/2017/11/16/legacy-firefox-extensions...
Comment linking /blog/2017/11/16/legacy-firefox-extensions-and-userspace/
on “Hyrum's Law”https://dblohm7.ca
Comment linking /
on “Ask HN: Could you share your personal website here?”