Mastodawn

C:\KKJ\>

2d ago

Codex is porting my old game (for Firefox OS) to my ZIG engine :D

Work in progress but it mostly works :)

#ZigLang #Codex #Porting

Hacker News 3d ago

Porting 3D Movie Maker to Linux

https://benstoneonline.com/posts/porting-3d-movie-maker-to-linux/

#HackerNews #3DMovieMaker #Linux #Porting #OpenSource #Gaming #TechNews

Porting 3D Movie Maker to Linux - Ben Stone Online

McZee meets a penguin!

Ben Stone Online

Script Kiddie 4d ago

#Linux gains more critical #Windows apps: 3D Movie Maker and Space Cadet Pinball

source: theregister.com/oses/2026/05/1…

It's not only a native port, they also had to do more work to make it 64-bit clean, add native file load and save dialog boxes, #MIDI background #music via #FluidSynth, and a video player powered by #GStreamer – among other things. Currently, they're looking at making a #RaspberryPi version as well.

Who even needs #Microsoft #Windows anymore?

#news #software #linux #software #game #gamer #gaming #foss #floss #freedom #hooray #future #computer #os #porting #port

Linux gains more critical Windows apps ... 3D Movie Maker and Space Cadet Pinball

Further demonstrating its role as industry default OS the versatility of modern porting tools

theregister

Hacker News May 5

Bun is being ported from Zig to Rust

https://github.com/oven-sh/bun/commit/46d3bc29f270fa881dd5730ef1549e88407701a5

#HackerNews #Bun #Rust #Zig #Programming #Language #Porting

docs: add Phase-A porting guide · oven-sh/bun@46d3bc2

Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one - docs: add Phase-A porting guide · oven-sh/bun@46d3bc2

GitHub

Michael Knudsen May 4

I'm porting some code from POSIX to Windows. Fairly simple: poll(2) on STDIN_FILENO and on an FD for a UART. Set .events and check .revents. read() / write().

On Windows this involves waiting for events on handles, which is fine. Except, the wait-for-multiple interface only informs of the first event, so either the event list must be rebuilt without the event, or each subsequent event must be checked on it's own using the wait-single interface. This seems complex with no apparent benefit.

On Windows checking stdin seems to involve a special Console API which seems to provide "almost-fgets(STDIN_FILENO)" via ConsoleRead() , but I also seem to have to handle "CR key-up", and other keys, e.g. ctrl, also seems to generate unhandled events that must be peeked and discarded with ConsoleReadInput() to avoid blocking in ConsoleRead().

The UART is a whole other story, or rather more of the same. Everyone seems to say you need to use threads that block and then communicate using control events or use "async / overlapped IO" but my entire application is single threaded, and adding multiple new classes of software bugs to interface with a UART in 2026 seems nuts.

#swdev #windows #porting