Live data from Hacker News

New to Ruby? Tips for the new Rubyist.

jasimabasheer.com

41–50 of 65 posts

Re: New to Ruby? Tips for the new Rubyist.

#41

I'm in the middle of picking up Ruby primarily because there was a GitHub project I wanted to fork and modify for my purposes that happened to be written in Ruby.The biggest problem I found is that the Ruby (or maybe the Rails?) community by and large provides shit instructions on how to get something running. I checked out a handful of projects and they all said things like, "Just deploy the normal what you deploy a…

I think the genesis if this problem is due mostly to the fact that programmers from a PHP background are used to not thinking about their server stack. That is changing though. In languages like PHP, it's possible (again, this is becoming less common) to run an ad-hoc PHP application by simply requesting the URL to the file. For example: * Drop myapp.php in to your httpd doc root * Request http://myserver.tld/myapp.p…

Alternatively, I have almost no web experience and come from an embedded consumer electronics background. Similar problem... :)

Re: New to Ruby? Tips for the new Rubyist.

#42
post #4

I would like to get some advice from experienced Ruby hackers. Currently I am picking up Ruby through rails, which I am assuming is fairly common. I want to know the downsides to this and what people did to supplement their ruby knowledge beyond Rails. I eventually would like to write my own gems, contribute to open source, and so forth. I am absolutely not satisfied with just consuming Rails.

Probably the biggest downside is that you'll incorrectly assume that some parts of Rails are actually part of Ruby. Then you'll miss them when they're not there and possibly feel a small amount of sadness. Oh the humanity! :) The big one is ActiveSupport. There are many extensions to common Ruby objects like String, Enumerable, Hash, etc. For example. In Rails, you'll use something like this quite frequently: some_st…

Thanks. I was expecting somebody to mention this. What I am currently doing is investigating most of the code I use, be it methods, classes, and so on. It takes me off of the main task, but I think based on what you experienced its a good thing. I have a folder for rails source code in my editor and I usually just hang out there. ;) Hopefully this will mitigate the problem.

Re: New to Ruby? Tips for the new Rubyist.

#43
post #21

OT and hijacking this thread: 1. Who is actually new to Ruby? (After Ruby or rather the popular RoR is there almost for a decade everyone should have made some experiences with Ruby, so I am wondering if there are many new Rubiest) 2. What new language/stack did you start to learn recently? (for me: Node.js)

That was narrow minded. You know it's possible to be a developer and never touch a web app stack professionally, right? Let alone the One True Language that is Ruby.

Re: New to Ruby? Tips for the new Rubyist.

#44
post #21

OT and hijacking this thread: 1. Who is actually new to Ruby? (After Ruby or rather the popular RoR is there almost for a decade everyone should have made some experiences with Ruby, so I am wondering if there are many new Rubiest) 2. What new language/stack did you start to learn recently? (for me: Node.js)

As a Python guy I never had any reason to need to learn Ruby. And even now that I'm playing around with it it's purely out of professional curiosity.

For what it's worth, Ruby has always been more about "want" than "need" for me. When I really need to get something done, fast, I'll choose Python; Python always seems to have an esoteric-but-very-necessary lib for every situation. But Ruby is where I want to spend my fun time.

Opinions will differ, of course. Both languages are tops.

Re: New to Ruby? Tips for the new Rubyist.

#45
I think it's wrong to judge Zed's Learn Ruby the Hard Way too harshly as the OP does...yes, it's a straight port from the Python version, but both versions focus on teaching programming to non-programmers, which is a concept that can be largely language and idiom agnostic...at least between Python and Ruby.

Re: New to Ruby? Tips for the new Rubyist.

#46
post #4

I would like to get some advice from experienced Ruby hackers. Currently I am picking up Ruby through rails, which I am assuming is fairly common. I want to know the downsides to this and what people did to supplement their ruby knowledge beyond Rails. I eventually would like to write my own gems, contribute to open source, and so forth. I am absolutely not satisfied with just consuming Rails.

I'd recommend reading Eloquent Ruby by Russ Olsen. It's a great after-Rails intro to Ruby and uses a lot of specific examples from the framework to highlight how Ruby features make some of the magic happen in Rails.

I wonder if this can be read hand in hand with Ruby Best Practices. After all Matz wrote the preface to this one so I have to give it a go.

Re: New to Ruby? Tips for the new Rubyist.

#47
post #4

I would like to get some advice from experienced Ruby hackers. Currently I am picking up Ruby through rails, which I am assuming is fairly common. I want to know the downsides to this and what people did to supplement their ruby knowledge beyond Rails. I eventually would like to write my own gems, contribute to open source, and so forth. I am absolutely not satisfied with just consuming Rails.

Read everything from Gregory Brown.

Re: New to Ruby? Tips for the new Rubyist.

#48

I'm in the middle of picking up Ruby primarily because there was a GitHub project I wanted to fork and modify for my purposes that happened to be written in Ruby.The biggest problem I found is that the Ruby (or maybe the Rails?) community by and large provides shit instructions on how to get something running. I checked out a handful of projects and they all said things like, "Just deploy the normal what you deploy a…

I think the genesis if this problem is due mostly to the fact that programmers from a PHP background are used to not thinking about their server stack. That is changing though. In languages like PHP, it's possible (again, this is becoming less common) to run an ad-hoc PHP application by simply requesting the URL to the file. For example: * Drop myapp.php in to your httpd doc root * Request http://myserver.tld/myapp.p…

Are you saying Java deployment is complex? WAR files have been easiest to hot deploy for at least a decade - that too directly from your IDE with the click of a button. PHP deployment simplicity definitely beats everything - and Ruby will come last :(

Re: New to Ruby? Tips for the new Rubyist.

#50
post #48

Earlier quoted context omitted.

I think the genesis if this problem is due mostly to the fact that programmers from a PHP background are used to not thinking about their server stack. That is changing though. In languages like PHP, it's possible (again, this is becoming less common) to run an ad-hoc PHP application by simply requesting the URL to the file. For example: * Drop myapp.php in to your httpd doc root * Request http://myserver.tld/myapp.p…

Are you saying Java deployment is complex? WAR files have been easiest to hot deploy for at least a decade - that too directly from your IDE with the click of a button. PHP deployment simplicity definitely beats everything - and Ruby will come last :(

If you don't want too much infrastructure complexity in Java - go for Tomcat or Jetty - If you want advanced enterprise functionality go for JBOSS or another J2EE server. If you want asynchronous io, go for netty. Javaland is full of options that offer best performance.
Post reply on HN