Minify css with codekit code#

Minify css with codekit code#

When I am discussing compiling for the sake of this article, I am strictly talking about compiling the code with a preprocessor in order to spit out code in common web languages that are read by a web browser. There are many types of compilers and interpreters that differ wildly depending on what platform and programming language are used. In regards to web development, a web browser compiles Javascript in real-time via its customized javascript compilers, and web servers run (primarily) PHP/Python/Ruby/Java/Node.js each with its own real-time compilers. Some languages must be compiled before they can be run and some programming languages use Just-In-Time compilers (compiling on the fly) which are languages that are not compiled until the code is executed. For web development, many utilities/libraries (like Node.js and docker) require some basic terminal knowledge to use.Ĭompiler - A utility that transforms source code into another type of data that an operating system or program or web browser can understand. Commands are entered and run via the terminal on a computer, for most users this is done via a BASH terminal on a Linux/Unix variant like macOS (Formerly OS X) or Ubuntu (Linux). Mini-Glossary of TermsĬommand-line Interface(CLI) - A GUIless (graphical user interface) way to interact with a computer. (How's that for a review? You can essentially skip the rest of this review if you want.)Īs with my previous review, I'm starting with a mini-glossary of terms and how they relate to the review below. Postulation aside, If I can bring the tiniest bit of sanity or elucidation to this review, then I'll consider this a success.Īlso, this review may sound like I'm focusing on the negative (isn't that the way of 2016?), this is because CodeKit 3 is a very mature, very stable product and you probably should buy it if you like CodeKit 2 or fancy a GUI for task managing. I also worry until the fissures start forming, front end web development is a hostile environment for junior developers, due to the dearth of knowledge required to be independently successful. I imagine in less than a decade we may see a fragmentation of front end development into perhaps two or more divisions, starting with javascript app developers. The primary focus is on HTML, CSS, and Javascript, even if we abstract ourselves from it with technologies like JSX, Sass, and TypeScript. The great unifier between these professions is the core technologies: we all live and die (primarily) in the browser. It's also a wild mix of several professions including but not limited to: app developers, animators, data visualization architects, content/information architects, CMS (content management system) templaters, UX/UI designers, all residing under a very wide umbrella called front end development. Readers may want to revisit my previous review for context as I spend more time explaining the usefulness of a task manager and Sass.įront End Development is wildly a caustic field to learn as every week we're talking about some hot new JS framework. To explain the differences between CodeKit 2 and 3 requires certain vernacular, vocabulary, terminology, and industry acronyms. I'd like this review to be as accessible to novice coders and beginners as possible, but it will inevitably be more technical. It seems fitting that this now is officially the most longspun single article I've written for my blog edit: oh how naive I was when I wrote this, now that I have a 20,000+ word article. As the saying goes: Imitation is the highest form of flattery. The review was popular enough to be ripped off by a few hack writers on other blogs like which managed to use a verbatim copy of my review's final points.

It was a meditation on task management in the world of front end development.

Back in January of 2015, I posted the longest continuous blob of text I had written since college, a review titled 9 months with Codekit 2: A review.