IdeaWell

Project ideas from Hacker News discussions.

Wine ported to OpenBSD

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Theme 1 – Excitement about the Wine port and its technical achievement
Users praised the feat of running Windows games (including The Witcher remaster) on OpenBSD and highlighted the low‑level work needed to make it happen.

“Insane work! … There's even the remaster of The Witcher running! If I had money I would simply gift to those guys.” – ndbe
“Just this one patch gives us Notepad, Notepad++, Factorio, and many many other games.” – NethIafin

Theme 2 – Debate over AI/LLM assistance and code‑quality concerns
The discussion turned to whether the port relied on AI, worries about “slopcode,” and OpenBSD’s strict stance on maintaining understandable, maintainable patches.

“Afaik I think I saw the author say on reddit he used AI to prototype and then rewrote it.” – asveikau
“If ‘slopcode’ means code where the author consulted AI at all, yeah. But it's pretty easy to tell if the author AI‑spammed without even reviewing all of it …” – mahboi
“Theo de Raadt would spin in his grave — after the security implications of this to OpenBSD gives him a fatal aneurysm.” – overfeed

Theme 3 – Hardware (GPU) driver support as a limiting factor
Commenters noted that while AMD and Intel GPUs are well supported, lack of Nvidia drivers remains a hurdle for gaming and broader desktop use on OpenBSD.

“Nvidia support for OpenBSD is not really a thing … With AMD and Intel, you have support for modern hardware in the tree.” – ninjin
“OpenBSD has had hardware‑accelerated 2D and OpenGL since, well, forever‑ish. Just not for modern Nvidia GPUs.” – daneel_w
“Those are the versions in the coming release.” – bentley (referring to upcoming AMD/Intel drivers in OpenBSD 8.0)

🚀 Project Ideas

Generating project ideas…

OpenBSD Wine Patch Generator (OWPG)

Summary

  • Automates generation of OpenBSD‑specific Wine patches for GS register handling, SIGUSR1 emulation, and ptrace restrictions, sparing developers from low‑level assembly work.
  • Core value proposition: keeps the OpenBSD Wine port in sync with Wine upstream while reducing manual effort and error‑prone patching.

Details

Key Value
Target Audience OpenBSD ports maintainers and Wine developers wanting to run Windows applications on OpenBSD
Core Feature Rule‑based patch generator with optional LLM‑assisted instruction decoding; outputs ready‑to‑submit diffs
Tech Stack Python, LLVM MC for instruction decoding, optional local LLM (LlamaCpp) for complex cases
Difficulty Medium
Monetization Hobby

Notes

  • HN commenter NethIafin described the %gs register stubbing as “by far the most complex bit” and welcomed a tool that could automate it.
  • Provides a tangible way to reduce friction in porting Wine, likely sparking discussion on upstream acceptance and improving OpenBSD gaming desktop viability.

OpenBSD Nvidia GPU Compatibility Layer (ONGL)

Summary

  • Delivers a userspace wrapper that enables use of the Linux Nvidia kernel driver (or enhanced Nouveau) on OpenBSD, providing hardware‑accelerated OpenGL/Vulkan for Wine and native apps.
  • Core value proposition: fills the major Nvidia driver gap on OpenBSD, unlocking gaming and GPU compute without requiring a native kernel driver.

Details

Key Value
Target Audience OpenBSD users with Nvidia GPUs who want gaming, Wine, or GPU compute workloads
Core Feature Userspace driver that loads Linux Nvidia kernel module via the Linuxulator (or VFIO passthrough) and exposes GL/Vulkan through Mesa
Tech Stack C/Rust, libdrm, Linuxulator shim, Mesa, optionally Rust‑based GPU abstractions
Difficulty High
Monetization Hobby

Notes

  • Commenter ninjin noted “Nvidia support for OpenBSD is not really a thing” and many users expressed desire for Nvidia gaming support.
  • A compatibility layer would directly address this pain point, likely generating enthusiastic discussion and practical adoption among the OpenBSD desktop community.

OpenBSD AI Patch Review Assistant (OAPRA)

Summary

  • Automatically reviews patches submitted to OpenBSD ports for AI‑generated code signs, license compliance, and style, giving maintainers confidence before merging.
  • Core value proposition: enables responsible use of AI‑assisted development while upholding OpenBSD’s strict copyright and security policies.

Details

Key Value
Target Audience OpenBSD ports maintainers, contributors, and the core team
Core Feature LLM‑assisted analysis that flags suspicious copyright, suggests rewrites, and verifies buildability via sandboxed builds
Tech Stack Python, GitHub Actions, OpenBSD build sandbox (QEMU/vmm), optional LLM for explanations
Difficulty Medium
Monetization Hobby

Notes

  • Users such as freedomben highlighted that “LLMs could probably write drivers… but… copyright concerns” and others warned about AI‑generated slop.
  • OAPRA would directly address these worries, encouraging safer AI experimentation and fostering discussion on AI policy within the OpenBSD project.

Read Later