I agree also. It seems that there are also overlapping issues that go together with Rails programming. I would like to be able to be great at Ruby programming too. I picked up a book on “Scripting Intelligence” and while the author speaks of doing things in Rails, there is so much Ruby programming in the text.
On wikipedia Drupal is in the same classification as Ruby, as a “framework.” Not sure if it fits but I find myself getting ignored in my requests there. I have to admit that I don’t have that experience here. I do seem to get responses to my questions – even when I annoy others with my naiveté. This could be a topic in itself but anyway, I bought that book the Rails Tutorial. It struck me as somewhat overwhelming the programming in Rails can be. For example, in section 1.2 of the tutorial, the author writes, “(Also beware that lots of things can go wrong. For example, on my system the latest version of Ruby 1.8.7 won’t compile; instead after much searching and hand-wringing, I discovered that I needed ‘patchlevel’ number 174: $ rvm install 1.8.7-p174 When things like this happen to you, it’s always frustrating, but at least you know that it happens to everyone...)” Ok, the problem is that the author didn’t say how he determined what patchlevel he needed... So, I had mixed feelings... on the one hand there is the consolation in knowing that the difficulty one is having just getting started is not a unique experience for you coming to RoR. On the other hand, this is extremely daunting for a newbie to Rails. With other languages, usually backwards compatibility is maintained for a certain period of time. For example, you can run PHP 4.x.y on a system with PHP 5.3.x but not necessarily the other way around. As a matter of fact, I’m not aware of any other language I’ve used that had anywhere near the level of potential things that could go wrong. I don’t mean to discredit RoR but to see how one can get a handle on this issue. I wonder why one would need such a specific version of Ruby? In my case it was only Rails that created any kind of problem. Ruby was easy enough to get up and running. Bruce From: Ashokkumar Yuvarajan Sent: Wednesday, September 5, 2012 6:43 AM To: [email protected] Subject: Re: [Rails] I wanna make a new rails community :) I agree.. Am Ashokkumar, RoR developer. I started rails programming for my past 4months. I think we both are the right pair to start learning. All is well !! On Tue, Sep 4, 2012 at 7:03 AM, Tima <[email protected]> wrote: Hi everyone! I'm a newbie engineer. I started rails programming, but I'm learning alone and can't understand other rails cord so much. So I wanna have friend with other newbie rails engineers and share a process of making apps. It is not for sharing the "result" of programming like Github, but for recording the almost all of process of making one app. It'll not be so profitable for expert rails player, but good for beginners who haven't make so much apps. If some of you agree with this theme, please post on this board. regards Tima -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to mailto:rubyonrails-talk%[email protected]. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/y8UkerpvdOcJ. For more options, visit https://groups.google.com/groups/opt_out. -- "Attitude is a little thing that makes a big difference" Thanks & Regards Ashokkumar.Y ROR-Developer email : [email protected] -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
