Cyan: Gay or European~ πΆ
*Google Home trigger sound*
π€¨π€¨π€¨
GitHub | https://github.com/atirut-w |
Blog | https://atirut-w.github.io/ |
Cyan: Gay or European~ πΆ
*Google Home trigger sound*
π€¨π€¨π€¨
Lying in bed next to Cyan
Cyan: Can you whip me?
*Google Home trigger sound*
Cyan: IT'S NONE OF YOUR BUSINESS, GOOGLE!!!
Cyan and I just lost two boxes of sushi. Like, lost.
We bought three, she ate half of one, I ate the other half, and the other two are just nowhere to be found.
I checked the fridge, the trash, the floor...
????????????
@enigmatico @abstractslug It would be more within the spirit of assembly game development to make the game run on bare metal with your own graphics driver (in assembly). And shaders written in assembly for the GPU.
Of course the game only works one one particular model of graphics card.
@enigmatico @abstractslug @mei I'd say today is very different from 1999 in that we have at least 2 different CPU ISAs in very wide use on consumer's devices, and every consumer device has some kind of programmable GPU. You can't safely assume x86 but you can fairly safely assume something like OpenGL ES 2.0.
(While there were more ISAs around in 1999, x86 was vastly more popular than mips, sparc, 68k, powerpc, etc. Nowadays neither ARM or x86 can be safely ignored.)
@enigmatico I'm arguing that targeting assembly is a much worse idea now than it was back then. Whichever ISA you target, you are going to need to be emulated in order to run on the other one.
That and you don't want to be doing the rendering on the CPU at all any more.
The best part? Through use of an expansion port you could achieve complete #NintendoEntertainmentSystem compatibility. Port #RollerCoasterTycoon to #NES you cowards!