Start learning from Ruby or directly from Rails.

瀏覽次數:55 次
跳到第一則未讀訊息

Rubyist Rohit

未讀,
2012年7月31日 下午1:40:492012/7/31
收件者:rubyonra...@googlegroups.com
I want to build a small GUI application that makes sense and not just a
Hello World application. I tried wxRuby, FxRuby and other libraries but
all seem to complicate things.

How to learn basics of Ruby and make learning interesting? How you all
started with Ruby? Whether Ruby first or Rails first?

--
Posted via http://www.ruby-forum.com/.

Douglas Lovell

未讀,
2012年7月31日 下午4:08:272012/7/31
收件者:rubyonra...@googlegroups.com
I personally started with Ruby first. I like the books from The
Pragmatic Bookshelf. (pragprog.com)

Douglas Lovell
www.wbreeze.com

sameera

未讀,
2012年8月1日 清晨5:22:092012/8/1
收件者:rubyonra...@googlegroups.com

My personal view is, and what actually I did is learning rails first. I think its a good way of starting, because you can create a basic rails application with no time and that make you feel comfortable and confidence. But then start learning how this rails works, and start learning ruby..

Then sooner you will realise rails is not magic it pure ruby

So my advice (my personal)

1 - start developing a basic application in rails
     get your self some thing working, be happy be confident

2 - start learning ruby
   
     you will understand the magic behind rails

;D

cheers

sameera

Gintautas Šimkus

未讀,
2012年8月1日 清晨7:50:182012/8/1
收件者:rubyonra...@googlegroups.com
I started with Rails. Though I had some strong foundations in OOP and programming principles in general when diving into RoR.

And I found out that I agree with the idea that you don't need pure Ruby knowledge beforehand to learn Rails fast and effectively. Pure ruby will come into play when you need to code more advanced stuff. You will have decent knowledge of Ruby if you are good at Rails. It just comes naturally, because not everything that is needed FOR Rails app is written IN RoR - sometimes, it's just pure ruby.

IMO, just pick one of the better beginner/tutorial books that advertise "Ruby on rails for beginners", and keep checking the API documentation for both Ruby and RoR when you stumble upon something you don't understand. This way you will learn what you need to do things at hand fast, and the knowledge will build up eventually, for both RoR and Ruby.

I advocate this way also because Ruby is far more general than RoR. RoR is pretty much about Web or anything involving browser, while pure Ruby can be used as sysadmin language of choice. I think you see where I am going with this: it's better to learn the stuff that you are going to work with/on (i.e. RoR is far higher priority than Ruby when starting out).

2012/8/1 sameera <samee...@gmail.com>
--
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 rubyonra...@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-ta...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/1NuDrPAWMmsJ.

For more options, visit https://groups.google.com/groups/opt_out.
 
 



--
Pagarbiai,
Gintautas

Gintautas Šimkus

未讀,
2012年8月1日 上午8:04:222012/8/1
收件者:rubyonra...@googlegroups.com
To rephrase, when you learn RoR from a book aimed at beginners, you will get the (basic) Ruby knowledge necessary to make your Rails app work. While if you start with Ruby, you will not have any idea of MVC, views, templates, controllers, models etc. The focus will be a lot different than if you had been learning from Rails book. I think it's clear why starting with Rails would be more effective: you learn stuff that you need to advance further in Rails quicker, while at the same time you are free to deeper your knowledge about a Symbol further on your own, with the help of google or whatever.

And what if you miss how Enumerable#each_with_index works, you just check that on the internet, and carry on building your shopping cart ;)

2012/8/1 Gintautas Šimkus <dihi...@gmail.com>



--
Pagarbiai,
Gintautas

captdowner

未讀,
2012年8月1日 上午10:08:512012/8/1
收件者:Ruby on Rails: Talk
> > How to learn basics of Ruby and make learning interesting? How you all
> > started with Ruby? Whether Ruby first or Rails first?
> >
> I personally started with Ruby first. I like the books from The
> Pragmatic Bookshelf. (pragprog.com)

Ruby first. Rails is a great tool for quickly generating crud web
interfaces and dealing with databases (and so much more). But, what it
outputs is Ruby code, and if you understand ruby, you will understand
much of the magic that is Rails.

Better yet, you'll be in a position to modify and extend the code that
Rails generates to better suit the task at hand and gain a better
understanding of things like 'method_missing' which is responsible for
much of the magic behind the Rails curtain.

Feel free to check out http://RubyTalkTips.com. It's an open source
website for Ruby showing what I have considered to be some of the best
ruby language tips over the past few years from the Ruby Talk mailing
list.

-- Steve Downie
________________________________________________
aka Capt. Downer
Sea of Anarchy Yacht Club
http://rubytalktips.com
email: captd...@gmail.com

Rubyist Rohit

未讀,
2012年8月1日 下午2:31:322012/8/1
收件者:rubyonra...@googlegroups.com
@Steve:

Learning Ruby alone is difficult. As I said, if I can't quickly design a
GUI and make a small application with sense, the rest of the journey is
boring.

I'll check RubyTalkTips.com

...........
Rohit.

> Ruby first. Rails is a great tool for quickly generating crud web
> interfaces and dealing with databases (and so much more). But, what it
> outputs is Ruby code, and if you understand ruby, you will understand
> much of the magic that is Rails.
>
> Better yet, you'll be in a position to modify and extend the code that
> Rails generates to better suit the task at hand and gain a better
> understanding of things like 'method_missing' which is responsible for
> much of the magic behind the Rails curtain.
>
> Feel free to check out http://RubyTalkTips.com. It's an open source
> website for Ruby showing what I have considered to be some of the best
> ruby language tips over the past few years from the Ruby Talk mailing
> list.
>
> -- Steve Downie

thil

未讀,
2012年8月2日 清晨7:58:422012/8/2
收件者:rubyonra...@googlegroups.com
Hi ,

My learning curve in ruby and rails is in progressing.

 1. First learn Ruby basic things like iterations, looping , class and objects and then
 2. Start jump into the Rails.  

Ruby my favorite book is Programming Ruby by "Dave Thomas" which is currently following really good one.
for Rails I have searched lot but finally decided http://guides.rubyonrails.org/ is  best and Dave Thomas book "Agile Web development  with rails"

If you have anything interest pls post

Thanks,
Senthil Srinivasan

Capt. Downer

未讀,
2012年7月31日 下午6:51:232012/7/31
收件者:rubyonra...@googlegroups.com
> > How to learn basics of Ruby and make learning interesting? How you all
> > started with Ruby? Whether Ruby first or Rails first?
> >
> I personally started with Ruby first. I like the books from The
> Pragmatic Bookshelf. (pragprog.com)

Ruby first. Rails is a great tool for quickly generating crud web interfaces and dealing with databases (and so much more). But, what it outputs is Ruby code, and if you understand ruby, you will understand much of the magic that is Rails.

Better yet, you'll be in a position to modify and extend the code that Rails generates to better suit the task at hand and gain a better understanding of things like 'method_missing' which is responsible for much of the magic behind the Rails curtain.

Feel free to check out http://RubyTalkTips.com. It's an open source website for Ruby showing what I have considered to be some of the best ruby language tips over the past few years from the Ruby Talk mailing list.

-- Steve Downie
回覆所有人
回覆作者
轉寄
0 則新訊息