Hacker News
1OpenCiv3: Open-source, cross-platform reimagining of Civilization III
- OpenCiv3 is an open-source reimagining of Civilization III built with the Godot Engine, currently in early pre-alpha development. The December 2025 "Dutch" Preview 1 release features standalone mode with placeholder graphics, though importing original Civ3 files is recommended for better visuals. Available for Windows, Linux, and Mac, it aims to modernize Civ3 while retaining original gameplay.
Macos compatibility and security restrictions
Discussion about Mac's increasingly restrictive app security that requires xattr commands to run unsigned apps, Apple's $100/year developer fee for notarization, and comparisons to the old "cancel or allow" Windows parody ads. Users debate whether this protects users or creates unnecessary friction.Civilization game preferences and nostalgia
Community discussion about why Civ 3 was chosen over other entries in the series, with users sharing their favorite versions and explaining that preference often correlates with the first Civ game played. Mentions of FreeCiv, UnCiv, and other open source alternatives for different versions.Development challenges and community support
Core developers lacking Mac hardware seek community volunteers for testing, with multiple users offering help with M4 Macs and developer accounts. Discussion includes Godot C# implementation details and the technical architecture separating game logic from UI.
2France's homegrown open source online office suite
- Suite Numérique is an organization developing open-source collaborative tools including a video conferencing app powered by LiveKit, a note-taking and wiki platform, file sharing system, team management application, and collaborative inbox, all built primarily with Django and React for digital sovereignty.
Digital sovereignty concerns
Discussion centers on Europe's need for technological independence from US companies like Microsoft. Commenters debate the risks of depending on "hostile powers" for critical infrastructure, with mixed views on whether building sovereign alternatives is worth the cost and complexity.Technical architecture and performance
Users critique La Suite's technical choices, particularly the use of Python/Django, arguing it's too slow for enterprise use. Some defend the architecture while others suggest alternatives like Go or question whether this constitutes a true "office suite."Funding and development approach
Debate over whether Europe should invest billions in digital sovereignty projects or rely on private enterprise. Discussion includes criticism of current funding levels and questions about the political sustainability of long-term government tech investments.
3Hackers (1995) Animated Experience
- This appears to be a title or heading referencing the 1995 movie "Hackers" with an associated name "David Vidovic" and "Animated Experience," but contains no meaningful content to summarize beyond this basic identification information.
Nostalgia and cultural impact of the movie "Hackers"
Users share how the 1995 film "Hackers" inspired their careers in technology, with many watching it hundreds of times and relating to its hacker culture ethos. The movie captured the spirit of curiosity-driven exploration and anti-corporate sentiment that resonated with the early tech community.Technical appreciation and easter eggs
Discussion centers around the interactive Gibson visualization website, with users searching for hidden "garbage file" easter eggs and appreciating both the original movie's practical effects and this modern recreation using web technologies.Soundtrack and quotes
Participants enthusiastically share memorable quotes ("Hack the planet!") and praise the movie's electronic soundtrack featuring artists like Orbital and Prodigy, with many still using it as coding music decades later.
4An Update on Heroku
- Heroku is shifting to a sustaining engineering model focused on stability and security rather than new features. Current customers can continue using the platform with no changes to pricing or service, but new Enterprise Account contracts will no longer be offered.
Heroku's internal decline and stagnation
Former employees explain that Heroku's problems began before Salesforce acquisition, citing rapid growth leading to tech debt, scaling issues, founder departure, and shift from results-focused to process-focused leadership around 2012-2014.Corporate communication and end-of-life signaling
Users criticize Heroku's vague announcement about "sustaining engineering model" as poor corporate communication that fails to clearly explain what's happening to customers while essentially signaling the platform is entering maintenance mode.Heroku alternatives and migration options
Discussion of replacement platforms including Render, Fly.io, Railway, Coolify, and self-hosted solutions like Dokku, with users sharing experiences about pricing, features, and deployment simplicity compared to Heroku.
5Sheldon Brown's Bicycle Technical Info
- This appears to be footer or metadata information from a webpage showing a URL for bookmarking (sheldonbrown.com/index.html) and indicating it was last updated by John Allen. There is no substantial content to summarize.
Sheldon Brown's impact on bicycle education
Users share how Sheldon Brown's website taught them bicycle repair, wheelbuilding, and maintenance. Many credit his detailed guides with getting them started in cycling and bike mechanics, praising the generous spirit of knowledge sharing.Personal connections and memories
Discussion of Sheldon Brown's death in 2008 at age 63, with users sharing personal encounters, correspondence, and how his work influenced their cycling journeys. Some note his wife's academic background and the closure of his bike shop in 2021.Old web vs modern resources
Comparison between Sheldon Brown's dated but still valuable content and modern resources like Park Tool videos. Users appreciate the simple, passionate style of early internet knowledge sharing while acknowledging newer tools.
6Microsoft open-sources LiteBox, a security-focused library OS
- LiteBox is a security-focused sandboxing library OS that reduces attack surface by minimizing the host interface. It enables easy interoperability between various platforms and supports diverse use cases like running Linux programs on Windows, sandboxing applications, and operating in specialized environments like SEV SNP and OP-TEE.
What is LiteBox and library OS concept
LiteBox is Microsoft's open-source sandboxing library OS that reduces attack surface by limiting host interface. It enables running unmodified Linux programs on Windows, sandboxing applications, and works with various platforms like SEV SNP and OP-TEE. Discussion clarifies that a "library OS" links directly to programs rather than using syscalls.Microsoft's trustworthiness and quality concerns
Users express skepticism about Microsoft's reliability due to Windows bugs and declining product quality across Teams, Office, Azure, etc. Defenders argue MSR is independent and individual engineers shouldn't be judged by Windows issues, while critics cite systematic problems with corporate culture and management decisions.Technical implementation and dependency concerns
Discussion covers the project's 238 Rust dependencies and whether they've been properly audited, use of Copilot for development, and technical questions about sandboxing effectiveness when the host OS is already compromised. Some view dependency count as manageable given popular crates used.
7GitHub Actions is slowly killing engineering teams
- A former CircleCI employee who has extensively tested nearly every CI system argues that GitHub Actions is fundamentally flawed despite its market dominance. The author criticizes its broken log viewer that crashes browsers, confusing YAML syntax with expression language gotchas, slow Microsoft-hosted runners, insecure marketplace dependencies, and poor user experience requiring multiple clicks to view build failures. They recommend Buildkite as a superior alternative and suggest Garnix for Nix users, concluding that GitHub Actions only succeeds because it's conveniently integrated into repositories.
CI systems evolution from specialist to generalist
Discussion about how CI tools evolved from framework-specific systems to general workflow orchestrators, with debate over whether this was beneficial or if specialized systems better serve certain domains like game development.Local reproducibility vs remote CI
Debate about the importance of being able to run CI processes locally, with emphasis on avoiding "programming in configuration" and the costly feedback loops of commit-and-wait development cycles.GitHub Actions reliability and usability issues
Criticism of GitHub Actions' declining reliability, poor log viewing experience, YAML configuration complexity, and comparison with alternatives like Buildkite that offer better developer experience.
8We mourn our craft
- A programmer reflects on the inevitable rise of AI coding tools, acknowledging their effectiveness while mourning the end of hand-coding as a craft. Despite moral reservations, practical concerns like career competitiveness and financial obligations will likely force adoption of these tools, marking the end of an era for those who found artistry and satisfaction in writing code manually.
Joy vs. loss of craftsmanship
Sharp divide between developers who see AI as enabling more creativity and those mourning the loss of hand-coding. Some celebrate the "golden age" where they can build faster, while others feel programming craft has been reduced to reviewing AI output rather than creating.Economic disruption and job security
Debate over whether AI threatens programming jobs or just changes them. Discussion ranges from "only code monkeys are threatened" to concerns about widespread job losses, with disagreement on timeline and severity of displacement.Systemic technology concerns
Broader worries about computing's direction including black-box AI systems, subscription software models, undocumented hardware, restrictive operating systems, and centralization of services, with some seeing current era as a "software dark age."
9Show HN: I spent 4 years building a UI design tool with only the features I use
- A solo developer created Vecti, a streamlined design tool focused on essential features like pixel-perfect grid snapping and performant canvas rendering, without bloated collaborative or enterprise features. Built in the EU with privacy focus, it offers a free tier and targets solo designers and small teams seeking simplicity.
Feature selection and the 80/20 rule
Discussion centers on Joel Spolsky's observation that everyone uses a different 20% of software features, making it challenging to create simplified tools. Commenters debate whether building focused tools for specific user segments can succeed versus trying to serve all users.Competition with Figma and market positioning
Users question why they'd choose this tool over Figma, noting similar UI design and missing features like components and prototyping. The developer responds humbly, acknowledging it's a personal project meant to scratch their own itch rather than replace Figma.Product development philosophy
Debate over "build what you love and see if others love it too" versus extensive market research. Some advocate for passion-driven development while others emphasize the need for customer validation and market research before building commercial products.
10Show HN: If you lose your memory, how to regain access to your computer?
- The author created a secure memory recovery system after experiencing bike-related concussions and worrying about losing access to important data. The system requires 5 out of 7 trusted friends to agree before unlocking stored information, providing a safety net if memory loss occurs.
Physical vs digital storage methods
Discussion of storing master passwords in physical safes vs digital methods, with warnings about fire damage to safes and comparisons to bank deposit boxes. Users share experiences with house fires and debate the security tradeoffs of physical storage locations.Shamir secret sharing implementations
Multiple users reference existing and past projects using Shamir secret sharing for password recovery, including Keybearer from 2010 and other GitHub projects. Discussion covers technical implementation details and the challenge of making recovery user-friendly.Trust and coercion risks
Debate over whether memory loss or friend betrayal is more likely, with concerns about incentivizing friends to collude for access to assets. Users discuss the need to periodically update trusted contacts as relationships change over time.