zlacker

Not to disrespect this, but it used to be entirely normal to have a GUI environment on a machine with 2MB of RAM and a 40MB disk.

Or 128K of ram and 400 kb disk for that matter.

>>trollb+(OP)
Yea, but those platforms were not 64bit

>>trollb+(OP)
A single 1920x1080 framebuffer (which is a low resolution monitor in 2025 IMO) is 2MB. Add any compositing into the mix for multi window displays and it literally doesn’t fit in memory.

>>trollb+(OP)
> Or 128K of ram and 400 kb disk for that matter.

Or 32K of RAM and 64KB disk for that matter.

What's your point? That the industry and what's commonly available gets bigger?

>>maccar+y1
Do you really need the framebuffer in RAM? Wouldn't that be entirely in the GPU RAM?

>>echoan+B3
Aren’t you cheating by having additional ram dedicated for gpu use exclusively? :)

>>echoan+B3
VGA standard supports up to 256k

>>echoan+B3
To put it in GPU RAM, you need GPU drivers.

For example, NVIDIA GPU drivers are typically around 800M-1.5G.

That math actually goes wildly in the opposite direction for an optimization argument.

>>trollb+(OP)
The Acorn Archimedes had the whole OS on a 512KB ROM.

That said, OSs came with a lot less stuff then.

>>trollb+(OP)
I would like to have this again

I prefer to use additional RAM and disk for data not code

>>jerryt+M4
> NVIDIA GPU drivers are typically around 800M-1.5G.

They also pack in a lot of game-specific optimizations for whatever reason. Could likely be a lot smaller without those.

>>Rohans+26
Even the open source drivers without those hacks are massive. Each type of card has its own almost 100MB of firmware that runs on the card on Nvidia.

>>Perz1v+D
64 bit generally adds about 20% to the size of the executables and programs as t to last on x86, so it's not that big of a change.

>>forint+q5
If that is a lot less of things not needed for the specific use case, that is still a big plus.

>>jerryt+M4
Doesn't the UEFI firmware map a GPU framebuffer into the main address space "for free" so you can easily poke raw pixels over the bus? Then again the UEFI FB is only single-buffered, so if you rely on that in lieu of full-fat GPU drivers then you'd probably want to layer some CPU framebuffers on top anyway.

>>psycho+W7
It was GUI defined manually by pixel coordinates, having more flexible guis that could autoscale and other snazy things made things really "slow" back then..

Sure we could go back... Maybe we should. But there are lots of stuff we take for granted to day that were not available back then.

>>trollb+(OP)
When I first started using QNX back in 1987/88 it was distributed on a couple of 1.4MB floppy diskettes! And you could install a graphical desktop that was a 40KB distribution!

>>1vuio0+J5
To think that the entire distro would fit in a reasonable LLC (last level cache)..

>>maccar+y1
I had a 386 PC with 4MB of RAM when I was a kid, and it ran Windows 3.1 with a GUI, but that also had a VGA display at 640x480, and only 16-bit color (4 bits per pixel). So 153,600 bytes for the frame buffer.

>>snek_c+0b
640 * 480 / 2 = 150KB for a classic 16-color VGA screen.

>>jshear+k8
well, if you poke framebuffer pixels directly you might as well do scanline racing.

>>maccar+y1
It's so much fun working with systems with more pixels than ram though. Manually interleaving interrupts. What joy.

>>jshear+k8
Yes if you have UEFI.

>>beng-n+Ya
I've been wondering if I could pull the DIMM from a running machine if everything was cached.

Probably not due to DMA buffers. Maybe a headless machine.

But would be funny to see.

>>trollb+(OP)
With 320x240 pixels and 256 colors

>>the847+lc
Alas, I don't think UEFI exposes vblank/hblank interrupts so you'd just have to YOLO the timing.

>>trollb+(OP)
"640k ought to be enough for everyone!"

>>monoca+u7
That's 100MB of RISC-V code, believe it or not, despite Nvidias ARM fixation.

>>echoan+B3
You’re assuming a discrete GPU with separate VRAM, and only supporting hardware accelerated rendering. If you have that you almost certainly have more than 2MB of ram

>>echoan+B3
Computers didn't used to have GPUs back then when 150kB was a significant amount of graphics memory.

>>forint+q5
That's only RISC OS 2 though. RISC OS 3 was 2MB, and even 3.7 didn't have everything in ROM as Acorn had introduced the !Boot directory for softloading a large amount of 'stuff' at boot time.

>>pastag+p9
The OS did ship with bezier vector font support. AFAIK it was the first GUI to do so.

P.S. I should probably mention that there wasn't room in the ROM for the vector fonts; these needed to be loaded from some other medium.

>>1vuio0+J5
There’s an installation option to run apps off disk. It’s called “The Mount Mode of Operation: TCE/Install”.

>>beng-n+Ya
Like the k language!

>>jerryt+M4
Someone last winter was asking for help with large docker images and it came about that it was for AI pipelines. The vast majority of the image was Nvidia binaries. That was wild. Horrifying, really. WTF is going on over there?

>>pastag+p9
RISC OS has the concept of "OS units" which don't map directly onto pixels 1:1, and it was possible to fiddle with the ratio on the RiscPC from 1994 onwards, giving reasonably-scaled windows and icons in high-resolution modes such as 1080p.

It's hinted at in this tutorial, but you'd have to go through the Programmer's Reference Manual for the full details: https://www.stevefryatt.org.uk/risc-os/wimp-prog/window-theo...

RISC OS 3.5 (1994) was still 2MB in size, supplied on ROM.

>>maccar+y1
The Amiga 500 had high res graphics (or high color graphics … but not on the same scanline), multitasking, 15 bit sound (with a lot of work - the hardware had 4 channels of 8 bit DACs but a 6-bit volume, so …)

In 1985, and with 512K of RAM. It was very usable for work.

>>beagle+rD
a 320x200 6bit color depth wasn't exactly a pleasure to use. I think the games could double the res in certain mode (was it called 13h?)

>>mrits+eE
For OCS/ECS hardware 2bit HiRes - 640x256 or 640x200 depending on region - was default resolution for OS, and you could add interlacing or up color depth to 3 and 4 bit at cost of response lag; starting with OS2.0 the resolution setting was basically limited by chip memory and what your output device could actually display. I got my 1200 to display crisp 1440x550 on my LCD by just sliding screen parameters to max on default display driver.

Games used either 320h or 640h resolutions, 4 bit or fake 5 bit known as HalfBrite, because it was basically 4 bit with the other 16 colors being same but half brightness. The fabled 12-bit HAM mode was also used, even in some games, even for interactive content, but it wasn't too often.

>>mrits+eE
You might be thinking of DOS mode 13h, which was VGA 320x200, 8 bits per pixel.

>>Perz1v+D
Switch to an ILP32 ABI and you get a lot of that space back

>>Errone+ch
The IBM PGC (1984) was a discrete GPU with 320kB of RAM and slightly over 64kB of ROM.

The EGA (1984) and VGA (1987) could conceivably be considered a GPU although not turning complete. EGA had 64, 128, 192, or 256K and VGA 256K.

The 8514/A (1987) was Turing complete although it had 512kB. The Image Adapter/A (1989) was far more powerful, pretty much the first modern GPU as we know them and came with 1MB expandable to 3MB.

>>croes+6e
640x480 with 16 colours was standard in offices in the late 80s.

If you were someone special, you got 1024x768.

>>teamon+2O
And 6-bits per colour component.

>>teamon+2O
i remember playing with mode 13h, writing little graphics programs with my turboc compiler. computers were so magical back then.