<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Frontend on miti99</title><link>https://miti99.com/en/tags/frontend/</link><description>Recent content in Frontend on miti99</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 16 Nov 2026 17:39:19 +0700</lastBuildDate><atom:link href="https://miti99.com/en/tags/frontend/index.xml" rel="self" type="application/rss+xml"/><item><title>Newsletter #88</title><link>https://miti99.com/en/post/2026/03/13/</link><pubDate>Fri, 13 Mar 2026 00:00:00 +0700</pubDate><guid>https://miti99.com/en/post/2026/03/13/</guid><description>&lt;p&gt;&lt;em&gt;Enjoy Newsletter #88.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="a-broken-heart"&gt;&lt;a href="https://allenpike.com/2026/a-broken-heart/" rel="noopener noreferrer"&gt;A Broken Heart&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Allen Pike recounts a memorable debugging war story: the dashboard of a web app his team was building suddenly started taking ten seconds to load instead of one. He immediately suspected React and asked Claude to audit the components, but fixing redundant renders and missing memoization barely moved the needle. Digging deeper, he noticed the slowdown only happened in Safari, where the profiler showed the browser spending 94% of CPU time in Layout—over 1,600ms per pass, roughly 100 times slower than normal. Pairing binary search with a coding agent, he systematically stripped out pieces of the UI to narrow down the culprit. Within about ten minutes, the offender emerged: a single heart emoji ❤️ inside a &amp;ldquo;Send Feedback&amp;rdquo; button. Removing the emoji dropped Layout time to 2ms.&lt;/p&gt;
&lt;p&gt;With the coding agent&amp;rsquo;s help, he quickly put together a minimal reproduction for a bug report and uncovered the root cause: Google&amp;rsquo;s Noto Color Emoji webfont, which had been added so emojis would render consistently on Linux. The font uses the COLRv1 format and falls back to embedded SVGs on browsers that don&amp;rsquo;t support it, including Safari; the WebKit team confirmed the bottleneck was inside Apple&amp;rsquo;s CoreSVG. The bug was even glyph-specific: ❤️ and 🤯 took 1,600ms, while 🧺 and 🫠 took just 0.2ms. The workaround was placing &lt;code&gt;&amp;quot;Apple Color Emoji&amp;quot;&lt;/code&gt; ahead of &lt;code&gt;&amp;quot;Noto Color Emoji&amp;quot;&lt;/code&gt; in the &lt;code&gt;font-family&lt;/code&gt; stack. The punchline: Claude was the one that had suggested adding Noto Color Emoji in the first place, prompting the author to compare coding agents to a chainsaw—wildly productive, and proportionally dangerous.&lt;/p&gt;
&lt;h2 id="wrapping-code-comments"&gt;&lt;a href="https://matklad.github.io/2026/02/21/wrapping-code-comments.html" rel="noopener noreferrer"&gt;Wrapping Code Comments&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;In this short note, matklad makes two observations about line wrapping: code and comments should be wrapped at different widths, and comment width should be measured relative to where the comment starts. A hard limit around 100 columns makes sense for code because it still fits two editor panes side by side, whereas prose reads best at around 60–70 columns. The apparent contradiction disappears once you account for indentation eating into the line and code being much sparser horizontally than prose. Accordingly, the author wants code lines wrapped at 100 columns and comment text wrapped at roughly 70 columns; deeply indented comments shift to the right while keeping the same measure of text, as long as the total line length stays under 100.&lt;/p&gt;
&lt;p&gt;Simple as that sounds, popular editors don&amp;rsquo;t support it well: VS Code&amp;rsquo;s Rewrap extension lets you configure a separate width for comments, but measures it from column zero, making deeply indented comments narrower and narrower, while Emacs&amp;rsquo;s &lt;code&gt;M-q&lt;/code&gt; doesn&amp;rsquo;t wrap comments to a relative width by default either. The author also explains why soft wrapping in the editor isn&amp;rsquo;t a substitute: proper wrapping requires understanding the structure of the text—for example, a wrapped line inside a Markdown list item needs to align with the item&amp;rsquo;s indentation, which only works when the comment is parsed as Markdown.&lt;/p&gt;
&lt;h3 id="bonus"&gt;Bonus&lt;/h3&gt;&lt;p&gt;&lt;strong&gt;Images:&lt;/strong&gt;
&lt;img src="https://substackcdn.com/image/fetch/$s_!h2M_!,w_1100,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1d6d88ea-4355-4f29-96fa-9770907beebb_2360x2960.png" alt="RabbitMQ vs Kafka vs Pulsar"&gt;
&lt;img src="https://substackcdn.com/image/fetch/$s_!8P-v!,w_1100,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6039d506-e02f-4313-ab97-2c04f8c94d90_2360x2960.png" alt="REST vs GraphQL"&gt;
&lt;img src="https://substackcdn.com/image/fetch/$s_!yela!,w_1100,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5ac3310f-e380-48c2-93ff-051f7606b533_2250x2624.png" alt="Eventual Consistency in Modern Databases"&gt;
&lt;img src="https://substackcdn.com/image/fetch/$s_!vB9v!,w_1100,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbc02c74f-e91f-438a-8ad8-d5ba6831e7f0_2250x2624.png" alt="Strong Consistency In Databases"&gt;
&lt;img src="https://substackcdn.com/image/fetch/$s_!h8d0!,w_1100,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc5f67fe5-0efa-4fc6-98da-d176b60b1a92_2508x3000.jpeg" alt="PostgreSQL versus MySQL"&gt;
&lt;img src="https://substackcdn.com/image/fetch/$s_!_roW!,w_1100,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdbdb9cae-3bda-4a62-9077-3f9d1e13fede_2360x2960.jpeg" alt="Network Protocols Explained"&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Videos:&lt;/strong&gt;
&lt;a href="https://www.youtube.com/watch?v=z_NbVtbgBJw" rel="noopener noreferrer"&gt;Video: What Is Redis Really About? - ByteByteGo&lt;/a&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;em&gt;This post was rewritten by Claude Code with Opus 5.5 on 27/09/2026.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Newsletter #27</title><link>https://miti99.com/en/post/2025/05/14/</link><pubDate>Wed, 14 May 2025 00:00:00 +0700</pubDate><guid>https://miti99.com/en/post/2025/05/14/</guid><description>&lt;p&gt;&lt;em&gt;Enjoy Newsletter #27.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="heading"&gt;&lt;a href="https://blog.cloudflare.com/introducing-the-cloudflare-vite-plugin/" rel="noopener noreferrer"&gt;&amp;ldquo;Just use Vite&amp;rdquo;&amp;hellip; with the Workers runtime&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Cloudflare announced version 1.0 of the Cloudflare Vite plugin alongside official support for React Router v7. Previously, Vite&amp;rsquo;s development server always executed server-side code inside Node.js—even when the application targeted Cloudflare Workers in production—causing subtle, hard-to-catch discrepancies between local dev and production. Built on the experimental Environment API introduced in Vite 6, the new plugin runs your Worker code directly inside the native Workers runtime (&lt;code&gt;workerd&lt;/code&gt;) during local development, keeping dev behavior as close to production as possible.&lt;/p&gt;
&lt;p&gt;For single-page applications (SPAs) built with React, Vue, or Svelte, you can scaffold a new project with the &lt;code&gt;create-cloudflare&lt;/code&gt; CLI or migrate an existing app simply by adding &lt;code&gt;@cloudflare/vite-plugin&lt;/code&gt; to your Vite config and creating a &lt;code&gt;wrangler.jsonc&lt;/code&gt; file. When you edit server-side Worker code, Vite hot-reloads the Worker environment without losing client-side UI state in the browser. Running &lt;code&gt;vite build&lt;/code&gt; outputs both client and server bundles, &lt;code&gt;vite preview&lt;/code&gt; previews the production build inside the Workers runtime, and &lt;code&gt;wrangler deploy&lt;/code&gt; deploys straight to Cloudflare without an extra bundling step. With React Router v7 (the successor to Remix), a single entry file defines the Worker across both dev and build without needing a separate adapter, and the plugin supports the full Cloudflare Developer Platform including KV, D1, Durable Objects, and Workers AI.&lt;/p&gt;
&lt;h2 id="the-best-programmers-i-know"&gt;&lt;a href="https://endler.dev/2025/best-programmers/" rel="noopener noreferrer"&gt;The Best Programmers I Know&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Matthias Endler distills the common traits he has observed in the best programmers he has ever worked with—a list he wishes he had when starting out. First and foremost, they read the canonical reference documentation directly instead of guessing, copying from Stack Overflow, or asking an LLM. Second, they know their tools inside and out: why the tool was created, who maintains it, where its limits lie, and what the surrounding ecosystem looks like. Great programmers also actually read error messages carefully, break intimidating problems down into small, solvable steps, and aren&amp;rsquo;t afraid to get their hands dirty in unfamiliar codebases—which is how they become the go-to person on their team.&lt;/p&gt;
&lt;p&gt;Beyond raw technical chops, they generously help others, write clearly because clear writing reflects clear thinking, and never stop learning—some of the sharpest programmers Endler knows are in their 60s and still run circles around developers half their age. They don&amp;rsquo;t care about titles or hierarchy, build lasting reputation by shipping widely used work, stay patient with both computers and people, never blame &amp;ldquo;random&amp;rdquo; hardware glitches or compiler bugs before checking their own assumptions, aren&amp;rsquo;t afraid to say &amp;ldquo;I don&amp;rsquo;t know,&amp;rdquo; refuse to guess when requirements are ambiguous, and relentlessly favor simple code. Endler notes that this isn&amp;rsquo;t a checklist or a competition, just a reminder that there are no shortcuts around deliberate practice.&lt;/p&gt;
&lt;h2 id="rdel-87-how-do-ai-coding-tools-actually-change-developer-work"&gt;&lt;a href="https://rdel.substack.com/p/rdel-87-how-do-ai-coding-tools-actually" rel="noopener noreferrer"&gt;RDEL #87: How do AI coding tools actually change developer work?&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;In this installment of &lt;em&gt;Research-Driven Engineering Leadership&lt;/em&gt;, Lizzie Matusov summarizes a three-week randomized controlled trial conducted by Microsoft and the Institute for Work Life across 228 engineers at a global software company. Participants were split into three groups—engineers newly granted access to GitHub Copilot, a control group using no AI tools, and a comparison group of existing Copilot users—combining daily diary studies with system telemetry. Before the trial began, 86% of experienced Copilot users believed AI coding tools were useful compared to just 44% of non-users, and the single most common reason engineers hadn&amp;rsquo;t tried AI tools yet was simply being too busy.&lt;/p&gt;
&lt;p&gt;After three weeks, enjoyment and perceived usefulness rose significantly among the new users; 84% reported that Copilot positively changed how they worked, cutting down on tedious boilerplate and making coding more enjoyable. Engineers used Copilot not just for code completion, but also as a replacement for web search and as a sounding board for ideation and design. Interestingly, system telemetry showed no statistically significant difference in lines of code, pull request volume, or active coding time, and engineers&amp;rsquo; baseline level of trust in AI-generated code remained unchanged. Matusov advises engineering leaders to measure productivity holistically across satisfaction and flow using the SPACE framework, carve out dedicated time for teams to experiment, and view AI as a way to offload repetitive drudgery so engineers can focus on design and learning.&lt;/p&gt;
&lt;h2 id="overclocking-dbt-discord"&gt;&lt;a href="https://discord.com/blog/overclocking-dbt-discords-custom-solution-in-processing-petabytes-of-data" rel="noopener noreferrer"&gt;Overclocking dbt: Discord&amp;rsquo;s Custom Solution in Processing Petabytes of Data&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Discord data engineer Chris Dong shares how his team scaled &lt;code&gt;dbt&lt;/code&gt; (data build tool) to process petabytes of data across more than 100 developers collaborating on 2,500+ models. Their out-of-the-box setup quickly hit a wall: full project compilation took over 20 minutes, default incremental materialization strategies struggled at petabyte scale, and developers constantly clobbered each other&amp;rsquo;s test tables in shared environments. To isolate environments cleanly, they overrode the &lt;code&gt;generate_alias_name&lt;/code&gt; macro to automatically prefix table names with the developer&amp;rsquo;s username in local dev, the PR number or commit SHA in CI/CD, and the canonical name in production.&lt;/p&gt;
&lt;p&gt;On the performance side, they replaced standard &lt;code&gt;MAX(timestamp)&lt;/code&gt; incremental filtering with explicit &lt;code&gt;start_date&lt;/code&gt; and &lt;code&gt;end_date&lt;/code&gt; variables—noting that the expensive full-table scans came from the &lt;code&gt;MAX(timestamp)&lt;/code&gt; subquery in the old pattern rather than the &lt;code&gt;is_incremental()&lt;/code&gt; macro itself. They also patched partial-parsing hash mismatches and leveraged zero-copy BigQuery partition copies; together, these optimizations sped up runs by 5x. Historical backfills were automated via semantic versioning inside each model&amp;rsquo;s &lt;code&gt;meta&lt;/code&gt; config: bumping the major version triggers a full refresh of the table and all downstream dependents, while bumping the minor version runs a targeted date-chunked backfill. A shared macro library and Buildkite CI/CD pipeline validate query dry-run costs, dependencies, and blast radius before any change lands in production.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;em&gt;This post was rewritten by Claude Code with Opus 5.5 on 27/09/2026; reviewed and edited by Codex with GPT 6.1 Sol on 09/11/2026.&lt;/em&gt;&lt;/p&gt;</description></item></channel></rss>