sorted by: recent | see : popular

Content Tagged with Ruby + Opinion

On the eve of a new JRuby course at rubylearning.org, Charles Nutter gives some advise to JRuby newbies in the form of an interview.

'Funny' Rails Envy Podcast Voicemail remix. In case you need a good laugh today listen to the remix, though the orginal voicemail it making some valid points. Way better than Terry Chays' PHP anthem.

When starting a Rails project, four golden folders are predefined: Models, Views, Controllers, Helpers. Could we possibly need anything more? In my experience, the answer is yes. This leads to the question of, where do these extra files go?

Be productive with Squeak and Seaside. Metaprogramming and DSLs with Smalltalk.

It seems like their is a new Cool wave flowing in the developer community which involves finding reasons to say PHP sucks.

Note that I’m not going to address the “Rails vs. Scala” debate, which would be better rephrased as “Ruby vs. Scala”, or “Rails vs. Lift or a hypothetical Scala web app framework”.

This week's source is a clever "ClickOnce"-style hack for Ruby. It's cool because it brings together a number of technologies into a very clean end-user experience. The intent is to make the running of a Ruby GUI Application effortless, and it works and it's brilliant on several levels.

I was talking to Tim the other day about auditing Rails projects, and how we see a lot of Rails projects that reinvent the wheel instead of using plugins. The obvious follow-up question, of course, is "What plugins (or gems) should we be using?" Below I list ten plugins that we use regularly, and a brief reason why you might want to, too.

Even if you’re new to the Ruby community, you are unlikely not to have heard about the Pragmatic Programmers, who are well reputed for publishing great programming books. You may not have noticed that lately though, they’ve also been releasing several series of screencasts.

Twitter is arguably the most heavily used Ruby on Rails application in the world. Almost since its inception, Twitter has fostered a wildly passionate cult following. Also from the beginning, Twitter has suffered from chronic outages under that load.

This is a continuation of my previous posts describing layers of code written in different programming languages. I have thought about the things involved for a while, and had several discussions with people about it. There were some parts that I didn't describe as well as I thought in my posts, and I will try to do better in this one.

RailsConf 2008 is over, and it was by far better than last year. I'm not one for drawn-out conference wrap-up posts so here's a summary of my most inspiring moments and if applicable how they're going to affect JRuby going forward.

Of course anyone who reads my blog expected I'd have something to say about Maglev once it was made public. I've previously performed what I thought was a fair analysis of the various Ruby implementations, and Maglev was mostly a sidebar. With their coming out at RailsConf, they're now fair game for some level of analysis.

Announcing the Ruby Benchmark Suite project.

This post covers a couple of topics: 1) Why MagLev matters; 2) My plan for the next Ruby shootout.

Here's my summary of Saturday morning's events.

Over the past year, there's no doubt that if there is a poster child for Rails, it is now Twitter. With such notorious bouts of downtime, a worse poster child Rails could not possibly hope for. But is Twitter even the largest application out there running on Rails? Does it even matter?

Lately I seem to find everywhere lots of articles about the imminent dismissal of Java and its replacement with the scripting language of the day or sometimes with other compiled languages. No, that is not gonna happen. Java is gonna die eventually of old age many many years from now. I will share the reasoning behind my statement. Let’s first look at some metrics.