Live data from Hacker News

Font Awesome 4 released

fontawesome.io

21–30 of 97 posts

Re: Font Awesome 4 released

#21
Seems like a lot of people don't like the namespaces changes. I actually really like this! I suppose it's cumbersome even if you're building a project where you have full control. Then again - come on, we're talking about search&replace for 10 minutes here. And in more complex projects, you should have had a flexible function to handle icons anyways.

Why I really, really like it: If you're building something in a namespace polluted environment (say, a component for a popular CMS), this is a damn god-send.

I was on the fence before, from now on, it's fontawesome all the way for all my projects. They've done an amazing job so far and I'm looking forward to what they will do next.

Re: Font Awesome 4 released

#22
post #9

I hoped for more than 10 icons :-( Any advice on how to "add" some other SVG icons to the mix and generate the whole font package?

This update is about getting the CSS right. Cleaning it up, speeding it up, making it leaner. More icons in future versions.

Re: Font Awesome 4 released

#24
post #21

Seems like a lot of people don't like the namespaces changes. I actually really like this! I suppose it's cumbersome even if you're building a project where you have full control. Then again - come on, we're talking about search&replace for 10 minutes here. And in more complex projects, you should have had a flexible function to handle icons anyways. Why I really, really like it: If you're building something in a nam…

It's also customizable in the LESS or SCSS as a variable. Want to go back to the icon-* prefix? No problem.

Re: Font Awesome 4 released

#25

They renamed the icons. They don't just break apps when they do that, they break users. At some point things like the names of icons should be frozen. I love Font Awesome of course. But please!

This is why it is a major release. It breaks compatibility for the sake of moving forward.

Re: Font Awesome 4 released

#26

370 icons is nice, but what i really want is a tool that lets me put together a smaller subset from multiple icon fonts that only has what my app needs. A global font-icon library from which to assemble this subset would be ideal. These collections are trying to cater to everyone by growing in size when the better solution here is a modularizer.

http://fontello.com/

Re: Font Awesome 4 released

#29
post #21

Seems like a lot of people don't like the namespaces changes. I actually really like this! I suppose it's cumbersome even if you're building a project where you have full control. Then again - come on, we're talking about search&replace for 10 minutes here. And in more complex projects, you should have had a flexible function to handle icons anyways. Why I really, really like it: If you're building something in a nam…

It's also customizable in the LESS or SCSS as a variable. Want to go back to the icon-* prefix? No problem.

Well thanks for reminding me how profoundly lazy I am ;-)

And hey: Again, kudos!

Post reply on HN