Two ideas for improving MDN’s browser compatibility tables:
Converting to and from Base64 in #JavaScript: > Uint8Array.of(0, 1, 2).toBase64() 'AAEC' > Uint8Array.fromBase64('AAEC') Uint8Array.of(0, 1, 2) Decent JS engine support:
“[With] Chrome 154 in October 2026, we will change the default settings of Chrome to enable ‘Always Use Secure Connections’. This means Chrome will ask for the user's permission before the first access to any public site without HTTPS.” I’m ambivalent: Browsers already use HTTPS as much as possible. They should really test if non-technical users understand what the warning says. Otherwise it may scare them away from older sites that would still be useful for them.
Kind words from @npub13dlk...l6n5 in the most recent JavaScript Weekly (*). Thanks Peter! My CSS blog post: (*) image
Using Cloudflare for static file hosting: • Cloudflare Pages is easy to use but forwards requests from /home.html to /home (which I don’t want because it changes existing URLs) • Solution: Switch to Workers where forwarding can be switched off. • New problem: / isn’t forwarded to /index.html anymore. Not sure how to fix that yet. • A % in a filename caused an error with an obscure message and prevented deployment. I may not be their target audience. I just want simple static file hosting.
Render took my sites offline, due to an increase in traffic (not humans, probably LLMs). I’d upgrade to their paid plan but I can’t set a spending limit – which find too risky. I’ll probably migrate to Cloudflare Pages.