It's also mentioned a bit here - http://facebook.github.io/react/blog/2014/09/16/react-v0.11....

Is this much different than running `sass --watch` with livereload? Seems to me it'd be nearly identical.

If you are just doing a single page its not that different, but if you are building a web app and trying to tweak the CSS inside a modal or something that isn't there on page load it makes a difference. Instead of refresh -> click button to show modal again, it lets you see the changes as you make them.

It updates as you type which makes for a completely different experience.

I wouldn't say that's a completely different experience. It's the same experience minus having to hit save (which I'd imagine is fairly automatic/in the subconcious for most devs). I'll have to try it out and see for myself though I suppose.

What would a better alternative be for `var self = this` ? I use it all the time, never thought of it as an anti-pattern as long as it's only declared where you actually need it.

> What would a better alternative be for `var self = this` ?

    function foo(){};
    setTimeout(foo.bind(this),1000);

That being said, I'm not entirely crazy about that method as well.

A billion binds on every nested function you see. It's gross :)

None of these devices are one div... http://i.imgur.com/IwhB56A.png

Sure, look up "single div" on codepen and you'll find tons (http://codepen.io/search?q=%22single+div%22&limit=all&order=...). I don't think this website claims any new technique, It just shows off a collection of things made using it...

I was wondering that too... With some sort of insight into the correct response, one might be able to learn rather than just be tested. A lot of fun regardless.

Same here, but SourceTree just seems to get so slow after a fair amount of use.

SourceTree crashes like all hell for our team. I like the pretty visualisation of the branches, and it's not bad for git newbies, but it actually feels like a relief using the command line most of the time.

Is there a reason to use SourceTree a lot? I only fire up Source Tree when I'm feeling too lazy to compose a search command from the terminal. Of course, `git log | grep phrase` usually does the trick but if I need anything fancier (date ranges, for instance) I'll just fire up ST.

I use it mostly for the graphs... We work between a ton of branches and it's nice to see the visualization. Also, it's a lot faster when I have to push multiple branches to multiple repos (looking through 2 remotes with 7 branches each right now).

what does its visualization offer that gitk --all doesn't?

I use it to read commit log messages and see what changes were made to the files.

For actual commiting, branching, etc I just use the terminal.

Visually tracking merges. Even minimalist command-line-only people I know use basic GUI apps like gitk for this.

Yeah, the bugs (it occasionally needs a full restart) in SourceTree definitely hold it back. I'm willing to put up with them for all the other features, but I can understand how others wouldn't.

It seems like this is more of a workflow than just a framework. Zurb and bootstrap don't come with build tools as far as I know, whereas this includes a gulpfile and a bunch of other stuff that's very common in my workflow. This feels more yeoman-esque + generator to me.

Edit: Totally posted this before I read 'Web Starter Kit is inspired by Mobile HTML5 Boilerplate and Yeoman's generator-gulp-webapp, having taken input from contributors to both projects during development. Our FAQs attempt to answer commonly asked questions about the project.'

Yeah. that is a very good summary. If you want build process and tooling to help then we have that based on the tools that we think are the best, however we don't force workflow on people if they don't want it.

Noticed Paul Irish is no longer active on H5BP, is he now on team Web Starter Kit or working on the broader Web Fundamentals?

Paul Irish has given us guidance, input and feedback and is on the same team as me, but Addy Osmani is the main driver of starter kit, with me leading Web Fundamentals.

Thanks for the insight. Given his broader influence and role at Google it made sense he was involved in some way.

Funny this should show up today. Just got this error yesterday on one of our properties from maxmind, and sure enough, it was a payment issue. First time I'd seen it in use.

With that bounce-back effect it doesn't seem like it was designed with usage in mind.