The Balance
Posted on
The balance between shipping and perfecting the details is what makes things great. Last night I spent 3 hours on an animation for Cheddar. It was probably overkill to make a custom animation curve with CAKeyframeAnimation, but I really wanted it to look like what I had in my head.
Looking back at it today, I'm proud of it and glad that I learned more than I cared to know about animation curves. It might have been a better use of time to just use a default curve and finish the feature instead of spending the whole time on a single animation.
I'm still not sure if learning something new and perfecting it was better than finishing in this case. Usually whenever I spend hours on a particular detail (like fading in a slight shadow at exactly the right speed) I'm never sure which side of the spectrum it falls on. I think this feeling means you're doing it right.
Strapless iPod Nano Watch
Posted on
Who needs a wristband for an iPod nano when you can just implant magnets? I'm sure he'll have fun at airports now.
(via Kevin Smith)
Introducing SSPullToRefresh
Posted on
There are tons of pull to refresh views for iOS on GitHub. Every time I need to add pull to refresh to a project, I end up hacking one of them to pieces. This is silly. I wrote a better one: SSPullToRefresh.
SSPullToRefresh is highly customizable. There is a contentView property that allows you to set the view that shows when the user pulls. This is really great because you can simply make a view conforms to the SSPullToRefreshContentView protocol you're good to go. You don't have to hack up the pulling logic.
By default, a basic content view is set if you don't provide one. See the readme for the full details on customizing).
SASS vs LESS
Posted on
Chris Coyier from CSS Tricks compares LESS to SASS in the most fair post I've seen. His conclusion:
SASS is better on a whole bunch of different fronts, but if you are already happy in LESS, that's cool, at least you are doing yourself a favor by preprocessing.
Most arguments I've read are just "I like SASS better." His is very technical comparison of the two. It's a really interesting read.
Ruby in the Browser
Posted on
Ruby just got support for Native Client.
Google Native Client (NaCl) is a sandboxing technology for running a subset of Intel x86 or ARM native code using software-based fault isolation. It is proposed for safely running native code from a web browser, allowing web-based applications to run at near-native speeds...
This is pretty exciting. This means you can start running Ruby code in the browser.