My dad barely knew how to run things in windows 3.1 but he still regrets the day he installed windows 95 because it was all downhill from there when it came to him knowing what was going on.
This has made a lot of people very angry and been widely regarded as a bad move.
Seriously though, this is the first properly good UI for a desktop computer. Mac OS (or I guess Macintosh OS at the time) was okay, but reliant on the global menu and weird drop-downs. Windows kept everything self-contained. Even multi-window programs tended to use the “multiple document interface,” i.e., windows inside windows. Tabs weren’t really a thing yet.
It also crashed if you looked at it funny and had the antivirus capabilities of warm cheese. But there’s damn good reasons Windows 7 was the same experience, extended, rather than replaced. It’s more-or-less what I style Linux to look like. And in light of that I’m kinda pissed off any OS ever struggles to remain responsive, when this relic ran smoothly on one stick of RAM that’s smaller than my CPU’s cache.
Thoroughly familiar with it; don’t care. The global menu has always been goofy because of the invisible relation to some open window. Usually a small window floating out in middle of the desktop, because Mac OS took forever to adopt any concept of “maximize.” I’m still not sure they do it right.
Does it? I never pay attention to what version work has me running but hitting the maximize button is still exclusive full screen as effectively a new desktop
If you hold down one of the modifier keys, either Options/Alt or Cmd I don’t quite remember which, and then click the maximize button it does the normal Windows style maximize.
It usually maximizes it Windows style as well. I feel like I’ve had more inconsistency in behavior from that (like it would sometimes just fill the width but not the height), but nothing I can reproduce right now.
Googling around suggests it’s a global setting. Having recently used an Xfce version that didn’t want to super+arrow, maximize-vertical is an okay tool, but outside of super-duper-widescreen, it’s not what I’d ever want by default.
Lol this is my biggest beef with MacOS: the extent to which you have to memorize a bunch of utterly non-intuitive key combinations just to do basic tasks. Like taking a screenshot, which remains an absurd nightmare.
In its basic form, Fitts’s law says that targets a user has to hit should be as big as possible.
Dear god, my biggest beef with using a smart phone is that UI designers 1) love to have tiny buttons for shit, and 2) the tappable areas for those buttons are almost never made larger than their tiny graphics, so it’s a bitch to actually tap them.
I used to be a mobile app developer, and when I wrote apps by myself I would always expand the tappable areas so they were easy to hit with fat fingers. My last job was working for a huge cable company (maybe the name rhymes with “bombast”) and whenever I expanded the tappable area of a tiny button the UI designers would pitch a fit and insist that that not be done. Management would agree with them on the grounds that expanding the tappable area would require too much time to implement - and then they’d order me to spend even more time un-implementing it.
Something that irritates me in desktop design is, there’s a clickable icon. There’s no box around it to represent a button, just the icon on a blank background. You move your mouse towards the icon. When you get close to the icon, a box appears around it. You take this to mean “this object will be interacted with when you click the mouse.” You click the mouse. Nothing is achieved. You have to move the mouse into the actual borders of the icon, it’s just that now icons get visibly excited that you might pick them.
Windows 95 legitimately had better UI than that “Material” bullshit, via relief shading conveyed through four fucking colors. The hierarchy of elements is instantly visible. Buttons even popped in and out when clicked. There’s just no excuse for how minimalism fetishists have taken over user experience.
The full screen app contained in a single window was great! I hated the Mac eat fo many windows floating around. My ADHD was so overwhelmed by all the tiny windows instead of a clear one.
First off, Apple licensed the idea from Xerox, they didn’t steal it. Second, Apple lost because they had a badly worded contract with Microsoft for implementing Word for Mac that could be construed to allow them to copy the system’s API and thus UI.
Microsoft marketing hasn’t gotten any better about song choices. A few years ago their ads had soft bleep-bloop tunes and “go baby, go baby, yeah we’re right behind you.”
The song is “Cherry Lips,” by Garbage. It’s the twink anthem.
And it’s still not as tone-deaf as whichever Bill Hicks target picked out “hey ho let’s go” from the god-damned “Blitzkrieg Bop.”
Huh, I guess you said Windows version? I read it for some reason as l"east bloated Microsoft OS". In my defense, I was still drinking my morning coffee.
You weren’t stoked for XP? XP is the OS that got me into computing. Before XP computers were a novelty to me. When XP came out they finally seemed powerful enough to accomplish cool things with.
I learned a lot with XP because it required constant trouble shooting. Was a buggy mess imo. I was more excited about hardware advancements and cool games at that time.
Well. 4 MB was a bit of a stretch. I remember buying a RAM upgrade to 8 MB to get it to run decently. Cost me 200 DM on top of the 200 for the Windows upgrade. It was a huge leap compared to Windows 3.1, though. And this stuff just was a lot more expensive back in the day.
• no streaming/subscription fees
• no ads
• rocks have very wide adoption rates
• cave art can last thousands of years without power
• content is auto-saved without a dvr
• cave art programming is tangible, tv programming is not
I don’t need insurance, I don’t need no parkin space
and if you try to clamp my horse he’ll kick you in the face
I don’t pay no tax, fuck NCT
you’ll arrive in style if you ride with me
32 bit hacked and kludged onto a 16 bit system that was still MS-DOS at the core. It was a mess. A highly unstable "wonder how it's even working" mess. The "lol Windows always bluescreens" memes came from this era because of this. The switch to NT and pure 32 bit from boot to desktop for consumer OSes with Windows XP made the stability issues mostly a thing of history unless you had bad drivers or hardware.
And then starting with Vista, Windows went to 64 bit. It was a complete rewrite of Windows and is way more stable because it requires every driver to be signed by Microsoft. You can disable the signed driver requirement, but then you’re risking stability.
It was a whole new kernel. They didn’t rewrite every single utility, but the kernel was a rewrite along with things like diskpart and the boot loader. The core of the OS. They also dumped all of the old 16 bit legacy apps.
I would like to see a source for that. I know they rewrote critical subsystems (like the audio and video stack), but the whole kernel? I don’t think so.
This might come as a shock to you, but Windows 95 isn’t even an operating system. It’s a GUI shell that runs on DOS, which is a 16 bit operating system. There is no Windows 95 kernel.
It’s a bit more complex than that. Intel CPUs (to this day) boot in real mode, which is what DOS is using. In this mode, the system only has access to 640k of RAM. Windows 95 and later switch the processor to protected mode, where the system gets access to all of the RAM and also to memory protection features, so processes can’t real and write each other’s memory. However, in this mode it’s impossible to run real mode code, such as the one provided by DOS.
DOS games had a trick where they briefly switched back to real mode to execute DOS functions (mostly reading and writing to disk) and then back to protected mode, but I don’t think that Windows 95 did that.
Also, the part no one ever brings up: No per-program volume control. Ugh. That was so actively irritating until they finally added it (was it in XP? or not until 7?)
No per-program volume control was entirely the fault of whatever program you were using, not Windows. The Windows audio API supported global and application-level volume from the beginning with Windows 95 (even Windows 3.1 had it). Even if Windows 95 had not had application-level volume control, a developer could have implemented it for their application since they were composing the audio data sent to the API for playback (in other words, they could have just attenuated all the sample values to a lower volume).
I already had one of those fancy new-fangled CD-ROM drives. You could get a computer magazine with a cover-CD and it had all the patches for all current games and major software packages. So cool.
en.wikipedia.org
Hot