framebuffer

The aesthetic is totally based on people running emulators showing you the framebuffer in a way it was never meant to be seen.

They are probably just running a browser directly on the framebuffer (no X) on a Linux kernel.

If everything is rendered server-side, and the client is a dumb remote framebuffer, then yes, you'll notice 100ms of input lag.

The 800x600, 16-bit hicolor (that's what I used at the time) framebuffer had a bit under 940 kB.

For example the camo-suit basically used the framebuffer as texture, from the location where the character was rendered - so it looked a bit like shimmering!

I'm just using the mainline Kernel with Simple Framebuffer support, and U-Boot.

On the XBox One I believe it's used as a framebuffer.

I read through the first section on assembly optimization almost completely in order, and used some of the graphics algorithms in an ancient Linux framebuffer project.

It will be like a VM plus an OS API: -DOM replace GUI frameworks (like Qt) -Canvas replace framebuffer (or GDI) -JS File API replace fopen() (or with emscripten virtual FS) -...

Something that takes a framebuffer as input and simulates the electric signals that control the magnets around the tube, how those magnets affect the electron beam, how the beam interacts with the shadowmask, etc.

The high-level scene graph interface is purely functional, but rendering such a scene graph is an imperative process: binding textures, vertex arrays, shaders, writing to a framebuffer, etc.

Remote access can be achieved by running a special Wayland server on the remote side that connects to a Wayland client on the local side and exchanges framebuffer and event data with that client.

The end of that page says "You should use a product based on the Remote Framebuffer Protocol (RFB), such as a member of the VNC family." I'm personally using a Chromebook, and there is a VNC app that works well.