Skip to main content
tdro

Another wandering soul whispering into the void. If you are looking for my blog you are in the wrong place. The profile and header pictures are brought to you by cdd20.

tdro micro.thedroneely.com view
  • Markdown Plaintext Embed Permalink
  • 28/50 words 9s read
    tdro

    Another wandering soul whispering into the void. If you are looking for my blog you are in the wrong place. The profile and header pictures are brought to you by cdd20.

    tdro micro.thedroneely.com view
  • Markdown Plaintext Embed Permalink
  • 92/50 words 31s read

    When making hugo themes, it’s probably better defaulting to absURL and relURL over baseURL for links. It avoids most breakage on links that depend on a base and more easily allows multilingual support with absLangURL.

    However realistically (for anything), interpretations of file, directory/, absoluteness, and relativity are varied. Testing artifacts for ≈ 100% internal/self linking consistency, under different conditions, and after every code change is better time spent debugging. Sub directories are exceptional cases… even now some of my links are broken except that my web server automatically fixes common mistakes (:

    #webdev
    tdro

    Another wandering soul whispering into the void. If you are looking for my blog you are in the wrong place. The profile and header pictures are brought to you by cdd20.

    tdro micro.thedroneely.com view
  • Markdown Plaintext Embed Permalink
  • 65/50 words 22s read

    The Chrome experimental recorder tool has been around for a long while. I thought it was still mostly but I got schooled and apparently, this is a more faster way to jump–start a puppeteer script/test:

    Chrome recorder developer tool
    Index: Cache · Source
    #clips #webdev
    tdro

    Another wandering soul whispering into the void. If you are looking for my blog you are in the wrong place. The profile and header pictures are brought to you by cdd20.

    tdro micro.thedroneely.com (edited) view
  • Markdown Plaintext Embed Permalink
  • 128/50 words 43s read
    Browser rendering engine feel: Webkit (Safari), Blink (Chrome) or Gecko (Firefox)?

    Which browser engine “paints” the smartest on my device? In the clip below; Surf substitutes for Safari and Chromium for Chrome. My blog is the testee since there’s guaranteed cache control and jitter.

    Webkit (Safari/Surf/+) > Blink (Chromium/Chrome/+) > Gecko (Firefox/IceCat/+)
    Index: Cache · Source

    Surf and by extension Safari (or any Webkit–based browser) wins . Webkit feels smooth (sneakily, too smooth). It’s probably partly why Safari on macOS/iOS feels so fast. Chrome (not Chromium) is almost on par or so I’ve been told. Not exactly web dev but interesting huh?

    #clips #webdev

    Authors

    Gallery

    Web Feeds (6)

    Web Ring