Paul Young paulyoung

How not to scale css

Several years ago I got curious about how css worked at scale. When I first started out, there weren’t nearly as many learning resources as there are now. CSS zen garden was amazing, at the time it showed how much you could change a design without altering the html.

In the beginning, that’s what people sold me as a feature. By writing css, you could make a change one place and have it propagate everywhere. In principle this sounds pretty good. I’m lazy so I like doing things one time. But eleven years later, my experience on both large and small teams is that this is the most terrifying thing about css.

https://twitter.com/thomasfuchs/status/493790680397803521

In the past few years a lot of very smart people have been thinking more about CSS and this has lead to some fascinating discussions around how to build ‘scalable’ ui and how that relates to CSS. When I first started to think about scalability I naturally started to read every blog post and watch every tech talk I could get

¯\_(ツ)_/¯

	# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env
	# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced
	# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start
	# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running.

	# Add the following to your shell init to set up gpg-agent automatically for every shell
	if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then
	source ~/.gnupg/.gpg-agent-info
	export GPG_AGENT_INFO
	else

	import Foundation

	public func getASTString() -> String {

	// get the file path for the file "test.json" in the playground bundle
	// let filePath = NSBundle.mainBundle().pathForResource("FirstTtest", ofType: "ast")

	// get the contentData
	let contentData = NSFileManager.defaultManager().contentsAtPath("a.txt")

	const daggy = require('daggy')
	const compose = (f, g) => x => f(g(x))
	const id = x => x

	//===============Define Coyoneda=========
	const Coyoneda = daggy.tagged('x', 'f')

	Coyoneda.prototype.map = function(f) {
	return Coyoneda(this.x, compose(f, this.f))
	}

	import { createStore, applyMiddleware } from 'redux';
	import { Observable, Subject } from 'rxjs';

	const api = type => {
	console.log(`calling API ${type}`);
	return new Promise(res => setTimeout(() => res(), 500));
	};

	const actionOrder = (actions, order) => actions.every((action, index) => action.type === order[index]);
	const actionPredicate = actions => filterableAction => actions.some(action => action === filterableAction.type);

	final class CenteringView: UIView {
	// MARK: - Initialization

	init(contentView: UIView) {
	super.init(frame: .zero)

	addSubview(contentView)
	contentView.translatesAutoresizingMaskIntoConstraints = false

	NSLayoutConstraint.activateConstraints([

	{-# language KindSignatures #-}
	{-# language PolyKinds #-}
	{-# language DataKinds #-}
	{-# language TypeFamilies #-}
	{-# language RankNTypes #-}
	{-# language NoImplicitPrelude #-}
	{-# language FlexibleContexts #-}
	{-# language MultiParamTypeClasses #-}
	{-# language GADTs #-}
	{-# language ConstraintKinds #-}

	// Variables just contain an integer. We can have a maximum of `Int.max` variables in our program. ¯\_(ツ)_/¯

	private struct Var {
	static var freshVarIx = 0
	let ix: Int
	init() {
	Var.freshVarIx+=1
	ix = Var.freshVarIx
	}
	}

	// http://twitter.com/nicklockwood/status/690540488433274881
	// @0xced hmm, you're right. So under what circumstances does it populate the error param? Why even have it at all?

	// http://twitter.com/0xced/status/690543445404991488
	// @nicklockwood Just disassembled again, seems it can errors if a string fails to convert to UTF8. @nst021 Idea how to produce such a string?

	// http://twitter.com/mikeash/status/690564095322542081
	// mikeash: @0xced @nicklockwood @nst021 Maybe try an NSString containing half of a surrogate pair.

	#import <Foundation/Foundation.h>