medialwerk

require 'rake'
require Compass::AppIntegration::Rails.root.to_s + '/lib/compass/css_splitter'

namespace :css do  
  desc 'split css files'
  task :split do
    infile = ENV['infile'] || raise("missing infile")
    outdir = ENV['outdir'] || File.dirname(infile)
    max_selectors = ENV['max_selectors'] || 4095

medialwerk

# Was asked how I keep  my zshrc config sync'd between my computers with Dropbox

# Add a new directory in your Dropbox (or use an existing one)
mkdir -p ~/Dropbox/ohmyzsh

# move existing file to Dropbox
mv ~/.zshrc ~/Dropbox/ohmyzsh/zshrc

# symlink file back to your local directory
ln -s ~/Dropbox/ohmyzsh/zshrc ~/.zshrc

medialwerk

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't