Frontend Assets in Phoenix -- why the fuck does it need to be so hard

Ok so I wanted to do font awesome on a new phoenix website I created. Normally I’d imagine a quick 2 minute install, but it turned out to be an evening fucking nightmare. I didn’t get hella pissed off, but it’s like WTF…

http://cloudless.studio/articles/21-front-end-packages-with-phoenix-and-brunch

I don’t know if I would have ever figured it out unless I found that article.

See I fucking hate the asset pipeline in rails – http://codefor.life/serving-front-end-assets-in-rails-lessons-learned/ – so this is a lot better – but WTF WHY THE FUCK CANT IT BE EASY –

The good thing about the asset pipeline is that it is controller by the rails team, so they change something about the asset pipeline and it doenst fuck up rails and asset pipeline integration.

like this was a cool and awesome integration with brunch and font awesome… but BRUNCH WENT AND FUCKED IT ALL UP.

http://cloudless.studio/articles/4-installing-font-awesome-from-npm-in-phoenix

FUCK

I am not so mad at this because WEBPACK and GRUNT and GULP ARE SO FUCKING STUPID IMPOSSIBLE TO USE AND INSTALL. SO THANK YOU BRUNCH, BUT LETS BE REAL, PEOPLE ONLY USE BRUNCH BECAUSE THEY USE PHOENIX, SO DONT FUCK YOUR MAIN CUSTOMER ANYMORE.

Post Content