Feather – open source icons
feathericons.com
feathericons.com
Feather is great as are their design guidelines, but it needs way way more icons. Lucide picks up beautifully where it left off.
I guess some discretion is required before using any of those icon fonts. That's really not a point against it.
Anyway, my favorite feature is that the disability guy is in a rush.
That’s actually a thing now: https://blog.logomyway.com/new-handicapped-logo-and-the-hist...
For me the rushing icon does look better. But I wonder why they didn't make the icon on a more normal position, with the body and arms closer to the resting position. We don't make signage with people running except when we actually want to say that they are going fast; the same should apply here.
The article linked by grandparent says: "the new design pictures a handicapped individual with their head tilted forward, indicating their mobility and that they are in control of where they are going. The new design also pictures the individual with their arms back, once again indicating that they are dynamic and in control of their own mobility."
If you just reduce the inclination of the body and arms, you get that effect.
This wasn't meant to be a neutral change, or even a change to bring it from negative connotations to neutral - it's the equivalent of affirmative action for symbols.
But seriously, I 100% agree! No one is paying for these icons. Mistakes happen. The world is not ending if they do not get corrected immediately. We all have a ton of things we are working on and cannot always make our FLOSS side-projects our top priority.
(Though, I will readily admit that this raises some provocative questions about how much "mission critical" projects should rely on open source projects which they have no contract/SLA/affiliation with...)
Of course I'm sure the second person to touch a computer did something irresponsible with it, so what can you do, right?
I've seen plenty of terrible quality closed source projects and even some impressive high quality closed source projects that were still imperfect and open to human error.
I don't think we should have lower levels of scrutiny or expectations from open source projects. I do think the gp's criticism was exaggerated and unwarranted for any project, open or closed.
It's open source, you've seen the error and you know how to fix it. Make a pull request yourself.
If it really bothers you so much, it sounds like it would’ve taken you less time to fix it than to complain all the way over here. I’m pointing this out not because open source is often thankless (it can be), but because this kind of negativity snipe is often demoralizing even for those of us not even maintaining the project.
[1] https://iconsear.ch/search.html
I'd consider making the search experience more like https://www.flaticon.com/. The drop-shadow boxes are too distracting. Adding consistent spacing will help too.
I love that it's easy to get to the source, but having a page in between would be nice to see other icons from the set and information about where the icon is from.
I like instant search better than suggestions/autocomplete. It also works with JavaScript disabled though not instant.
For example if I search Facebook, I get dozens of icons. Now how do I find the same style of icons for Twitter, etc. If you can fix that, it'll truly make you awesome.
---
[0]: https://www.emilydamstra.com/please-enough-dead-butterflies/
My set, Microns, has fewer icons but is good for starting new projects.
https://www.s-ings.com/projects/microns-icon-font/
The icons are intentionally designed to not have too much personality. Less rounded and cutesy than Feather.
A similar project I also enjoy using is https://heroicons.com/
Probably already mentioned before (lazy to scroll) but if you’re building something and need icons don’t just use one package.
If you’re building in React or a compatible JSX library use react icons (https://react-icons.github.io/react-icons/).
It lets you pick and choose from many packs (Feather included) and if you’re careful with your selections you can meet pretty much all needs in a cohesive way. Until you can afford an in house designer :P
Similarly, Visual Studio actually comes with an icon library at https://social.technet.microsoft.com/wiki/contents/articles/..., though 2012 sadly switched from 3D icons (a mixed bag, some beautiful ones and then some awful ones like a downscaled yellow-shaded XP-era exclamation point triangle) to flat line art indistinguishable from today's icon style except in having backgrounds. You can find "totally legal" offline downloads of VS2010 on archive.org (the online installer is down).
Someone made the effort and ported them to .svg [1]
Donationware
Feather: Open-source icons - https://news.ycombinator.com/item?id=15089916 - Aug 2017 (140 comments)
(https://github.com/Remix-Design/RemixIcon)
Contains more than many similar iconsets, though hasn't seen any updates in quite a while.
(Edit: Well, it kind of already did. Has massively more GitHub stars than when i last checked.)
If I remember correctly, Material Design team did lots of i18n research for their icon pack. I assume Bootstrap icons also score well, owing to the diversity of contributors (although, I’m surprised RTL landed only recently).
(maybe an arrow into a folder, but then some new computer users don't even know what folders are because their systems don't show them to the users)
I'm also not opposed to keeping it a floppy disk. It's okay to use outdated references for things. And it's funny to hear a kid say you have a 3d-printed save icon.
Not sure it's an improvement over the floppy disk. Other variations on the prompt tend to yield things like CF cards. Although I guess the file folder with the arrow isn't too bad. (For contemporary values of "Isn't too bad" equal to "Holy shit, this thing is starting to understand abstract concepts" a few months ago.)
Automatically save a copy that you can recover from, sure, but let the user decide when and if to save it for real.
If i want something to be stored in permanent storage i explicitly request that with the Save or Save As functionality.
That is not to say that an autosave functionality is always useless, it can be useful -e.g.- for recovering from program failures, but not as a replacement for the explicit Save/Save As functionality.
A: They died to become the icon of saving.
That's not reason to drop any of them.