Sep 23, 2004 here! 285k scrobbles. Always been a loyal user. My use goes back far enough that I would have scrobbles queued up for when my dialup connection came online to push the days’ missed scrobbles up.
I initially moved to it because Shortcuts broke my "generate 2h of music I rarely listen to" shortcut (it stopped being able to add music to playlists - hilarious for an in-house app talking to an in-house app!) and someone suggested Marvis because it has a "dynamic smart playlist" and it also has integrated scrobbling.
You can pretty much replace the Apple Music frontend with Marvis (at least on iOS) and everything works the same (because it's still using Music as its backend.)
Those icons were well-designed for the newly computerized office employee of the day. The new school of icons are made by graphic designers for other graphic designers.
I agree with the author. I understand many of the reasons others give here for why icons could be beneficial- localization, literacy, vision issues, etc. all are great reasons to supplement text with icons, theoretically. But I disagree that these icons, I mean those shown as examples in the Apple menu, Safari menu, or Google Docs menus- actually convey anything useful and really do prove the authors point that they’re poorly implemented.
I realize it may be generational and privilege based, as I can read English and have a good deal of computer literacy. To my eyes the icon trend of flat, minimal icons paradoxically ask a user to possess a higher degree of computer fluency to successfully parse the artistic intent of the icon and map it to its function. When these icons don’t accurately convey their function (the Paste icon is a blank clipboard. What’s that do?) and when the design language is inconsistent within the same application and OS (do cogs mean Preferences? Services? you’re building a very confusing world for most of the user group types you claim to be helping.
It doesn't actually matter that much what the icon is. It's impossible to creat icons people would fully understand - otherwise you wouldn't need a label at all.
The function of the icon is to have distinct shape so you are able to visually distinguish menu items quickly in future (more you use the app).
There are other factors like consistent placement that can help. This icon approach is good especially if you have common shared menu items over the OS or they change their placement throughout the app.
The IKEA instructions are generally regarded as a triumph of simplicity. Yet on more than one occasion I've come across cases where a few words in a call out would have prevented having to redo some step after later realising that some features had to be oriented a particular way - the pictures not quite conveying their intention until it was obvious in hindsight.
> The function of the icon is to have distinct shape so you are able to visually distinguish menu items quickly in future (more you use the app).
In theory, yes. But if you look at the examples in the article, the shapes are basically all similarly-sized circles.
In the Apple example, "System Settings" is circle (A gear with barely discernible teeth.) "Recent Items" is a circle (a clock.) "Force Quit" is a circle (a rounded! octagon.) "Sleep" is...a circle with a line through the bottom third. "Log Out" is...a human silhouette in a circle! (Why?)
It doesn't matter what the icon is as long as the icons are distinct, and today's icons aren't.
Others have brought up the Office 97 style for good reason. Everything has an icon, on an icon toolbar. Every command can also be on a file menu but most of them there don’t have an icon. The ones that do are special or intended to draw your attention.
And there’s a consistent metaphor: for example the web browser is represented by a globe for the world wide web. So the “hyperlink” function is a globe with a chain. This the “preview as web page” is a globe with a magnifying glass (whereas the print preview command is a sheet of paper with a magnifying glass.).
This icon language hints at function through its form and helps serve as a cue, a reminder, or a visual representation of
its function.
And it all worked on 640x480 256 color screens. They are thoughtful and useful. These plain flat uninformative icons are just rude.
Sure. There are also icons that are plain flat and don't use metaphor and work great. Play, share, hamburger, bluetooth, power... i am sure there are more. Icons are more about familiarity than anything.
I assume you were very familiar with Office 97. I can tell you people born in 97 are probably not. High chance they might not like and understand the icons because they aren't familiar with them.
It's like when everybody wants to design logo as unforgettable as Nike. But in reality anything people see 20 times a day people will remember.
> The function of the icon is to have distinct shape so you are able to visually distinguish menu items quickly in future (more you use the app).
I wrote it in a different comment elsewhere: this is exactly why you don't want icons on every menu item. When everything tries to be stand out, nothing does. It's much easier to distinguish groups and "it's the third item below the icon" than "out of these identical looking icons one of them points to a menu item that does what I want".
Sure! I agree. My comment above probably seems like i think this new Apple design direction is good. I don't. Tahoe seems like amateur hour.
What i was mainly saying is that the icon does not have to describe the label for it to be effective. That doesn't mean that usage/quality of the icon suddenly doesn't matter.
A lot of apps people use these days are cloud-first and automatically save all the time, so there's not even a save button to have a floppy icon for! The icon to say that it's synced looks like a cloud, and if you're using a web browser it'll probably have a Download button with a download icon. No floppy disks in sight.
I wouldn't be surprised if there's computer users out there that wouldn't recognise the "save icon".
I disagree. Not all it's "autosave on cloud", and some apps keeps having an explicit save something button or option.
I recently had a discussion about replacing the "save icon" (IE. the old floppy disk icon) for an icon with an arrow pointing down, for a button that saves (don't download!) a custom query of the user in the system. Perhaps it could be replaced with another icon, but not by someone that everyone would think is "Download".
Growing grains is no longer relevant. You can just walk into any supermarket and purchase packaged cereals, breads, and cakes, and you don’t have to deal with operating a tractor, cultivating soil, or sowing seeds.
The article is too optimistic in its view of how short-form video allows everyone to partake in these trends. In an attention-driven culture where nothing cool can be kept a secret, as the very essence of coolness would be defined not by the thing itself but by how many people watched your tiktok about it, you end up with these nonsense low-quality “viral trends” that everyone is talking about because everyone is talking about it.
Very little of it is actually good. So what then, if it’s able to spread faster than ever before? It stinks!
Plenty of search overview results I get on Google report false information with hyperlinks directly to the page in the vendor documentation that says something completely different, or not at all.
So don’t worry about writing that documentation- the helpful AI will still cite what you haven’t written.
If it helps, Macintosh Garden has a FTP server, but everything is un-organized in one of 2 folders, apps and games. Too slow to get a directory listing on these older systems but you can get a file directly if you know what you’re looking for.
Very cool and much needed. I run an iMac G3 on OS 9, and it’s a bit of a challenge to download files on because most websites don’t work, and the FTP directory listings on Macintosh Garden are so long that they never finish loading for me. Granted it’s nothing compared to the file transfer difficulties of the past, but it’s nice to see a period-correct workaround.
Oh, that’s quite alright, the way I do it is to browse the site on my phone which lists the file names for each download, then just type them in to the FTP program. You really need to browse the site to know what everything is, anyhow, as there are multiple downloads for each program- demos, different languages, patches etc. Thank you though!
There’s so much value in consistent, expertly-written technical documentation that outsourcing it to the hallucination machine is a pointless exercise in aggravation. I do not wish to read machine-mangled slop. I want an expert to write expertly.
I am afraid the choice in many OSS projects is not slop vs expert-written content but LLM-assisted content or nothing.
I recently produced a bunch of migration guides for our project by pointing Claude 4 Sonnet at my poorly structured Obsidian notes (some more than 5 years old), a few commits where I migrated the reference implementation, and a reasonably well-maintained yet not immediately actionable CHANGELOG. I think the result is far from top-notch but, at the same time, it is way better IMO than nothing (nothing being the only viable alternative given my priorities): https://oslc.github.io/developing-oslc-applications/eclipse_...
