ryanbigg

9 ms·

61.
by ryanbigg 15y ago
I strongly disagree with the purpose of this. It still has precisely the same problem that regular git has: you need to understand the language behind it. Just learn regular Git rather than re-inventing the language.
62.
by ryanbigg 15y ago
To make it "easier" for people to use their engine. Obviously this is wrong.
63.
by ryanbigg 15y ago
Yup, nobody's writing Rails apps anymore. ahem Basecamp Next, Living Social, Groupon, Caring.com, GitHub, Shopify, Scribd, Ravelry, Harvest. Just to name a few that are still growing. I don't think you could've posted a more flamebait p
64.
by ryanbigg 15y ago
Agreed here. While it would satisfy the curiosity of people, it is not really all that relevant how he died, just that he is now dead. There are rumors, but there's no point talking about them because there's no facts behind them. You may a
65.
by ryanbigg 15y ago
Could you elaborate?
66.
Live Coding Screencast - Game of Life in Ruby(ryanbigg.com)
2 points by ryanbigg 15y ago|0 comments
67.
by ryanbigg 15y ago
I am not quite sure. Maybe Manning gave them to Amazon at a certain price and Amazon chooses which price they want to sell at? I have no idea.
68.
by ryanbigg 15y ago
I wrote a book called "Rails 3 in Action" for getting started with Rails. Obligatory link: http://manning.com/katz The idea behind it was to have more focus on BDD than anything else out there, which is exactly what the community is all a
69.
by ryanbigg 15y ago
I would do the same thing, as Test::Unit's syntax is more confusing to a newbie than RSpec. For instance: assert_equal 2, @thing.method vs @thing.method.should == 2. RSpec is also used by the majority of Rails developers (based on a random
70.
by ryanbigg 15y ago
While I can't answer #1, I can give a reason for #2. When you're teaching people Ruby on Rails you would/should be teaching them what exists in the framework by default. The default templating language for views happens to be ERB-powered HT
71.
by ryanbigg 15y ago
Thanks for linking to the new Asset Pipeline guide. Richard Hulse, Mohammed El-Abid and me put a lot of work into that to try to help people understand how it works. It's just a fantastic feeling to see something that I've worked on be help
72.
by ryanbigg 15y ago
I disagree. We have this as the !ask command in #Rubyonrails for when somebody asks to ask. It really improves the kind of questions that people would ask if you first ask them to read it. You can't just expect people to chance across golde
73.
Hipster Ipsum(hipsteripsum.me)
13 points by ryanbigg 15y ago|3 comments
74.
by ryanbigg 15y ago
You are contrasting the versions incorrectly. Rails 3.0 may have been released then but the latest version of it is Rails 3.0.9, which was released < 1 month ago.
75.
by ryanbigg 15y ago
I second the advice about setting up an Ubuntu machine. Windows is unnecessarily painful for development in comparison. Although there are "workarounds" around the problem, you'll find things much easier for development on an Ubuntu or Mac
76.
by ryanbigg 15y ago
What struck me the most in that lawsuit (which I haven't yet finished reading, but seems pretty compelling) is: "Bedier transferred up-to-date versions of documents outlining PayPal's mobile payment and point of sale strategies to his non-P
77.
by ryanbigg 16y ago
No Australian cities? Boo ;)
78.
by ryanbigg 16y ago
Rails 3.0.5 did nothing wrong. The correct code for this: namespace :products do resources :comments do member do get :like end end end Using a `get` without a `member` block leads to the m
79.
by ryanbigg 16y ago
And if you could elaborate on those "dozens of problems" then we would be most accepting. Broad, overarching statements aren't beginner friendly.
80.
by ryanbigg 16y ago
It's not too often that you'll have a server that runs two applications. Sure, if that were the case then you would be using RVM in which case I would recommend following the guide already linked. But if you've got one application running o
81.
by ryanbigg 16y ago
I'm glad you found it useful, but yes it was already posted back in December.
82.
Why Pivotal charging for Tracker is a Good Thing(ryanbigg.com)
2 points by ryanbigg 16y ago|0 comments
83.
Why you should run bundle update(ryanbigg.com)
2 points by ryanbigg 16y ago|0 comments
84.
by ryanbigg 16y ago
Honestly, the setup isn't that complicated that it should take anybody who's following any kind of instructions any time at all. Even compiling from source is pretty straight forward... although there's a couple of "mystery packages" like l
85.
by ryanbigg 16y ago
Additionally, apt also packages "ruby-1.9.1" which actually installs Ruby 1.9.2. More evidence that apt is fundamentally broken when it comes to Ruby package management.
86.
by ryanbigg 16y ago
Could you explain how these instructions would give you a "headache fast"?
87.
by ryanbigg 16y ago
Ruby 1.9.2 and Rails 3.0.3 are now considered stable by what appears to be everyone but the packagers. apt installs Ruby using a non-standard configuration too, when you do `apt-get install ruby1.8`, the executable is `ruby1.8`. Nobody in t
88.
Advanced Rails Documentation(ryanbigg.com)
2 points by ryanbigg 16y ago|0 comments
89.
by ryanbigg 16y ago
Knowing when to stop. When you reach a seemingly impassable problem, talking it over with other people and then sleeping on it will make everything clearer come morning. If you work constantly you are a worse programmer than those who know
90.
by ryanbigg 16y ago
+1 Ruby

More ›