I’m not afraid of the Terminal, and still use it do all my config apache setups for OS X but I have a fondness for GUIs, especially ones that make tasks much easier.

These days my workflow is a combination of Sublime Text 3, Sketch, Photoshop/Illustrator, Tower, Kaleidoscope, Colorsnapper, GifBrewery, ImageOptim, Muir, and Prepros. Grunt JS does its job admirably from the CLI, which makes a utility like Prepros less a necessity than applications for Git management. I tend to favor GUIs when they empower me more than the command line. For the most part, I’m pro-SASS.Įveryone’s work flow is a little different. However, this is not about my opinions on SASS. (Edit: I lied, I love Sass, vanilla CSS is evil) They do amazing things, with a few simple for loops, I can easily generate an entire responsive grid but they lend themselves to nested tag hell, and encourage over redundant classes. I have a love/hate relationship with precompiling languages, I’m not always convinced I’m writing better CSS than if by hand but the management capabilities. Today, you have your pick of precompiliers: SASS, LESS, Haml, Stylus, Jade, slim, CoffeeScript, Livescript Time for a story… Once upon a time, when you coded the front end of a website, you wrote your CSS and JS in their native format. Most of the comparisons were to CodeKit 1.0, which wasn’t nearly as flexible as CodeKit 2.0, and before BrowserSync (for Grunt/Gulp).

It’s filled with typos, crimes against English and edits. Not long after writing it, I retired Prepros 4 for CodeKit 2/Grunt. I’ve posted a much better written, in-depth, Prepros 5 review, you can read here. The review below is for Prepros 4. (complete with Live Browser Refreshing, Preprocess Compiler, JS minifier, Remote Device Inspect Element and HTTP serving)

Compatibilizar prepros 5 con pug