rtomayko

10 ms·

61.
by rtomayko 16y ago
Funny how these things work: http://img.skitch.com/20100806-n839s48kxx3gq6ae3m7ru45t6j.pn... http://img.skitch.com/20100806-dy2ghicjxgac7dpmdd2pwhdntc.pn...
62.
by rtomayko 16y ago
The GitHub homepage had support for the Konami code with the commercial launch, IIRC: http://github.com/site
63.
by rtomayko 16y ago
> GitHub rocks, it has really changed the contributor attitudes for my main project, I am a paying customer (another account) Thanks! > and just really hope you guys are around a long time! We'll be here. It's a profitable business
64.
by rtomayko 16y ago
That's mostly correct. We use the email addresses provided in the commit Author and Committer fields and correlate them with the email addresses associated with GitHub user accounts. The commit Author/Committer email addresses are also used
65.
by rtomayko 16y ago
Yep. It's not bad. I cloned the [experimental git repository]( http://ftp.netbsd.org/pub/NetBSD/misc/repositories/git/pkgsr... ) to `/usr/pkgsrc` and was able to install most packages I tried. They seem to lag behind current versions quite
66.
by rtomayko 17y ago
Also, I personally wouldn't call what we do "extreme agility" (whatever that means). "Flexible", "minimal process", "ad hoc" are all more accurate (and less gut wrenching) ways of describing it if you ask me.
67.
by rtomayko 17y ago
You can pass an anonymous function or lambda: def foo(thing, block): thing = "cruel " + thing block(thing) # like `yield thing' or 'block.call' in ruby def bar(thing): return "hello " + thing foo('world', b
68.
by rtomayko 17y ago
Yep. `yield` in Ruby is a normal anonymous method call. It pushes a new frame onto the stack. `yield` in Python works more like Ruby's [Generator]( http://ruby-doc.org/stdlib/libdoc/generator/rdoc/classes/Gen... ). It freezes the current st
69.
by rtomayko 17y ago
I recommend "me MONKEY TAIL domain FULL STOP com". More: < http://ascii-table.com/pronunciation-guide.php&#62 ;
70.
by rtomayko 17y ago
Me too, actually. I tried to keep Ron 100% markdown compatible but broke that with the `<VAR>` syntax. It'll probably break with Markdown more in the future, as I can already see places (pre-formatted blocks) where I'm going to want
71.
by rtomayko 17y ago
> Actually, antonovka did an excellent job explaining it above. The most important aspect is that threads are "lighter weight" than processes. They use less memory and are quicker to context switch (usually). Processes and threads have
72.
by rtomayko 18y ago
Me too :)
73.
by rtomayko 18y ago
Ahhh, I see. Like telling a joke in the first person because it just works better. Well, that's definitely good to know. It does read as if you were forced to discover the concept independently, though, which might be a tad confusing for th
74.
by rtomayko 18y ago
I'd say only positively. Regarding the article, this statement really freaked me out: > So, we’ve got an idea - why can’t we place such a server in front of our application and make it cache content for all users in the world? Seriously