The source code is a treasure trove for those looking for an example of a larger Backbone.js application with a Rails backend and Faye for push notifications to the browser.
Thanks - Akash Manhor (https://twitter.com/hashnuke) made both of those decisions early on in Kandan's life. There have been challenges around both, but overall it's worked out very well - in fact, the faye interface opens up some really interesting possibilities. We'll have some examples of this soon.
I built http://gitego.com a few months back to keep track of watchers, forks, size, and issues over time. I'm glad they're enhancing the code-related graphs. Stats for those would be much harder to gather externally.
I'd agree with you if not for the many subtle and critical bugs I've seen introduced into our production environment due to and/or precedence problems. The increased expressiveness when used correctly is just not worth it.
Indeed, "and" and "or" are excellent for their intended use, for control flow. Like explained by the style guide the Github one is based on. https://github.com/bbatsov/ruby-style-guide
# boolean expression
if some_condition && some_other_condition
do_something
end
# control flow
document.saved? or document.save!
I'm not sold on tossing "and" and "or" out the window, but wouldn't "document.saved? or document.save!" read better as "document.save! unless document.saved?"
I tried listening to podcasts before, but get distracted... i need to listen to the podcast and try considerately on code... Electronic music and dance is good... but as a follow up question: what do you listen to this on? iPod, Computer, phone, other?
I run a website that tracks watchers on GitHub projects, http://gitego.com.
What I see is that it is incredibly rare for a project to lose watchers. It seems that people are using GitHub's watch feature as a bookmarking service.
On a side note, GitEgo tracks two[1,2] of paulasmuth's GitHub repositories, and neither of them has "lost lost around 30 watchers by the evening." He may be referring to other projects on GitHub, but even Twitter Bootstrap[3] (the most popular GitHub project), almost never loses watchers. Granted, these projects could all be gaining just a few more watchers than they are losing per hour, but the net effect is almost always a gain each day.
I think the real problem is that watching a repository doesn't engage a user in its contents. Watching commit messages fly by isn't as entertaining as reading 140 characters someone groomed for public consumption.
