<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><description>Frontend developer in love with the Web, browsers, bicycles, and podcasting. He/him, @developer.mozilla.org‬ technical writer, @web-standards.dev editor, Google Developer Expert📍Berlin&#xA;&#xA;https://pepelsbey.dev</description><link>https://bsky.app/profile/pepelsbey.dev</link><title>@pepelsbey.dev - Vadim Makeev</title><item><link>https://bsky.app/profile/pepelsbey.dev/post/3mrrtu5sbx22k</link><description>I’m cursed to see faux bold rendering when font-weight is cranked higher than the included font actually supports. I wish browser DevTools would flag it in the console. Makes me wonder if this could be caught by a linter 🤔</description><pubDate>29 Jul 2026 11:42 +0000</pubDate><guid isPermaLink="false">at://did:plc:onen6wik35u2kcychpqy2d56/app.bsky.feed.post/3mrrtu5sbx22k</guid></item><item><link>https://bsky.app/profile/pepelsbey.dev/post/3mq7zafbkc22r</link><description>Now that most of the browsers are moving to a 2-week release cycle:&#xA;&#xA;Firefox 200 in 2028&#xA;Firefox 300 in 2032&#xA;&#xA;…and if I live long enough, I might see Firefox 1000 in 2059 😬&#xA;&#xA;Firefox https://groups.google.com/a/mozilla.org/g/dev-platform/c/qlaQ1YSlOP8&#xA;&#xA;Edge https://blogs.windows.com/msedgedev/2026/06/11/faster-updates-enterprise-friendly-schedule-the-new-microsoft-edge-release-cycle/&#xA;&#xA;Chrome https://developer.chrome.com/blog/chrome-two-week-release</description><pubDate>09 Jul 2026 16:05 +0000</pubDate><guid isPermaLink="false">at://did:plc:onen6wik35u2kcychpqy2d56/app.bsky.feed.post/3mq7zafbkc22r</guid></item><item><link>https://bsky.app/profile/pepelsbey.dev/post/3mpvpmhlq2k2a</link><description>Why bother with time zones when you can just offload this problem on your user’s shoulders? Lazy Vattenfall bastards 🙄&#xA;&#xA;(pressing “Continue” reloads the page)</description><pubDate>05 Jul 2026 13:47 +0000</pubDate><guid isPermaLink="false">at://did:plc:onen6wik35u2kcychpqy2d56/app.bsky.feed.post/3mpvpmhlq2k2a</guid></item><item><link>https://bsky.app/profile/pepelsbey.dev/post/3mpnp7v7zk22d</link><description>@rachelandrew.co.uk @alexandrascript.com @bram.us @una.im @robertnyman.com @paul.kinlan.me Is there a reliable way of tracking Chrome release notes the day it ships? It’s been two days since Chrome 150 release notes are up:&#xA;&#xA;https://developer.chrome.com/release-notes/150&#xA;https://developer.chrome.com/blog/new-in-chrome-150</description><pubDate>02 Jul 2026 09:18 +0000</pubDate><guid isPermaLink="false">at://did:plc:onen6wik35u2kcychpqy2d56/app.bsky.feed.post/3mpnp7v7zk22d</guid></item><item><link>https://bsky.app/profile/pepelsbey.dev/post/3mp4pw6mrne2o</link><description>Yes, that&#39;s exactly what you need to do when a client-side exception has occurred: fill the page black and guide users to the console. Well done 👏</description><pubDate>25 Jun 2026 15:16 +0000</pubDate><guid isPermaLink="false">at://did:plc:onen6wik35u2kcychpqy2d56/app.bsky.feed.post/3mp4pw6mrne2o</guid></item></channel></rss>