rails

Aaron Worsham / Oct 24, 2008

Ruby one-liners get answered

rubymegyarsh The guys over at Rails Envy, a Ruby on Rails enthusiast podcast, have a running joke. Their catch phrase? – ‘Rails can’t scale.’ Yeah, I wasn’t too sure I got the joke either. Then I heard it myself in CIO level discussions from smart business people parroting things they didn’t understand and read somewhere once in an article in a magazine bylined by a guy in a suit who looked corporate and trustworthy. Rational reasoning and discourse can sometimes be co opted by bumper-sticker wisdom even at the highest levels.

Here is the thing about corporations; enterprises are in the business of managing calculated risk within the market or industry they operate. They do this by forcing non-core operations to be conservative, risk-adverse and predictable. It’s a bit like hedging your business’s bet in the junk bond market (core business) by backing it with rock solid, non sexy T-Bills (non-core like software development). Sure, the return on the T-Bills is lousy but you know in three years you won’t be out that investment. Java, backed by Sun Microsystems, and .Net, backed by Microsoft, are some of the blue chip securities of the programming world. Enterprises trust them. One-liners like ‘Rails can’t scale’ are the one-handed brushoff of entrenched corporate IT’ers to the mere idea of using something new like Ruby or Rails.

Still, Ruby is a persistent pitch man, especially in the web technologies.

Corporate IT: Ruby uses green threads and Rails is single threaded, why are we even talking?

Ruby: Ruby’s MRI is green threaded, but the JRuby interpreter uses native threads in the JVM, just like Java. Also, Rails 2.2 just released 2.2 RC1 that is thread safe. Merb was thread safe from the start and just released 1.0 RC2.

Corporate IT: There aren’t enough ruby programmers to staff a project.

Ruby: The Rails Rumble contest didn’t have any problems finding entrants. Five hundred programmers just gave up a weekend to write 248,000 lines of code. Teams up to four completed 131 different Rails projects in under 48 hours, so you can see just how productive a small group can be in Ruby.

Corporate IT: Sorry but we need dependable database connectivity, not this serial locking business.

Ruby: So pooled connections in jruby and Rails 2.2 scratch that itch?

Corporate IT: There still isn’t a big company backing it so no support. No support, no chance bub!

Ruby: Have you ever actually called Microsoft about a .Net problem? Or maybe Sun to support your Java app? Maybe you have, or at the very least arranged a support contract with a .Net or Java consulting company. Try instead one of the fine Ruby consulting companies like EdgeCase, HashRocket or ThoughtWorks. Sun already bankrolls the JRuby guys and for the Softies out there, Microsoft is putting its wallet behind Ruby on the CLR.

Corporate IT: Books?

Ruby: New one every day.

Corporate IT: You’ll get me to use some text editor in place of my IDE when Heck freezes over.

Ruby: Not a problem. NetBeans guy, Eclipse, or IntelliJ?

Corporate IT: Yeah, okay, you win. Now can I have that stack of waterfall project specs back, they were holding up the table at that end.

Ruby: Have you ever considered Agile?

If you liked this article, consider subscribing to this blog via email or RSS. Also, consider subscribing to have our free weekly newsletter sent to your email inbox.

Photo attributed to Megyarsh @ Flickr CC

Aaron Worsham / Aug 27, 2008

Quick bite – show / hide button in Rails, RJS

Sazbean is about online business strategy and we work hard to keep this blog as accessible to our readers as possible. ‘Say it with words, not code’ is one of our guiding principles which keeps us honest when covering technical topics with applied business uses. A principle, I should add, that I will be flagrantly ignoring for this post.

It isn’t always wise to hold back that urge to express our deeper technical understand of a subject we are passionate about. Instead, we have opted to create a segment called quick bites that will be short, technically focused example posts about some subject we are currently working.

I was recently building a UI for a client in Rails and found a good use for a show/hide button in the design. Show/hide buttons, as their names describe, reveal content when pressed and then hide it when pressed again. Typical example code for this using Rails and Javascript might be…

Aaron Worsham / May 14, 2008

Interview with Lance Walley, CEO of Engine Yard

I have mentioned before that hosting Rails applications is one of those great opportunities to avail yourself of assistance. The guys behind Engine Yard saw their chance to help the community and build out a solid foundation for a business. I had a chance to talk with Lance Walley, CEO of the San Francisco based hosting company about Ruby, Rails and their business model.

Sazbean: What problem is Engine Yard solving?
Lance: We make deployment and scaling of Ruby on Rails applications easy and largely hands-off. Our customers pay for great infrastructure and excellent people running it, all focused on Rails apps. In the end, they see us as inexpensive payroll on top of great hosting infrastructure. Some of the basic technologies (Ruby and Rails) can be improved or augmented our support of Rubinius and Merb are helping both move forward and grow to answer customer needs. We are hosting + expertise + software development to make Ruby and Rails better for all!

Sazbean: So how can EY help the average B2B company?
Lance: B2B companies will certainly want to develop web apps to support internal needs and external needs (customers). Ruby on Rails is great for fast development of those apps. Engine Yard is great for no-thinking, just-get-it-done-without-me deployment and management of those apps once they’re developed.

Sazbean: Obie Fernandez wrote in a January 2008 article that there was a waiting list for new customers. Is this still true?
Lacnce: We massively built up our support organization, which includes sys admins, Rails experts, and database admins. That solved the waiting list issue. We now have a queue of about 5 days, mostly because customers take time getting info to our guys that our guys need to deploy customers’ apps.

Sazbean: Does EY consider itself a silicon valley startup?
Lance: We’re a Sacramento / San Francisco startup. We modeled this business to be profitable and not need VC [Venture Capital ~ed]. We later took VC to pursue areas that represent a huge opportunity, and which we could not pursue quickly without VC and we’re about 2 years old and didn’t take VC until we were 1.5 years old so I’m not sure if that all adds up to traditional valley startup.

Sazbean: Unlike startups with a software product, hosting solutions like EY have a large barrier to entry. You need hardware, you need specialized skills and you need capital. So, why hosting?
Lance: It was a natural outgrowth of a previous business. We have an older company that does consulting; we saw that clients didn’t want to do this stuff, but they wanted really good solutions run by top-notch people. We created Engine Yard. while it did take some capital up front, we knew from the experience of others that it’s a quick cash generator vs. some other businesses. We literally saw it as a pretty quick path to cash generation and profitability. We’re now doing a lot of stuff that goes beyond that original idea, but we always saw hosting as a good business in which to start in a new market like Rails.

Sazbean: Many B2B companies are untrusting of startups and of new ventures. It means something that you are profitable and stable and up front about it.

Lance: Yeah, we experienced some of that back when we started in 2006. People had to get to trust us and our financial footing also helps when they know that we founders are all small business guys in the past… never huge companies, but real, profitable, decade or more companies each Now, of course, with pretty big VCs involved, that’s also a good thing, but I suppose VC makes some people suspicious, too. We have still kept our basic business philosophies of running a tight ship, not burning cash without need, etc.

Sazbean: You mentioned your people a few times tonight. Do you consider your people the distinguishing part of the equation?
Lance: There are 3 distinguishing parts.

The infrastructure we designed is extremely solid, very redundant, etc. We’ve been at it for 2 years and the architects are incredible people. Customers are buying that.
The staff that supports our customers directly is top-notch. There are between 35-40 people in Support now, spread from CA to NY to UK to Australia. Customers are paying for the ability to get help and wisdom from this staff 24/7. As well as stuff like database tuning, etc. The people component is very important to customers.
We have some of the best people working on those open-source projects that promise to improve Ruby and Rails for everyone. Our customers are indirectly buying into those people, too. There is a general feeling by customers that they get all this expertise for a relatively low price in terms of human costs.

Sazbean: Any well known Rails websites using EY that you can disclose?
Lance: Sure If you check out http://rails100.pbwiki.com/ we are literally involved thru Engine Yard or Quality Humans, Inc with 33-50% of those sites. Hulu (#3) for instance is NBC + Fox we helped them build that site back in 2006 or 2007. Seeking Alpha is a cool financial info site, they provide data to Yahoo Finance. Kongregate was a VERY early EY customer. I think they just took an investment from Jeff Bezos, who does not invest lightly.

Sazbean: Impressive.

Lance: It’s not yahoo or google, but they’re coming.

Technorati Tags: engine yard, rails, rails hosting, internet consulting