korrents
Jake Archibald

Jake Archibald

@jake-archibald · 7 positions · On ppll ↗

Web platform engineer known for work on service workers and browser APIs; writes about browsers and web performance at jakearchibald.com.

Jake Archibald did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

Filter All topics · Newest first
Topic
All 7design 1
Sort
NewestOldest

  1. Our reading

    Testing accessibility with only one screen reader, like testing with only one browser, does not give the full picture.

    Their wordsTesting in one screen reader is like testing in one browser - it doesn't always give you the full picture.

    ↗Fixing my tooltip accessibility mistakejakearchibald.com

  2. 9 months earlier

  3. Our reading

    Native JSON module imports should not be treated as a blanket replacement for fetching JSON data.

    Their wordsI'm glad native JSON importing feature exists, but it should be used with care, and not as a blanket replacement for fetch()ing JSON.

    ↗Importing vs fetching JSONjakearchibald.com

  4. 7 days earlier

  5. Our reading

    Progressive image rendering is not a substitute for keeping image file sizes small.

    Their wordsIt certainly isn't an alternative to taking care over your image sizes.

    ↗The present and potential future of progressive image renderingjakearchibald.com 1st of 2 in this piece

  7. Our reading

    Using progressive decoding to let a browser cancel an in-flight image request once it has enough resolution will not work, because of the lag between each step.

    Their wordsThe problem is there's significant lag between each of these steps, to the point where it's very likely that you'll receive megabytes of data you don't need, per image, before the response is successfully cancelled.

    ↗The present and potential future of progressive image renderingjakearchibald.com 2nd of 2 in this piece

  8. 6 weeks earlier

  9. Our reading

    Converting data to HTML on the server or at build time is better than transforming it in the browser.

    Their wordsIn almost all cases, the best thing to do is convert your data to HTML on the server, or as part of a build process.

    ↗Making XML human-readable without XSLTjakearchibald.com

  10. 2 months earlier

  11. Our reading

    Footnotes are a hack for print's limitations and do not belong on the web, which has no such limitations.

    Their wordsFootnotes are a shitty hack built on the limitations of printed media. It's dumb to build on top of those limitations when they don't exist on the web platform.

    ↗Give footnotes the bootjakearchibald.com 1st of 2 in this piece

  13. Our reading

    Letting readers skip over less-relevant content is a normal, unremarkable part of reading that does not need special design solutions.

    design

    Their wordsSkipping over less-relevant content is a normal part of reading. We don't need to over-engineer it.

    ↗Give footnotes the bootjakearchibald.com 2nd of 2 in this piece