Arturo Escartin kripy

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;

Frontend Development

Attention: the list was moved to

https://github.com/dypsilon/frontend-dev-bookmarks

This page is not maintained anymore, please update your bookmarks.

	#!/usr/bin/env xcrun swift -O

	/*
	gen.swift is a direct port of cfdrake's helloevolve.py from Python 2.7 to Swift 3
	-------------------- https://gist.github.com/cfdrake/973505 ---------------------
	gen.swift implements a genetic algorithm that starts with a base
	population of randomly generated strings, iterates over a certain number of
	generations while implementing 'natural selection', and prints out the most fit
	string.
	The parameters of the simulation can be changed by modifying one of the many

	# iPhone 6 Reservation Availability in Australia
	# !! Please use responsibly. Personal use only !!
	# `ruby iphone6.rb` - list all available models in all stores
	# `ruby iphone6.rb R405` - list available models for a specific store, Rundle Place in this example.

	require 'open-uri'
	require 'json'
	MODEL_NAMES = {
	"MN8X2X/A" => "7 32 Black",
	"MN8Y2X/A" => "7 32 Silver",

	#!/bin/sh

	test_document="{
	\"text\": \"HEAR the sledges with the bells, / Silver bells! / What a world of merriment their melody foretells! / How they tinkle, tinkle, tinkle, / In the icy air of night! / While the stars, that oversprinkle / All the heavens, seem to twinkle / With a crystalline delight; / Keeping time, time, time, / In a sort of Runic rhyme, / To the tintinnabulation that so musically wells / From the bells, bells, bells, bells, / Bells, bells, bells— / From the jingling and the tinkling of the bells.\"
	}"

	if curl -fs -X HEAD localhost:9200/top-terms; then
	echo "Clear the old test index"
	curl -X DELETE localhost:9200/top-terms; echo "\n"
	fi

	group :production do
	gem 'unicorn'

	# Enable gzip compression on heroku, but don't compress images.
	gem 'heroku-deflater'

	# Heroku injects it if it's not in there already
	gem 'rails_12factor'
	end

	#!/bin/bash

	set -exo pipefail

	BUILD_ENV=$1
	if [ `uname` == 'Darwin' ]; then
	OSX=1
	JSCOMPRESSOR="yuicompressor --type js"
	else
	OSX=

	#!/bin/sh

	echo "NB! This process could be too destructive sometimes and you may need to run 'bundle' command from your project directory."
	echo "Do you want to cleanup all gemsets?"
	read -p "(anything other than 'yes' will cancel) > " ANSWER

	if [[ $ANSWER != "yes" ]]
	then
	echo "Phew...\nMay be another day."
	else

	# You have your csv data and it looks like so... It's in a file named "my_data.csv" and we want to import it into a table named "my_things".

	"1", "Something", "0.50", "2013-05-05 10:00:00"
	"2", "Another thing", "1.50", "2013-06-05 10:30:00"

	# Now you want to import it, go to the command line and type:

	$ PGPASSWORD=PWHERE psql -h HOSTHERE -U USERHERE DBNAMEHERE -c "\copy my_things FROM 'my_data.csv' WITH CSV;"

	# Voila! It's impoted. Now if you want to wipe it out and import a fresh one, you would do this: