4 ms·
[Blog post author here] I agree. Um, perhaps I should have used a less obscure word than "odious"? :-) "arousing or deserving hatred or repugnance; hateful; a
by lproven 5y ago
[Blog post author here]
I agree. Um, perhaps I should have used a less obscure word than "odious"? :-)
"arousing or deserving hatred or repugnance; hateful; an odious crime; a false and odious comparison."
This does neglect the reason, which was well-known at the time and may be forgotten by now. MS was subject to a monopoly lawsuit by the US Department of Justice back then, and was trying to show that IE was an inextricable part of the Windows OS.
If IE were just a web browser, you could remove it and the OS would still function just fine; but if it's also the desktop, you can't uninstall it without crippling the OS -- therefore, it's part of the OS and MS couldn't be told to remove it.
And that's the only real reason.
The slight side-note being that "Active Desktop" was multithreaded, like the MacOS 8 Finder.
In Win95 or MacOS 7, if you started a file copy (for example), the whole desktop froze until the copy was done. You couldn't do anything else except sit there and watch the progress bar.
In MacOS 8, the Finder (the program that drew the desktop) got multi-threading along with lots of other improvements (desktop drawers, an easily-customisable Apple menu, and more). Start a big file operation and you could go do something else while it sat there working away in the background.
IE4's Active Desktop brought this to Win95 OSR3, Win98, and NT 4 if you installed IE4. But it was the only improvement. The rest was, as you say, bloat.
- Sesse__ 5y ago> In Win95 or MacOS 7, if you started a file copy (for example), the whole desktop froze until the copy was done. You couldn't do anything else except sit there and watch the progress bar. In Win95, the copy happened on the destination folder's thread. You could still open other windows and keep browsing around, but that specific window would be unresponsive.
- lproven 5y agoThat is not how I remember it, from *extensive* use at the time, but I would have to spin up a VM to try it. I don't think you're right. The OS was still running; you could switch to an app and keep working, for instance. But Explorer had only 1 thread, AFAICR, and a large file operation visibly locked that thread.
- mnl 5y agoI honestly can't remember about such details, but with IDE drives and 95A you were limited to PIO. You could enable DMA in 95B, it wasn't by default. It was in W98. That should make a drastic difference.
- lproven 5y agoI think it depended on the disk controller, no? https://www.philscomputerlab.com/windows-98-dma-mode.html https://www.philscomputerlab.com/windows-98-dma-mode.html I wrote about this in PC Pro in about 1995-1996. Because it had a true pre-emptive kernel, it could do other stuff while waiting for disk I/O, and on NT, enabling DMA made a big difference. As I recall, on 98, it just made disk access a bit quicker, that was all.
- lmm 5y agoActive Desktop was great. Wallpapers are bloat, having something you actually want to glance at occasionally like news headlines on the desktop was wonderful. I still miss it.
- lproven 5y agoGood heavens. So there was someone. How about that? BTW & FWIW, I'd say "bloat" means something that you don't need that adds complexity, memory overhead, and attack surface to a product, and probably makes it slower, use more disk, and generally makes it heavier and less responsive. I don't think desktop wallpaper counts as any of that. The memory usage is trivial, it needs no CPU or disk space, and it has no UI after it's been set. It's chrome: unnecessary functionality added only to improve the visual appearance -- but in my definitions it's not bloat.
- Krssst 5y ago> I don't think desktop wallpaper counts as any of that. The memory usage is trivial, it needs no CPU or disk space, and it has no UI after it's been set. A bitmap of 1024x768x24 is around 2MB uncompressed in memory, which could be a lot at the time. (I remember having 24MB on my machine, maybe a bit outdated for W98?) However, I guess that when a pattern is used as wallpaper, memory usage is indeed trivial (only store the pattern, blit repeatedly)
- deleted 5y ago[deleted]
- lproven 5y agoOK, yes, that's entirely fair, although I have to say that in 1998, 1024×768 was quite big and asking for it in true colour as well would be… optimistic. I think it got swapped out as soon as it could be, though. I remember moving windows aside on low-end machines and hearing the hard disk chug as it loaded the previously-obscured bits of the desktop image back in, scaled them and redrew them. (I don't remember when Windows gained the ability to scale the wallpaper. IIRC, it was in the Windows 95 PowerToys – the base OS couldn't do it. I think it also only understood `.BMP` files originally. JPG and other compressed formats only came later – probably in 98, come to think. I had a few such machines that could do 1024×768×24, but they were pro-grade kit, and as such, I ran NT 4 on them, not GameOS®™. About 1997 or so I was rather proud of my Pentium II 450 MHz in a Baby-AT case (not ATX) which had 2 Matrox cards, allowing me to run a dual-head desktop at 2048×768. I think I then went from 2×14" screens to 2×15" which allowed me to run twice 1152×864: 2304×864. So… much… desktop!