Kitty 0.50, C++26 Setback, Safari’s Adaptive Dark Mode Arrive

Kitty 0.50 lands on the terminal scene

Kitty 0.50 was released this week, updating the GPU‑accelerated terminal emulator with a handful of bug fixes and new configuration knobs. The changelog, hosted at https://sw.kovidgoyal.net/kitty/changelog/, lists the version bump and mentions improvements to font rendering and scrollback handling.

The release attracted 219 up‑votes on Hacker News, with 137 comments dissecting the changes. Contributors praised the reduced latency for large outputs but noted that the new configuration syntax breaks a few legacy dotfiles. The discussion also flagged a regression in the recent Windows build, prompting the maintainer to promise a hotfix.

Kitty’s niche is performance‑first users who run heavy workloads in the shell. By moving more work to the GPU, the emulator sidesteps the bottlenecks of traditional CPU‑bound terminals. The 0.50 update does not add headline‑grabbing features, but it tightens the experience for power users who already rely on its speed.

C++26 fails committee approval

The ISO C++ committee voted to disapprove the draft for C++26 in a recent meeting, according to a blog post by Andreas Fertig dated November 2026. The post, https://andreasfertig.com/blog/2026/11/cpp26-dis-failed-how-does-cpp-survive/, outlines the reasons: insufficient consensus on the proposed modules overhaul and lingering concerns about the new concurrency primitives.

The decision sparked 348 points of discussion on Hacker News, with 246 comments debating the impact on the language’s roadmap. Some participants argued that the setback could delay library adoption, while others saw an opportunity to refine the proposals before the next standardization cycle.

Committee members did not disclose a new target date for the next vote. The blog notes that the group plans to reconvene in early 2027 to address the open issues. Until then, compiler vendors will continue shipping C++23 as the latest stable release, leaving developers to work around the missing features.

Safari adds adaptive dark mode in version 27.3

WebKit announced that Safari 27.3 now supports adaptive dark mode, a feature that automatically switches the browser’s UI and web content based on the operating system’s theme preference. The official blog entry, https://webkit.org/blog/18541/introducing-adaptive-dark-mode/, details the implementation and provides guidance for developers to opt‑in via CSS media queries.

The announcement earned 461 points on Hacker News, with 241 comments probing the practical effects for web designers. Commenters highlighted that the feature respects user‑level preferences without requiring explicit site‑level toggles, but they also warned that legacy sites might display unintended color schemes if they rely on hard‑coded backgrounds.

Adaptive dark mode aligns Safari with competing browsers that have offered similar capabilities for years. The WebKit team emphasized that the change is backward‑compatible: sites that do not declare a color‑scheme will continue to render as before. The rollout is tied to macOS Ventura’s system‑wide dark mode setting, meaning the behavior is consistent across Apple devices.

Context: tooling, standards, and UI trends intersect

The three announcements illustrate a broader tension in the developer ecosystem: rapid iteration in tooling versus the slower cadence of standards bodies. Kitty’s incremental update shows how open‑source projects can ship fixes quickly, leveraging community feedback on platforms like Hacker News. By contrast, the C++ committee’s disapproval underscores the deliberate, consensus‑driven process that governs language evolution, even when the community’s appetite for new features is high.

User‑interface expectations are also shifting. Adaptive dark mode reflects a user‑centric design philosophy that treats theme preferences as a first‑class concern. The move forces web developers to audit their CSS for color‑scheme compatibility, a task that mirrors the configuration adjustments some Kitty users must make after a version bump.

These developments converge on a common trade‑off: stability versus agility. Terminal emulators can push performance tweaks without waiting for a standards vote, but they risk breaking existing workflows. Language committees protect long‑term compatibility at the cost of delaying useful abstractions. Browser vendors sit in the middle, delivering user‑experience features that must respect both legacy content and modern expectations.

What to watch next

Kitty’s maintainers have promised a hotfix for the Windows regression within days; tracking that release will show whether the project can maintain its rapid response model. The C++ committee’s next meeting, slated for early 2027, will reveal whether the disapproved proposals gain the needed consensus or are shelved. Finally, developers should monitor how quickly major sites adopt the prefers-color-scheme media query in response to Safari’s adaptive dark mode, as early adoption could set a de‑facto standard for cross‑browser theming.