Victor Delgado vdel26

Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.

My 3 developers team has just developed React.js application with 7668 lines of CSS (and just 2 !important). During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.

Here are main principles we use to write CSS for modern (IE11+) browsers:

SUIT CSS naming conventions + SUIT CSS design principles;
PostCSS + CSSNext. Future CSS syntax like variables, nesting, and autoprefixer are good enough;
Flexbox is awesome. No need for grid framework;
Normalize.css, base styles and variables are solid foundation for all components;

	<!doctype html>
	<meta charset="utf-8">
	<title>Example</title>

	<style>
	div {
	width: 100px;
	height: 100px;
	background: black;
	animation-duration: .5s;

	set nocompatible
	set encoding=utf-8 nobomb
	filetype off

	" set the runtime path to include Vundle and initialize
	set rtp+=~/.vim/bundle/Vundle.vim
	call vundle#begin()

	" let Vundle manage Vundle
	Plugin 'VundleVim/Vundle.vim'

	:root {
	--ease-in-quad: cubic-bezier(.55, .085, .68, .53);
	--ease-in-cubic: cubic-bezier(.550, .055, .675, .19);
	--ease-in-quart: cubic-bezier(.895, .03, .685, .22);
	--ease-in-quint: cubic-bezier(.755, .05, .855, .06);
	--ease-in-expo: cubic-bezier(.95, .05, .795, .035);
	--ease-in-circ: cubic-bezier(.6, .04, .98, .335);

	--ease-out-quad: cubic-bezier(.25, .46, .45, .94);
	--ease-out-cubic: cubic-bezier(.215, .61, .355, 1);

	const trackTime = timing => {
	const now = performance.now();
	if (!timing.startTime) timing.startTime = now;
	const elapsed = now - timing.startTime;
	const {duration} = timing;
	if (duration != null && duration <= elapsed) timing.startTime = null;
	return elapsed;
	};

	const delay = (callback, duration) => {