Hacker News new | ask | show | jobs
by signal11 944 days ago
Higher resolutions (and the accompanying resource sizes) would be hell for 32-bit OSes though.

Also, it’s kind of amazing that many web pages these days are larger than Doom shareware’s zip size.

4 comments

Not true. Or it's true because of software bloat and resource waste these days.

When I was a teenager, I wanted to see what was the maximum resolution my monitor supported. It was a Samsung Syncmaster 14" entirely analog, no OSD, with analog adjustment knobs on the bottom. The video card was a Matrox Millennium II 8MB VRAM and the OS was Windows 3.10. The maximum resolution that I could get was 1600x1200 @ 41Hz interlaced. That's almost 2K (1.92K to be more precise). 41Hz interlaced hurt my eyes like hell but everything worked on the software side.

There's a lot more to it than just increasing the resolution. Graphics, animations, font rendering quality, huge images, the list goes on.
Most of that is GPU-accelerated anyway so the OS / CPU doesn't need to do much beyond telling the GPU what to do.
That's clearly not true.

I can run a full virtual music studio on my Mac, with tens of channels, each with a collection of plugins, and multiple samples and audio files streaming off SSD at the same time.

None of that is GPU accelerated - except maybe the UI, which is split across three 4k monitors

On Windows 95 I could barely play a single WAV at once, and a dual monitor system was an exotic luxury.

Hardware has gotten a lot faster, and the software can do more without crashing. (Mostly.)

The real problem has been the move to browser+cloud for productivity applications. The OS is a front end for the browser, which is a front end for remote compute. This is hugely slow and inefficient compared to making everything work locally, and perhaps including some cloud-ish hooks for sharing.

Graphics: Win3.10 had just the right amount.

Animations: NO, THANK YOU!

Font rendering quality: It increases with font size, which is needed for high res displays. Besides, current font authors don't waste any time doing manual font hinting like the old fonts had. Good luck having crisp font rendering without manual hinting! It's all just a blur since antialiasing was introduced.

Huge images: How huge? Win95 without any patches can allocate 500MB to a single program (image viewer). That's 170 megapixels @ 24bit-color.

I mean, I was rocking a 1920x1200 CRT for my Win2k/Win98SE dual boot system that I had until WinXP64. They were plenty capable of efficiently using the screen real estate.
I remember seeing Win9x UI on a really high resolution CRT display for the first time in early 2000s. It just had so much visual appeal to it.
I ran a 1999-era machine well into the 2000s (I think 2007?) with Windows 98SE on 1600x1200 and it worked great, and faster than the XP computer I had.
1) if you're just referring to pointer size, wouldn't it be mostly a matter of computer hardware and recompiling to 64bit exes? Functionally it's the same 2) there's less cluster and more optimization. Why would it suffer at anything?