Hacker News
1Linux gamers on Steam cross over the 3% mark
- Linux gaming on Steam has reached a milestone, crossing 3% market share in October 2025 according to Steam's survey, up 0.41% from the previous month. This represents millions of users, driven largely by Steam Deck's SteamOS and the trend toward Linux adoption as Windows 10 support ends.
Windows performance issues and Microsoft's focus
Users report Windows has deteriorated with React-based start menu lag, file explorer bugs, and memory leaks. Many criticize Microsoft's focus on dark patterns, data collection, and cloud services over performance improvements.Linux gaming compatibility and Proton success
Multiple users share successful transitions to Linux gaming, reporting 90%+ game compatibility through Steam's Proton. Main limitation is multiplayer games with kernel-level anti-cheat systems like Fortnite.Command line barriers and LLM solutions
Discussion of how AI assistants are lowering Linux adoption barriers by helping users navigate command-line tasks they previously found intimidating, making desktop Linux more accessible to non-technical users.
2How I use every Claude Code feature
- The author shares extensive experience using Claude Code as both a hobbyist and professional developer, providing practical guidance on maximizing its effectiveness. Key recommendations include treating the CLAUDE.md file as a curated constitution rather than comprehensive manual, using context management strategically with /clear and /catchup commands, keeping slash commands minimal, preferring Claude's built-in Task feature over custom subagents, and implementing hooks for deterministic rules in enterprise environments.
CLAUDE.md vs AGENTS.md file compatibility
Discussion about standardizing configuration files for AI IDEs. Anthropic recommends using CLAUDE.md with @AGENTS.md reference, but users debate whether to adopt AGENTS.md convention. Solutions include symlinks and file references, though some report Claude gets confused with symlinks.Claude Code's effectiveness and limitations
Users report mixed experiences with Claude following instructions in CLAUDE.md files, with some struggling to get basic commands followed while others have success with emphatic formatting. Performance comparison with Cursor and context management issues also discussed.Skills feature and agent architecture
Exploration of Claude's Skills feature as a better abstraction than MCP's rigid API model. Skills allow context-efficient CLI tool usage by separating "when" from "how" instructions, loading detailed guidance only when needed for specific tasks.
3Visopsys: OS maintained by a single developer since 1997
- Visopsys is an alternative operating system for PC computers that has been in development since 1997. It's a small, fast, and open source system featuring a graphical interface, pre-emptive multitasking, and virtual memory. The latest version 0.92 was released in September 2023.
College project experience
Student recalls using Visopsys for a 2006 OS class project, having to figure out modifications independently after professor prohibited contacting the author. The experience was educational and memorable, leading to choosing "visopsys" as their HN username 14 years later.Daily driver viability debate
Discussion on whether Visopsys could serve basic computing needs for kids/elderly vs. modern alternatives like iOS. Critics argue lack of mainstream browsers makes it impractical, while supporters see value in simple, focused computing environments.Single developer achievement
Admiration for Andy McLaughlin's 27-year solo development effort since 1997. Comparisons to other single-developer OSes like TempleOS, AtheOS/SyllableOS, and SerenityOS, with discussion of the complexity and dedication required for such projects.
4Claude Code can debug low-level cryptography
- A developer implemented ML-DSA, a post-quantum signature algorithm, in Go but verification was failing. After being exhausted from debugging, they used Claude AI which quickly identified a complex low-level bug where high bits were being computed twice in the verification process. The AI also successfully debugged two additional synthetic test cases, finding bugs in hardcoded constants and signature encoding length, demonstrating impressive capability for finding cryptographic implementation bugs.
LLM debugging effectiveness and limitations
Discussion centers on using LLMs to find bugs rather than write code, with mixed experiences. Users report success in algorithmic debugging but note agents can be aggressive, miss context, or provide misleading explanations that waste time.Chat vs specialized interfaces for LLMs
Users express frustration with chat-based LLM interfaces, preferring tools like Claude Code/Codex that provide more integrated development experiences. There's desire for better "copilot" modes that enhance rather than replace coding.Trust and verification when using AI tools
Debate over reliability of LLM output, especially for non-experts who may struggle to verify results. Discussion of security concerns with giving LLMs system access and the importance of domain expertise when evaluating AI suggestions.
5Show HN: Why write code if the LLM can just do the thing? (web app experiment)
- A developer tested replacing traditional code with AI by building a contact manager where every HTTP request goes directly to an LLM with database, web response, and memory tools. The AI dynamically creates schemas, generates UIs, and evolves based on feedback without traditional routes or controllers. While functionally successful, it's extremely slow (30-60 seconds per request), expensive ($0.05 per request), and lacks UI consistency. The experiment suggests that when AI inference speeds improve significantly, we might question the need for generating code at all rather than just improving code generation.
Determinism vs non-determinism in web applications
Core debate over whether web apps should behave consistently vs adaptively. Critics argue users expect predictable behavior (like cooking same meal with same ingredients), while supporters see potential for personalized, flexible interfaces that adapt to context and user needs.Performance and efficiency concerns
Discussion of computational costs, with LLM-generated responses being orders of magnitude more expensive than conventional methods. Participants debate whether the inefficiency is worth it for certain use cases or if optimization strategies could make it viable.Future of human-computer interaction
Exploration of voice-first computing where users verbally request complex tasks instead of using traditional UIs. Includes concerns about reduced human agency and predictions of societal splits between those who embrace vs reject such simplification.
6Visible from space, Sudan's bloodied sands expose a massacre of thousands
International involvement and proxy warfare
Multiple countries including UAE, China, Iran, Russia, and others supply weapons to different sides in Sudan's civil war, often for strategic interests related to gold resources and Red Sea access. The conflict serves as a proxy battleground between regional powers.UAE's role in money laundering and sanctions immunity
Discussion focuses on Dubai/UAE's ability to launder gold and evade sanctions despite backing the RSF militia. Users debate why UAE remains immune, citing their strategic balancing act and importance as a logistics hub.Scale of humanitarian catastrophe
The conflict has resulted in over 150,000 killed, 522,000 children dead from malnutrition, and millions displaced. The RSF (formerly Janjaweed) continues committing genocide against non-Arab ethnic groups in Sudan.
7SQLite concurrency and why you should care about it
- Jellyfin addressed SQLite database locking issues that caused crashes on some systems by implementing three locking strategies through EF Core interceptors: no-lock (default), optimistic locking with retry logic, and pessimistic locking that serializes all writes, providing a solution for concurrent database access problems.
SQLite SQLITE_BUSY errors and concurrency issues
Discussion centers on SQLite's deferred transaction mode causing SQLITE_BUSY errors when transactions upgrade from read to write mode. Solutions include setting busy_timeout pragma, using immediate transaction mode, and proper configuration of WAL mode for better concurrency handling.SQLite configuration and performance optimization
Users share essential PRAGMA settings needed for production SQLite use, including WAL mode, foreign keys, busy timeout, and cache settings. Discussion covers SQLite's poor defaults and the need for proper configuration to avoid common pitfalls.Database choice considerations for applications like Jellyfin
Debate over whether SQLite is appropriate for applications requiring concurrency versus using PostgreSQL. Discussion weighs SQLite's simplicity and portability against PostgreSQL's better concurrency handling for self-hosted applications.
8GHC now runs in the browser
- TerrorJack has successfully implemented GHC (Glasgow Haskell Compiler) running entirely client-side in web browsers using WebAssembly, creating a Haskell playground where users can write, compile, and execute Haskell code without server dependencies. The implementation uses GHC's bytecode interpreter since it cannot invoke C compilers in the browser environment, and currently supports the GHC library and its dependencies with potential for adding precompiled third-party packages in the future.
Haskell bootstrapping problem
Major discussion about GHC's inability to be compiled from source without an existing binary, making it unsuitable for high-security distributions. Users debate alternatives like MicroHS and compare to other languages like Rust that have solved this issue.Practical applications and learning resources
Users discuss the practical uses of running GHC in browsers (education, demos) and share recommendations for learning Haskell, including books like "Haskell in Depth" and tutorials for those who understand theory but lack practical skills.Technical implementation details
Discussion of whether the browser implementation uses WasmGC or bundles its own garbage collector, with explanations of challenges related to Haskell's lazy evaluation and the complexities of making it work with WasmGC's rigid type system.
9SailfishOS: A Linux-based European alternative to dominant mobile OSes
- Sailfish OS originated from Nokia's MeeGo project, which was abandoned in 2011 when Nokia chose Windows Phone. The MeeGo team formed Jolla Ltd. to continue development, launching Sailfish OS in 2013 with Android app support. The OS evolved through four generations, targeting both consumers and enterprise markets.
User experiences and practical usage
Long-time users praise SailfishOS as "Linux in your pocket" with features like SSH access, VPN hotspot capabilities, and native Linux tools. However, users note limitations including lack of apps, outdated browser, and hardware constraints on supported Sony Xperia devices.Company credibility and business challenges
Discussion reveals significant trust issues with Jolla, including failed tablet crowdfunding without refunds, past Russian government ties (ended 2021), and ongoing financial struggles. The small team lacks resources for proper development and hardware support.Technical limitations and alternatives
Users debate Android app compatibility layer effectiveness, outdated Firefox browser (stuck on old ESR versions), and compare with alternatives like GrapheneOS, Ubuntu Touch, and other Linux mobile platforms for privacy-focused users.
10URLs are state containers
- The author discovered the power of URLs as state management tools when revisiting PrismJS configuration encoded in a URL. URLs can store application state through path segments, query parameters, and fragments, making web applications shareable, bookmarkable, and resilient without databases or cookies. Examples include GitHub line highlighting, Google Maps coordinates, and e-commerce filters. Modern frameworks like React Router and Next.js provide clean APIs for URL state management, while plain JavaScript offers URLSearchParams for basic implementation. The key is determining what state belongs in URLs versus other storage methods.
Storing state in URLs
Developers debate the benefits and drawbacks of encoding application state in URLs. Supporters argue it enables bookmarking, sharing, and prevents broken refresh behavior. Critics cite concerns about browser history pollution, URL length limits, and creating unintentional public APIs that constrain future development.URL literacy and user experience
Discussion around the general lack of URL understanding among users, even digitally literate ones. This impacts security (phishing susceptibility), privacy (tracking parameters), and overall web experience. Tools and browsers are criticized for hiding URLs by default.Technical implementation challenges
Developers share practical approaches for URL-based state management, including encoding strategies, compression techniques, and specific libraries like Rison. Examples include weather radar sites and RSS readers that successfully implement comprehensive URL state storage.