Comment by jeroenhd
7 days ago
Recreating Aqua is the easy part. Recreating all the applications you would use day-to-day to fit the design language specified by Aqua is another. Apple's visual OS design was never that far ahead of the curve, but they managed to convince developers for their platform to stick to their guidelines rather than reinvent the wheel, making the entire computer feel more like one integrated system than a toolbox filled with differently branded tools.
This is also why most "windows style" themes fall flat: you can copy the window decorations, button backgrounds, and icons, but unless your applications are designed to look and work like the OS your mimicking, it'll all just look weird and off.
At this point "operating systems" in a commercial sense are so large that only relatively new entries can afford to rebuild their stock applications to fit the current UI theme (ChromeOS comes pretty close but you'd need to appreciate Google's design to enjoy that). macOS, Windows, and even Linux to some extent all have decades of old software to support so they can't redesign their core GUI stack without breaking everything.
In the days that an internet browser wasn't considered a core part of the operating system, there just weren't as many places to get the design wrong or off-template without Q&A noticing.
> they managed to convince developers for their platform to stick to their guidelines rather than reinvent the wheel, making the entire computer feel more like one integrated system than a toolbox filled with differently branded tools.
Browsing the web on non-Apple platforms was annoying for a few years, with web designers aping the skeuomorphic design-language of whatever the then-current MacOS X release was. Besides cargo-culting, there was no justifiable reason for brushed aluminum or linen web page backgrounds, though I'm sure it looked really great on the designers Apple computer. If you, dear reader, did this when you were younger, I hope you have grown as a person and a designer.
> [...] unless your applications are designed to look and work like the OS your mimicking, it'll all just look weird and off.
Exactly!
i no longer use luxurious wood, linen, and metal textures. these did serve a purpose at the time, though. skeumorphic design was a guidepost for a far less digital-literate user.
One of the early DAWs (long forgot the name of it) had an interface that recreated the look of a flatbed with animated reels. It ran on an old monochrome green/black monitor. I saw this in the mid-90s and was already used to seeing a waveform in timelines, so this thing really felt ancient. Apparently, the makers felt sound editors would be unable to grasp a new interface???
8 replies →
> but they managed to convince developers for their platform to stick to their guidelines rather than reinvent the wheel
This attention to detail and "one integrated system" leads me to my favorite MacOS story:
- Windows and Linux machines would always DHCP for IP addresses
- MacOS would see if you had connected to the network before and just reuse the old IP you had under the assumption that is was probably still valid
- This worked most of the time and if you turned on a Mac and Windows laptop at the same time, the Mac would have a working IP first
As someone pointed out, this was probably one of the reasons why MacOS users would often say it just "felt better" than Windows. The fact that Mac owned both hardware AND software and treated it as a holistic system led to an overall better user experience.
My first laptop was G3 Apple laptop.
It was one of the worst laptops I have ever owned. The screen died right after the warranty expired. It would take multiple reboot to get the HDMI to properly register so I could use it as a desktop ... to the point I said fuck it and just tossed it.
Dell XPS 13 was the 2nd worst.
HDMI in 1997–2003?
1 reply →
why is this a good thing? This sucks, it would randomly cause IP conflict in some cases
There's gotta be a bit more subtlety going on here. DHCP leases include a lifetime:
It's possible that older versions of macOS persisted the lease details across reboots and reused unexpired leases on subsequent network reconnections.
I am also fairly sure that I have never personally seen any evidence of any OS doing this, including macOS, including when it was still called Mac OS X. I suspect macOS simply brings up its networking stack earlier in the boot process, so the network connection is more likely to be ready and waiting by the time the desktop loads.
1 reply →
If they implemented it well, they could have just sent an arp and check if it was already taken.
Then again, I haven't ever been limited by the speed of DHCP servers... Windows is just dog-slow for a lot of things, so yeah, macos just "feels better" generally. I doubt it was related to just this IP thing.
Users would assign it to 'just that network is flakey'.. not 'my hardware is not behaving properly' because it works elsewhere.
1 reply →
> Recreating all the applications you would use day-to-day to fit the design language specified by Aqua is another.
This is (maybe tangentially) something I don't understand about the software market today; how come only Microsoft and Apple seem to be in the market for building a suite of native deskop applications, while other companies make one-off applications? Why isn't there a successful company building and maintaining a suite of common alternative desktop applications?
I can make some guesses of course.
"Why isn't there a successful company building and maintaining a suite of common alternative desktop applications?"
Sure there are but in other domains than "office".
For example CAD has few incumbent companies with their portfolios - Autodesk, Trimble, Nemetchek, Bentley. (etc)
For design - Adobe, Affinity (well it's all Canva now), then legion of smaller offerings like Clip Studio Paint.
CAD is the only domain in which I have domain knowledge but I would be surprised if there are no others.
> Apple's visual OS design was never that far ahead of the curve
That tends to happen when you're the one defining the curve.
> but unless your applications are designed to look and work like the OS your mimicking, it'll all just look weird and off.
Actually worse than not looking like Windows, at that.