GitHub has been working on a re-architecture since our last major feature release, which was GitHub Issues in April.
And we can't wait to roll it out.
1,349 karma · joined July 9, 2008
GitHub has been working on a re-architecture since our last major feature release, which was GitHub Issues in April.
And we can't wait to roll it out.
This is about the best way to use Rubygems. Check out Josh Peek's recent article: http://weblog.rubyonrails.org/2009/9/1/gem-packaging-best-pr...
There are ways to use Rubygems without putting "require 'rubygems'" in your code. Those are the correct, most portable, least painful ways of using Rubygems. Learn them and cherish them!
That is what this is about: how you are using Rubygems, not whether or not to use them.
$ macirb
>> ''.class
=> NSMutableString
MacRuby is Obj-C! Of course, this works both ways: some stdlib stuff is currently less reliable than using the Cocoa framework equivalent.Either way they're making really awesome progress and it's an exciting project to watch.
Bundler: http://github.com/wycats/bundler
Rip: http://hellorip.com/
So is Rails core member Yehuda Katz.
So is Rails core member Josh Peek.
So is Rails core member Jeremy Kemper.
Calling Ryan "the extreme odd one out" is a) untrue and b) unfair.
One of the libraries is going to break.
try was originally defined as:
class Object
def try(method)
send method if respond_to? method
end
end
In Rails it is defined as: class Object
alias_method :try, :__send__
end
class NilClass
def try(*args)
nil
end
end
The following code will exhibit different behavior depending on which version of try you're using: [].try :upcase
For example: # original try
>> [].try :upcase
=> nil
# rails try
>> [].try :upcase
NoMethodError: undefined method `upcase' for []:Array
If Rails uses try internally, and a Rails plugin you've loaded depends on the original version of try, what now? They both behave differently and, presumably, code using them depends on their specific behavior.Also don't forget the dozen or so other versions of try people have added to their own plugins and apps...
But I still think you're right: this is a book for people who buy business books in airports and read them on planes. Which is where 37s probably needs to be heading - my dad wears a suit to work and has never heard of them, but I think he'd get excited by some of their ideas.
"Camping is magic, plus some other stuff."
(camping is an anagram of magicnp)
This is a sad day.
I may just start playing with it again. Thanks for responding.
It'll make you a better Python programmer for sure.
I found it much easier to learn on the second try. On the first try I was learning about syntax, functions, loops, variables, and types as well as memory management, header files, and pointers. On the second try I was only learning about memory management, header files, and pointers - I already knew about the other stuff. On top of that, pointers were much easier to grasp because I had experience with 'references' in higher level languages.
It's great to learn C, but I always recommend people learn to program by way of something like Python or Ruby. It's hard to beat print "hello" when you're just starting out.
mojombo has a background working with distributed systems (at Powerset) as well as in design (he freelanced for a few years). Which means he's our main UI / design person as well as the guy overseeing the "big picture" backend stuff. For instance, right now we're in the process of sharding all of our git repository data to get away from our network file system bottleneck. mojombo's leading that project and it's going great - we should see the plans come to fruition in the near future. He's also the guy that makes changes to the git-daemons and other sysadminy stuff.
pjhyett, one of the other founders, is a seasoned web developer with experience in (among other things) Java and Rails. Which made him the ideal head of our Firewall Install product (since it uses JRuby). He's currently on a trip to NYC to meet with potential FI clients, and is in charge of adding features to it, fixing bugs, basically lording over the product.
schacon isn't technically a founder, but we're a very flat (and small) organization. He's a Git expert so we deploy him on any and all things Git: weird server errors, crazy new projects (like the Fork Queue and Gist), and our issues scaling Git itself. He's currently experimenting with a Cassandra-backed git-daemon to help speed up clones (specifically the "Counting objects" / building packfile phase) and give us the ability to easily put mirrors in other continents.
Tekkub is our customer support expert: he hangs out in irc, on the mailing list, and oversees the help site. He has programming background (we found him because of all his Lua stuff on GitHub) which means he can write his own tools and knows Git very well.
I'm the third founder. I mostly hang out here.