mojombo

27 ms·

211.
by mojombo 16y ago
Thanks! I'm glad you like them!
212.
by mojombo 16y ago
We meet those requirements here at GitHub: github.com. Along with the official blog some of us also talk about the business on our own personal blogs: http://tom.preston-werner.com and http://ozmm.org .
213.
TomDoc - Reasonable Ruby Documentation(tom.preston-werner.com)
31 points by mojombo 16y ago|6 comments
214.
by mojombo 16y ago
This is also a big win for Windows users since the SSH setup procedure is complicated and error-prone on that platform. Once Windows tools start supporting Smart HTTP, the barrier to start using Git on Windows will be much reduced.
215.
by mojombo 17y ago
You can, you just have to know the URL: http://github.com/home
216.
Bye Bye Flash: GitHub's Network Graph is now Canvas(github.com)
149 points by mojombo 17y ago|33 comments
217.
by mojombo 17y ago
God can also use any kind of script you like to perform start/stop/restart. You can execute an external script or even write a Ruby block to interact with your managed process however you like.
218.
by mojombo 17y ago
As the author of god, I'll agree that if your only need is to ensure that a process is running, and that process isn't doing a lot of fancy daemonization or forking, then init is the best solution. In fact, on all our boxes at GitHub we use
219.
Announcing Ernie 2.0 and 2.1 (GitHub's Erlang RPC Server)(github.com)
20 points by mojombo 17y ago|1 comments
220.
by mojombo 17y ago
Like every decision Apple makes, this has everything to do with business and nothing to do with censorship or misogyny. Apple intends the iPhone/iPod/iPad to be something that everyone on the planet owns. To do that, they think that creatin
221.
by mojombo 17y ago
I find that perfecting what some would call "non-sexy infrastructure pieces" very rewarding. In fact, it's what I spend most of my day doing! Only to me, all of our infrastructure pieces are sexy. Because I wrote and open sourced a lot of t
222.
by mojombo 17y ago
You'd be surprised how often "the things that bug [our] customers the most" quickly become interesting to us. In this case, prioritization has played a huge factor. Wikis have been on our minds for a long time, it just happens that other st
223.
Uniform - Sexy forms with jQuery(pixelmatrixdesign.com)
151 points by mojombo 17y ago|33 comments
224.
by mojombo 17y ago
Erlang has the ability to keep two versions of a compiled module in memory at once (but only two, not three or more), making it possible to do hot code updates and achieve zero downtime upgrades. The message passing architecture makes this
225.
by mojombo 17y ago
It solves a significant problem that I've encountered several times in real world packaging setups. The problem it solves is outlined on the linked website. Semantic Versioning is also about more than just dependencies. It's about transpare
226.
by mojombo 17y ago
Interesting. Can you explain why you're doing one-off fixes instead of creating a general release with the fix that everyone can use? This seems like a bit of a complicated edge case that most people don't need a solution for. Semantic Vers
227.
by mojombo 17y ago
Can you elaborate on the kind of branching you're doing, and what your current favorite solution for that situation is?
228.
by mojombo 17y ago
> Hardly a new concept, and one that many companies and projects have used for ages. Certainly. And I don't claim to take credit for any of these concepts (and explicitly say so). The whole point here is to give this idea a name and cle
229.
Semantic Versioning - A technique for avoiding "dependency hell"(semver.org)
78 points by mojombo 17y ago|24 comments
230.
by mojombo 17y ago
The Erlang team uses ClearCase internally and decided that a full-history conversion to Git would be too difficult to be practical, which is why they are starting with a single commit. According to the official Erlang website: Beginning
231.
Erlang/OTP now on GitHub(github.com)
1 points by mojombo 17y ago|0 comments
232.
by mojombo 17y ago
This is a pretty nice visualization. It pegs the CPU of both cores on my MBP though (Webkit). =(
233.
BERT and BERT-RPC 1.0 Specification(bert-rpc.org)
12 points by mojombo 17y ago|4 comments
234.
Introducing BERT and BERT-RPC: GitHub's new serialization and RPC protocol(github.com)
57 points by mojombo 17y ago|17 comments
235.
How We Made GitHub Fast: A detailed look at GitHub's new architecture(github.com)
214 points by mojombo 17y ago|23 comments
236.
by mojombo 17y ago
A number like 500 req/s is irrelevant without an understanding of what the site has to do. For a simple site that does simple database lookups, I'd expect more than that. For a site like GitHub that has to do database lookups and pull large
237.
by mojombo 17y ago
Why is that shocking? Can you elaborate?
238.
by mojombo 17y ago
Each box can handle plenty more than 16 workers, but we currently don't need that many, so it's pointless to run them. Our frontend machines generally sit about 60% idle. We wanted to have plenty of headroom on our new setup. Also, our Ruby
239.
by mojombo 17y ago
We run 12GB of memcache on each slave file server. Hardly idle!
240.
by mojombo 17y ago
That's true, but we are not counting Gists in these Repository stats.

More ›