Ruby Inside

Not much in this review. This review of the book was more insightful: http://www.rubyinside.com/a-review-of-eloquent-ruby-by-russ-olsen-it-r…

http://rubyinside.com http://railscasts.com http://ruby-toolbox.com http://railstutorial.org

http://ruby.alltop.com/ http://www.rubyflow.com/ http://www.rubyinside.com/ http://seriouslyruby.com/

I just deployed to a large instance on one of these and it was fantastic. I'd been on RedHat before, so I had a slight learning curve to the Ubuntu/Debian ways, but it's a great AMI. Add in a Sprinkle script* to deploy a full Rails/MySql/Passenger stack and I moved a well trafficked production server from Nginx/Mongrel in just a few hours. *http://www.rubyinside.com/passenger-stack-quickly-install-a-full-ruby-…

I did a quick browse through the threads in question and suggest others do the same. Yes, there is negativity, but the actual debate is more complex than simply one grumpy side slamming a poor developer. The most relevant comment I found was by /u/bixmix: > It's getting much worse - not better. The internal churn within pip also is not community driven as much as it is developer driven. It's like we didn't learn from the debacle of python3 vs 2. I'm not a Pythonist so I had no idea there was such a huge debate over how to manage deps. At various points the past few years I've googled "bundler for python" and come up with different projects. I remember trying pipenv early on (didn't work with conda Python install). Then I revisited it months later--the project was much more developed--and it worked great. FWIW I like pipenv, it solves my largest gripe with Python development. If you have as part of your community philosophy "there should be one—and preferably only one—obvious way to do it," it seems like you're going get a lot of stubborn tug-of-war situations (see 2 vs 3) where each side thinks their way is the superior way and there is less room to compromise for the sake of keeping the community together. That said, this pattern of debate is pretty universal across communities. Ruby--even with it's MINASWAN motto--had it's own RVM vs rebenv drama back in 2011. Same sort of developer/community vs developer/community drama. Nowadays I think rbenv has a larger…

Yes there is. Check out http://www.rubyinside.com/

I was the curator and co-organizer of RubyFringe and FutureRuby in Toronto. I'm really sorry to hear that folks organizing BRC felt so beat down by negativity that cancelation was the best option. Most people simply do not appreciate the hundreds of unpaid hours of work that are required to pull off a good event. Several aspects of this controversy don't sit well with me, however. First off, since when does the curation of a conference have to follow someone else's value system? It's very simple: the people that organize an event should work hard to put together the most interesting line-up they can. It's then up to the potential attendees to decide if the event is worth their time to attend. That's it; there are no more rules! If you want to solicit proposals for talks, go ahead. If you like some of them, give them a shot at speaking. If you decide that none of them match your curatorial agenda, then thank them warmly for their submission and move on. You aren't obligated to take proposals at all, and you're certainly not obligated to make your decision process transparent or part of some laborious community democracy. In fact, I would guess that one strongly opinionated curator will put together a far more coherent line-up than any popularity contest ever could. If you're looking for inspiration, consider asking attendees from previous years if they'd like to consider "leveling-up" to speaker. When I put together our speaker lists, it wasn't arbitrary and much like test…

I absolutely love Lisp, but I'm not in the least bit offended at someone describing some aspects of the culture as cultish. But the thing is.. the very same thing could be said of most other language enthusiasts. Look at all the endless hype from Python and Ruby fans (especially when they compare their favorite language to Perl). Or look at some OCaml or Haskell fanboys and their attitude that static typing is The True Way and only ignorant savages would prefer a dynamically typed language. And this doesn't even touch on the vi vs Emacs holy wars. There's plenty of fanboyishness, exclusivity, and and chastisement of outsiders in many computer fields. And I dare say it's not really limited to computers either. I'm not sure if "cultish" is really the most appropriate term, but I feel no offense at it. The whole discussion reminds me of these images: http://www.deimeke.net/dirk/blog/uploads/G7WyP.gif http://www.rubyinside.com/holiday-fun-how-programming-language-fanboys…

I do agree with shooter that python is good technologically... but the problem with Python web frameworks is that there's no one official framework yet for python that's overwhelmingly popular in the python world (though someone can prove me wrong). The end result is that there aren't that many books on stuff like Django (compared to other technologies), which really sucks when you're just starting out. Rails on the other hand has tons and tons of books. I just started a little less than a year ago and I've caught up fast because of the plethora of books and communities for Rails. in the end, if you happen to find your partner quick - they may help you choose (that's probably the best route) Forgot to mention - check out some video tutorials of Rails programming: http://rubyonrails.com/screencasts http://railscasts.com http://peepcode.com (not free but really really good - they actually have 2 vids that covers all of the basics of Rails - in I think about 3-5 hours; you're not goign to remember all of it in the 1st run but it gets u comfy) a decent list of resources http://railshandbook.com/ http://rubyinside.com http://dzone.com http://poignantguide.net/ruby/ -funny and useful intro into ruby itself

I'm not sure if you're joking or just not familiar with _why, but his book on Ruby is probably his most famous writing: http://www.rubyinside.com/media/poignant-guide.pdf or http://poignant.guide/ It's an incredible work. Ruby is the spiritual successor to Perl, and the niche it filled was to be the "beautiful" programming language. If you don't appreciate _why's guide and the idea of code as magical incantations, you're not going to enjoy your Ruby experience. I don't think there's many rubyists that didn't appreciate _why. With something as weird as Ruby, where there's so many ways to do everything, you're going to want to start with beginner's mind anyway.

I'm a bit confused by the terminology here. I thought "autoloading" referred to deferring the loading of a constant until it is first used (as described in this post[0]). But the author seems to be talking about loading code without an "import/use/require" statement. Are those two different meanings for "autoloading"? Or do the two go together in Ruby? (As is probably obvious, I'm not a Ruby dev) [0]: http://www.rubyinside.com/ruby-techniques-revealed-autoload-1652.html

The core dev having worked on new GIL (py3.2) explained this to me. I never said it was magic. But he said GIL is a tool to achieve thread-safety in python when calling non 'thread safe' code. I am not him, I will not take on any argument of how it works. But since ruby GIL is inspired by python GIL let's hear ruby coders: http://www.rubyinside.com/does-the-gil-make-your-ruby-code-thread-safe… Oh, yes, it seems some people are seeing it my way and that it is a controversial point that can be argued. So I agree to disagree. Btw, I don't multithread and share states, I multiprocess with 0MQ and communication patterns such as PUB/SUB PUSH/PULL for the obvious reasons that I really think multi-threading is an over-valued and wrong abstraction.

FWIW, the first submitter of this post seems to be Jeremy Ashkenas, who was the creator of CoffeeScript: https://news.ycombinator.com/item?id=3128166 Even if you're being half-facetious...while CoffeeScript seems to have fallen in favor with the onset of ES6, it's hard to overstate its influence in 2011...Rails, which was most definitely the hott framework du jour, decided to make CoffeeScript -- along with the much more ubiquitous jQuery and SASS -- part of its default stack: http://www.rubyinside.com/rails-3-1-adopts-coffeescript-jquery-sass-an…

Rubyforge.org was a 'central repository of gems' in name only. The transition to gemcutter, which turned into today's rubygems, happened in 2009: http://www.rubyinside.com/gemcutter-is-the-new-official-default-rubyge…

If you like this sort of thing, you might like this piece I wrote some time back about writing a Ruby script using whitespace for all identifiers: http://www.rubyinside.com/the-split-is-not-enough-whitespace-shenigans…

Pay attention when using the Rails logo: http://www.rubyinside.com/david-heinemeier-hansson-says-no-to-use-of-r…

It's probably fake-factory to prevent confusion with the Ruby gem that's been around for more than 6 years http://www.rubyinside.com/faker-quick-fake-data-generation-in-ruby-665… It's a standard gem in the community and it's used for generating various types of seed database data. Don't know if does the exact same things that the Python faker does.

Yet this is what Ruby does, AFAIK. Numeric#days is an ActiveSupport method, not core Ruby. But yes, it does patch the behaviour into a core class. This is a bit of a legacy of Ruby programming, and it's definitely bad to pollute the global namespace. However, I expect we'll see eventual use of Refinements (http://www.rubyinside.com/ruby-refinements-an-overview-of-a-new-propos… now that they are available; this will allow classes to override core methods without affecting other classes out of scope.

Oddly enough that was done years ago via Silverlight of all things. http://www.rubyinside.com/ironruby-silverlight-ruby-in-browser-3192.ht…

I've found application boot time to be a pain point if you're running your tests frequently - I run mine several times a minute. For Ruby/Rails developers it's been especially bad, especially in JRuby. Some major patches have been made to Ruby(MRI) recently to help make this less of a problem: http://www.rubyinside.com/ruby-1-9-3-faster-loading-times-require-4927… http://blog.tddium.com/2012/11/20/profiling-ruby/

I'm guessing he had in mind this (very controversial) feature that was proposed for Ruby 2.0 and then scaled back: http://www.rubyinside.com/ruby-refinements-an-overview-of-a-new-propos…

>I am dreading the technical debt I have in test-unit, and meanwhile the (Rails) world is moving on to Minitest Minitest and Test::Unit are part of the same package since 1.9, with Test::Unit implemented as a simple compatibility layer on top of Minitest: http://www.rubyinside.com/a-minitestspec-tutorial-elegant-spec-style-t… The Minitest assertions are quite similar to the old Test::Unit assertions, a large number are identical: http://rubydoc.info/stdlib/minitest/1.9.3/MiniTest/Assertions

Use Ripper in 1.9.3. It's part of the distribution and it works well. http://www.rubyinside.com/using-ripper-to-see-how-ruby-is-parsing-your… https://gist.github.com/michaelfeathers/4704833

I'm not sure I fully understand what you mean by "code sample from these languages", but Ruby's source has plenty of code contributed from all over the world https://github.com/ruby/ruby If you're talking about code written in non-English languages, Peter Cooper has a fun article about writing Ruby code in UTF-8: http://www.rubyinside.com/the-split-is-not-enough-whitespace-shenigans…

http://www.rubyinside.com/ruby-iso-spec-draft-2900.html describes the reason behind the standardization. Seems it's more about allowing Ruby to be used in project dealing with the Japanese government than it is about insuring portability.

So did DHH give permission to use the Rails logo for this project????? "The use of the logo is restricted as it always is when talking about a trademark. When the logo is used in a commercial setting, such as part of the promotion of a book, it legally requires that the trademark holder has been involved and stands behind the quality of the book. If that's not the case, you're on the way to lose your trademark. So I only grant promotional use for products I'm directly involved with. Such as books that I've been part of the development process for or conferences where I have a say in the execution." http://www.rubyinside.com/david-heinemeier-hansson-says-no-to-use-of-r…

I found hijack on your blog: http://www.rubyinside.com/hijack-get-a-live-irb-prompt-for-any-existin… This ranks higher than the github repo while searching for "ruby attach running process." hnsearch showed the same article being submitted about 2 years ago, with not much interest showed. I was a bit surprised. I was searching for HN thread as I was expecting some useful discussion, but found none. I assumed this is the kind of topic which would interest HN crowd, but looks like that isn't the case.

Some languages make monkeypatching a lot less dangerous. For eg. in Perl you can use dynamic scoping to localise its effect: { no warnings 'redefine'; local *SomeModule::some_func = sub { say "MONKEYPATCHED!" }; # now everything in this scope that uses or calls SomeModule->some_func # will now use the monkeypatched version } # where has everything else outside this scope remains unaffected In Ruby Refinements earmarked for ruby 2.0 will have something similar: http://www.rubyinside.com/ruby-refinements-an-overview-of-a-new-propos…

> can't make a Ruby object falsy You can override ! (see http://www.rubyinside.com/rubys-unary-operators-and-how-to-redefine-th… from earlier this week) so !!obj can evaluate to false. But there is still this to solve: ruby-1.9.3-p0 :008 > obj ? true : false => true ruby-1.9.3-p0 :009 > If only there was a #to_bool to override... (For the record: yuck).