Earlier quoted context omitted.
There absolutely was TCP/IP support in Windows 95 from the very beginning. It was not installed by default but it was trivial to add via the Network applet in Control Panel. SLIP/PPP was also supported and you had basic utilities like Telnet and FTP included so you could connect to the Internet right out of the box. No web browser, though. Internet Explorer 1.0 shipped with the optional Plus! pack.
For some reason we used Trumpet stack. Could it be that OS stack didn't work very well at first?
Designing Windows 95’s User Interface
151–160 of 402 posts
Re: Designing Windows 95’s User Interface
#152It's hard to remember, but even though Windows 3.11 was extremely dominant at the time, it was by no means assured that Windows 95 would be the success that it was. The very first version missed wildly in some big ways (MSN was a folder integrated into the desktop, for example, and no TCP/IP support [*Edit: yes there was - I misremembered.]), but the core, underlying redesign of the GUI was so profoundly good it prop…
Well, I agree that there was no comparison with System 8, but not in the sense you mean. I think that the Mac back then was head-and-shoulders a better system than Windows. It might still be, but they're both so painful to use now that it's very difficult to pick a winner.
The Macintosh system was very understandable, very clean. Extensions were an easy-to-understand way to extend one's system, and easy-to-disable too. The window system itself was better-thought-out and less-confusing than Windows's was. The Finder was much more straightforward than the Windows equivalent (was it called the File Explorer back then?). The way that the Mac associated programmes to files (with an application code & a file code) was much better than the extension-based naming of Windows. The way that the Mac used its files' resource fork was great.
Programming a Mac back then was very clean & straightforward. I don't think there's anything today as nice, except maybe Cocoa, maybe. Certainly not the Windows 95 API!
Re: Designing Windows 95’s User Interface
#153Earlier quoted context omitted.
> Running the latest version of 10 it still feels very unfinished which I hope Microsoft intend to do something about. Might depend on what particular parts of the OS you come across. I use Win10 on my work notebook [1] and besides the long startup times [2], I haven't noticed anything "unfinished". In fact, Windows very subjectively feels more polished than macOS which I used before (until December). Then again, I d…
Pretty sure he is referring to the configuration structure. You get this fancy 8.1 sidebar configuration screens that may solve 80% of a average users tasks, but once you start digging you'll find configuration Windows in the style of W7, and if you dig even harder you'll even find stuff that looks straight out of 98. I am a linux users myself, configuration inconsistency gives me nightmares.
Re: Designing Windows 95’s User Interface
#154Ah, remembering Win95 makes me yearn for a simple, clean GUI again. All of the major operating systems have been in a downward slide in terms of UI/UX since the early 2000s. As far as UI/UX is concerned: Windows peaked with Windows 2000. MacOS with OS9 (Why didn't they just throw the classic GUI on top of Darwin)? At least with *nix you have choices and can go with one of the several variants of Gnome 2 (Xfce, et al)…
Just curious: why Windows 2000 and not Windows 7? Win7 was still internally consistent (as opposed to the newer tablet / mobile / pc / washing machine UIs of later versions) and provided few additional UI enhancements over 2k.
The most internally consistent design was that of NT 3.1 - it was a true classic in many respects. As far as general usefulness, performance, and versatility nothing can compare with Windows 10 (except Linux, of course).
Re: Designing Windows 95’s User Interface
#155Earlier quoted context omitted.
> I still get frustrated on OSX when I minimize a window and have to hunt around for it Windows user here. Honest curiosity: does anyone know why the minimize / maximize works on the Mac the way it does? I mean, what's the rationale to design it like this?
No idea... And a few versions ago Apple changed the maximize button to go full screen, which made it useless for the 95% of us who don't use one app at a time. Minimized windows also used to show up at the bottom of the screen when using "Expose", but then Apple changed the name to "Mission Control" and removed them. Just one more example of them slowly but surely driving its Mac customers away.
Re: Designing Windows 95’s User Interface
#156It's hard to remember, but even though Windows 3.11 was extremely dominant at the time, it was by no means assured that Windows 95 would be the success that it was. The very first version missed wildly in some big ways (MSN was a folder integrated into the desktop, for example, and no TCP/IP support [*Edit: yes there was - I misremembered.]), but the core, underlying redesign of the GUI was so profoundly good it prop…
The one thing I don't understand that Mac has never adopted is being able to use open and save dialogues as mini file explorers (move stuff around and rename, specifically). Having to switch to Finder to move or rename a file that has the same name as the file I'm trying to save is ridiculous. Of course I never need to do this anymore since I only work on text files under revision control, but it still seems odd to m…
++edited to clarify language.++
Re: Designing Windows 95’s User Interface
#157Earlier quoted context omitted.
It drove me nuts when they updated the maximize button behavior to full screen. I use ShiftIt, a neat little Open Source tool that help me manage windows sizes and positions (including minimizing and maximizing): https://github.com/fikovnik/ShiftIt I've recommend it to pretty much any Mac user I've met.
Haven't used ShiftIt, but I've been using Spectacle to accomplish the same thing. They seem pretty similar, overall. Works pretty well and I've had no issues.
Re: Designing Windows 95’s User Interface
#158Extremely easy to use, extend and navigatee, at the time it’s only missing piece was a built in “file explorer” but there were also so many 3rd party options by then, too (Directory Opus being my personal favorite).
Re: Designing Windows 95’s User Interface
#159Earlier quoted context omitted.
I have no idea... I'm came from ~18 of Windows & Linux usage and everyone always told me macOS is THE OS with the best usability. But I can't confirm this. Minimization of windows is shitty and maximization even more. When I maximize, often just the height is changed, when I go back to "normal" the height and the width is changed, so I always have to adjust the width manually. When I minimize a few windows, it's impo…
Know what you're talking about. Since I've switched back to Linux I can't imagine working without workspaces - each one dedicated for specific task/app - and every time staying with specific order so e.g. 1 workspace: Browser, 2nd: Code editor, 3rd: Terminal, 4th: File explorers etc. I used to it so much that I automatically use shortcuts to access it immediately - switching between minimized windows using alt + tab…
and if you have many windows open (in win 10 at least) you don't have to press alt+tab 10 times in a row to choose your desired program, you can hold alt+tab and use arrows.
Re: Designing Windows 95’s User Interface
#160Earlier quoted context omitted.
To be fair, Windows' file open/save dialogues are so far ahead of everything else that the competition seems like unusable garbage to me. I'm glad KDE/Qt chose to emulate these very closely on Linux. Wouldn't want a desktop where my only choice is Gnome's take at this. (On the flip side, Windows' select-a-directory dialogue of the same vintage is such an utter piece of garbage that I can't imagine there being any ove…
Because that is extremely non-intuitive. It's an "Open" and "Save" dialog. That is what it should do. Joe Public is not going to know it does anything else, yet it does.
For example: I literally can't know how I can save a file using Gnome's dialogue in the general case, e.g. if the dialogue opens at /foo, and I navigate to /foo/bar using the dialogue, but then go back to /foo ("bar wasn't the right place after all"), I can't save the file there any more. "bar" will be selected. Clicking "Save" while a directory is selected will not save, but navigate instead. Now I'm in "bar" again. I go back to /foo and try to click something else, say a file. This changes the to-be-saved-file's name to the selection.
After I asked someone who uses Gnome as their main desktop they told me "that's easy: you just have to ctrl+click on the selected directory to de-select it, then you can save in the current directory".
That, my dear readers, is indeed unusable garbage.