Consider a simple search problem with multiple paths. The main processing path can be computed in series as required functionality is identified. Completion occurs whenever an adequate solution is found. Alternatively, potential paths can be searched in batches or all simultaneously ahead of time**. This diminishes the wait for required functionality at the cost of additional processing, some of which may never be necessary. We trade computation power for statistically lower execution time.
Tag: ruby
How I cleaned up my music collection with 22 lines of ruby
*update* I added the music sort files to a github repo: http://github.com/victusfate/music-sort
Fat Guy in a little coat, Ruby on Windows
There’s just too much awesome in Ruby for a clean windows install and development environment.
Welcome to Ruby, Javascript and Ubuntu Linux Ben
Each Time I Get My Hands Dirty, I Learn
As long as I’m unwilling to face an obstacle, my mind invents clever schemes to prevent me from having to deal with undesirable tasks. That results in me treating the obstacle as a spooky animal. It also means I will miss out on any advantages of understanding the taboo subject.
Practical First Rails Threading Example
Getting a Handle On Threads
Yesterday I wrote briefly about threading in Ruby. Ruby threads don’t natively take advantage of multiple processors or cores (this may have changed), but they’re a great way to lower wait time on concurrent external delays. This is a non-blocking solution to initiating several API calls simultaneously, and greatly reduces delay, an imperative requirement to web services. (more…)
Ensure All Roads Lead to Your Goal (+ Ruby Threads)
Walking down the tracks with Ruby on Rails
this is a follow on post to Pigs may not have wings, but I can Ride the Rails with a flu
Gems Gems Gems
The first barrier to entry to ramping up on RoR (Ruby on Rails) was setting up a build environment. I found several windows friendly developmet options. Netbeans has an install. Steel Ruby has a visual studio variant, Instant Ruby creates an environment you can drop rails projects into (instantly 
), and Ruby Forge has an executable for windows machines. I opted for the Ruby Forge windows exec after trying the other routes to varying degrees of success. Primarily because it almost works (there’s no shuffle! Array function on the RoR Ruby Forge version, or my environment still has problems), it’s command line driven, and I know where the common install/gem folder is.
