Live data from Hacker News

Modern Ruby Development

ascarter.net

31–40 of 56 posts

Re: Modern Ruby Development

#31

Interesting guide, one thing I find lacking in ruby is longevity in projects. Too much cool new stuff, why not just work out the bugs in the existing projects instead? Of course it's easier to write a new half-assed implementation than getting the hard last percent done. Interesting that he roots for homebrew over macports and rbenv over rvm while at the same time voting for capistrano. Of those 3 projects I find mac…

Capistrano is lacking, but has fewer good alternatives. What would you recommend over it?

I dunno, I've stuck with Capistrano... I've used Vlad, but Cap just works and it only needs to be as complicated as you make it. My cap files are usually about 40 lines total and that often includes a section where I write the database.yml on the fly to the server. I've used all the other options, and they're nice, but Cap works nicely still.

Re: Modern Ruby Development

#32
post #17

Interesting guide, one thing I find lacking in ruby is longevity in projects. Too much cool new stuff, why not just work out the bugs in the existing projects instead? Of course it's easier to write a new half-assed implementation than getting the hard last percent done. Interesting that he roots for homebrew over macports and rbenv over rvm while at the same time voting for capistrano. Of those 3 projects I find mac…

Too much cool new stuff, why not just work out the bugs in the existing projects instead? This may not be a popular opinion, but I have a suspicion that the high degree of wheel reinvention in the world of Ruby and Rails libraries is due to two things: NIH Syndrome & the professed preference by employers for people with active GitHub projects. This causes all kinds of people to make their own gems and such where exis…

I love that things change, and I love the almost competitive nature between projects, but it's grating if you maintiain existing things.

If you're a consultant hopping from one client gig to the next each few months, it's great. If you maintain your own things, it gets frustrating when things you relied on are no longer maintained because the developer got tired of putting up with putdowns about how his project "sucks" and [x] is the new hot way to log people in. :)

Re: Modern Ruby Development

#33

Personally, I don't understand the hype of rubyenv. I really love rvm. I'm not sure why the author called rvm a "mess of bash scripts". I guess because rvm has a lot of features? If I did not care for gemsets and all of the other niceties that rvm has, I guess I would be on the market for another ruby manager. The fact that the author of this article was rubbed the wrong way by Wayne and rvm, rubbed me the wrong way.

He probably called it a "mess of bash scripts" because, uh, it is a mess of bash scripts. Have you looked at the implementation? RVM is amazing in the functionality it has, don't get me wrong, but it hacks into your shell in some nasty ways and when things go wrong good luck figuring out why without diving deep into the underlying bash.

Re: Modern Ruby Development

#34
post #19

Earlier quoted context omitted.

Try RubyMine from JetBrains, a very slick product, and worth paying for (I don't pay for much but JetBrains IDEs I make an exception for). In true HN tradition, I must urge you to try Vim. I found this very helpful when I first start: http://yannesposito.com/Scratch/en/blog/Learn-Vim-Progressiv...

Sometime I don't understand people that use Vim for everything. I used Vim casually so I'm not an expert. I understand that it'll take a while to master it. But compare to netbeans where you can navigate Ruby code quite fast (shortcut to method implementation, class implementation, project browse, auto-suggest, etc), why would I want to use Vim when I have to find the proper plugins (not just one, but a few) before I…

I understand people who use VIm for everything. I've recently come ack to it after a few years away.

It's nice to have an editor you know how to be productive in when you start using a new tech.

In an average workday I'll touch ASP, JavaScript, Sass, CoffeeScript, PHP, and Ruby code. When I use VIm, I can use all of the shortcuts and things I've learned over the years to manipulate text. I know how to manage projects, find files, etc.

That's a huge advantage. Having to learn Eclipse to do Java or Visual Studio to do C# adds complexity cos you have to learn the tool and the language.

So yea, I totally get it. This goes for TextMate or Emacs too.

Re: Modern Ruby Development

#36
post #19

Earlier quoted context omitted.

i m moved to gedit and redcar from netbeans on ubuntu for any ruby development. on ubuntu does anyone have any recommendations?

Try RubyMine from JetBrains, a very slick product, and worth paying for (I don't pay for much but JetBrains IDEs I make an exception for). In true HN tradition, I must urge you to try Vim. I found this very helpful when I first start: http://yannesposito.com/Scratch/en/blog/Learn-Vim-Progressiv...

[deleted]

Re: Modern Ruby Development

#37

A huge flaw of Mac OS X is the lack of a proper package manager. Mac OS X does provide a package manager - the App Store.

I've been using macports for ages, nothing wrong with it. Okay, it does not check to see the stock installs of OSX, and installs its own ruby, perl, python etc. Apart from that it's been very reliable.

Re: Modern Ruby Development

#38
Software that lacks a good uninstaller is always suspect, to me. It makes me smile to know that this is all that's necessary to remove RVM:

  > rvm implode
How's rbenv for uninstallation? I'm familiar-enough with rvm that I know I can restore absolutely everything from scratch with a couple config options and a while for compilation - I'm more than happy to spend that to experiment as long as rbenv has a similar panic-button.

Re: Modern Ruby Development

#39

A huge flaw of Mac OS X is the lack of a proper package manager. Mac OS X does provide a package manager - the App Store.

I've been using macports for ages, nothing wrong with it. Okay, it does not check to see the stock installs of OSX, and installs its own ruby, perl, python etc. Apart from that it's been very reliable.

My main problem with macports has been that it occasionally does not play nicely with manual source-installs, or any other package manager. And damn near everything needs sudo.

Everything I've needed has been available in homebrew, and more up-to-date and better isolated and hasn't collided with anything yet. I haven't used it as long as I've used macports, but so far it has been a far more pleasant experience. And incomparably faster - I swear, macports has a sleep() call in every operation. Very much recommended if you haven't tried it, and it cleans up nicely too - you just delete its single folder.

Re: Modern Ruby Development

#40
This article tells me that i'm not modern because I don't use a Mac, I don't like zsh, I prefer Mercurial, and so on.

Why isn't it titled "My brand new Rails development stack on Mac"?

Post reply on HN