Key idea: Ghostty, a terminal emulator developed by Mitchell Hashimoto, is being moved off GitHub due to concerns over GitHub’s reliability, corporate direction under Microsoft, and declining service quality.
Discussion highlights: Users debated the reasons behind GitHub’s decline, citing Copilot prioritization, organizational bloat, and reliability issues. Some criticized emotional attachment to proprietary platforms, arguing that dependence on GitHub contradicts open-source principles.
Community sentiment: Mixed—sympathetic to Hashimoto’s personal connection but broadly critical of GitHub’s current state. Many see the move as a symbolic rejection of platform lock-in and a call for more resilient, decentralized tooling.
2. Belgium stops decommissioning nuclear power plants (948 comments)
Key idea: Belgium reversed its nuclear phaseout policy, extending the operation of its last two reactors until 2035 amid energy security concerns following the Ukraine war.
Discussion highlights: Commenters noted the contradiction between climate goals and anti-nuclear stances, with praise for pragmatic energy policy. Historical context was provided on previous shutdowns and safety records.
Community sentiment: Strongly pro-nuclear, viewing the reversal as long-overdue. Many criticized environmental groups for delaying low-carbon energy deployment and emphasized nuclear’s role in grid stability.
3. Claude Code refuses requests or charges extra if your commits mention "OpenClaw" (707 comments)
Key idea: Anthropic’s Claude Code reportedly blocks or throttles users whose commits reference “OpenClaw,” a third-party AI tool, suggesting active interference with competing services.
Discussion highlights: Users confirmed behavior changes, including session terminations and usage caps. Some interpreted this as a reaction to load spikes from OpenClaw automation, while others saw it as anti-competitive censorship.
Community sentiment: Concerned about transparency and fairness. Criticism focused on Anthropic’s erratic policy changes and perceived weak leadership, damaging trust in the platform.
Key idea: Zed, a modern, AI-integrated code editor, launched its 1.0 version, emphasizing speed, collaboration, and remote development via SSH.
Discussion highlights: Praise for performance and UI, but criticism over default linting behavior in legacy projects and lack of advanced search features. Licensing concerns were raised about data usage terms.
Community sentiment: Enthusiastic but cautious. Users appreciate Zed’s innovation but want more configurability and clarity on privacy. Integration suggestions included adopting Ghostty’s terminal backend.
5. For Linux kernel vulnerabilities, there is no heads-up to distributions (525 comments)
Key idea: A security disclosure controversy arose when a Linux kernel exploit was published without prior notification to major distributions, exposing systems to immediate risk.
Discussion highlights: Debate centered on whether the reporter or kernel team should notify distros. Greg Kroah-Hartman clarified that legal constraints prevent selective early disclosure.
Community sentiment: Critical of the kernel project’s disclosure policy. Many argue that structured coordination with distros is essential given Linux’s widespread use in production systems.
Key idea: xAI released Grok 4.3, an updated large language model with improvements in tone adaptation, voice input accuracy, and agentic capabilities.
Discussion highlights: Users praised Grok’s natural language style and high-quality voice mode. Criticisms included underdeveloped apps, lack of memory, and missing project integration features.
Community sentiment: Positive on model performance, especially for informal use. However, frustration exists over poor tooling and lack of developer-focused features despite subscription costs.
Key idea: A critical Linux kernel vulnerability (CVE-2026-31431) in the AF_ALG crypto API allows local privilege escalation via a 732-byte exploit.
Discussion highlights: Experts urged disabling CONFIG_CRYPTO_USER_API_* to mitigate risk. Confusion arose over patch status across distros, with some labeling it “moderate” severity despite exploit ease.
Community sentiment: Alarmed but pragmatic. Many reiterated that AF_ALG is unnecessary and high-risk, advocating for its deprecation in favor of userspace cryptography.
8. Uber torches 2026 AI budget on Claude Code in four months (432 comments)
Key idea: Uber reportedly exhausted its annual AI budget in four months due to widespread use of Anthropic’s Claude Code by engineers, with 70% of code now AI-generated.
Discussion highlights: Debate over productivity ROI: some questioned cost efficiency, while others contextualized spend as a small fraction of R&D. Concerns arose about performance incentives driving overuse.
Community sentiment: Skeptical but open-minded. Many challenged the lack of outcome metrics, suggesting that cost alone doesn’t indicate value or waste.
9. Can I disable all data collection from my vehicle? (328 comments)
Key idea: Rivian’s support page outlines user options for limiting data collection in EVs, raising questions about trade-offs with safety updates and connectivity features.
Discussion highlights: Concerns about OTA-only recall remedies and lack of user-accessible update methods. Privacy issues were highlighted, including carmakers collecting sensitive personal data.
Community sentiment: Wary of surveillance and vendor lock-in. National security implications were noted, especially for foreign-made EVs with remote data access.
10. Talkie: a 13B vintage language model from 1930 (326 comments)
Key idea: Talkie is an experimental 13B-parameter LLM trained exclusively on pre-1930 text, simulating the worldview of that era.
Discussion highlights: Users found it entertaining but unreliable, often generating plausible-sounding historical inaccuracies. It reflects early 20th-century biases, such as optimism about perpetual peace.
Community sentiment: Amused but cautious. Seen as a novelty rather than a tool, with warnings against using it for factual queries due to high hallucination rates.
Key idea: Texas Instruments launched the TI-84 Evo, featuring a 156MHz ARM CPU, replacing decades of Z80-based architecture in its graphing calculators.
Discussion highlights: Engineers praised the upgrade but lamented TI’s monopolistic pricing and outdated business model. Nostalgia was common, with anecdotes about early programming experiences.
Community sentiment: Cynical toward TI’s market dominance but appreciative of incremental improvements. Many view the device as overpriced for its educational utility.
12. AI uses less water than the public thinks (310 comments)
Key idea: A blog post argues that AI’s water consumption is minor compared to agriculture and urban use, especially when contextualized per task.
Discussion highlights: Some challenged this view, citing lawsuits revealing Google’s large water usage in California. Others advocated comparing AI to discretionary water use like car washes.
Community sentiment: Divided. While many agree AI is not a primary water concern, there is growing demand for transparency and sustainable scaling as data center demand grows.
13. Apple accidentally left Claude.md files in Apple Support app (304 comments)
Key idea: Files named “Claude.md” were found in Apple’s Support app, suggesting internal use of Anthropic’s AI tools in product development.
Discussion highlights: Speculation grew about Apple’s AI integration, with some linking it to recent software quality issues. Questions arose about source control practices and AI-generated documentation.
Community sentiment: Curious and skeptical. While not alarming in terms of security, it highlights shifts in Apple’s development culture and possible overreliance on AI assistance.
Key idea: The article explores how extreme frugality, often rooted in scarcity, can become counterproductive in higher-income stages of life.
Discussion highlights: Commenters shared personal stories of thermostat wars, delayed upgrades, and guilt over spending. Some linked it to FIRE movement behaviors and psychological patterns.
Community sentiment: Reflective and empathetic. Many acknowledged the tension between prudent saving and self-imposed deprivation, especially in dual-income relationships.
15. Ask HN: Who is hiring? (May 2026) (258 comments)
Key idea: Monthly thread where companies post engineering job openings, spanning startups in fintech, robotics, and biotech.
Discussion highlights: Listings included roles in Singapore (mosquito control tech), NYC (HSA/FSA fintech), and Amsterdam (autonomous construction robots). Emphasis on generalist engineers and full-stack capabilities.
Community sentiment: Engaged and opportunity-focused. Recruiters provided detailed stack and culture insights, attracting interest from developers seeking meaningful, niche applications.
This content is for informational purposes only and does not constitute financial, investment, or trading advice. Always consult a qualified financial professional before making any investment decisions.