1. 9

  2. 4

    Fceux took a little more time because it required GTK+, a GUI toolkit. But hey, after porting over roughly 140 packages, what’s five or six more.

    This is absurd! How productive are they?

    So Chris whipped up an OSS-ish audio framework and wrote a driver for the Intel HD Audio device, common in PCs. The Raspberry Pi 3 is our favorite ARM platform, so he also wrote a PWM audio driver for that.

    1. 3
      1. 1

        It’s quite NT like in design ideas and style. You have NT tropes like the Object Manager, but adapted for a system where POSIX, rather than Win32, is the primary environment.

      2. 1

        The performance on a Raspberry Pi 3 isn’t too bad, Mario is quite playable despite the lack of accelerated graphics.

        This made me laugh (loud enough that I hope I didn’t wake the people in the room next door). There was no such thing as “accelerated” graphics in the 80s when Mario was released. The fact that something that ran so well on something so little, now requiring accelerated graphics is… a huge step back, it seems, from where we once were in terms of getting everything out of the devices you had.

        edit: but love their productivity