We’ve done it again and we’re pretty excited about it. We’ve unleashed yet another addition to the family: RubySource.
RubySource is armed with a team of talented, informed, and passionate bloggers, such as Dan Cheail and Xavier Shay. These Ruby practitioners want to share their knowledge in order to help bring Ruby to everyone in the web development community.
You can expect to find advice, tutorials, and commentary on the Ruby and Rails ecosystem, including:
Best practices for testing, developing, and deploying Ruby-based applications
Guides for experienced developers interested in making the switch to Ruby
Insight into Ruby’s syntax, conventions, and idiosyncrasies
Updates on releases, events, and other happenings across the broader Ruby community
Keep up with us on Twitter by following @rubysource or join us on Facebook.
I just hope it doesn’t get littered with too many Rails posts. I want to know about other frameworks and learn new approaches to Ruby web development. Of the 9 articles on the home page, only two aren’t rails related. Although I guess rails developers are probably the ones who need the most help.
Although I guess rails developers are probably the ones who need the most help.
I think maybe they’re just louder. That and a lot of businesses who started using Ruby, used Rails, so now there’s a lot of Rails code floating around…
What I meant by that was two fold. First, Rails attracts a lot of beginners to Ruby. I personally made a conscious effort to learn Ruby first, before getting into Rails. It turns out that I wasn’t a huge fan of rails, and decided to go down the road of freedom by using the likes of Sinatra, where I could enjoy creating libraries and my own solutions to what are probably common problems; all good learning experience and right up my alley.
The second reason for what I said, is that Rails employs a lot of magic, and puts a restriction on design freedom, hence there’s both a lot to be learnt before you master it, and because of the tighter boundaries, it seems to bring the problem solvers out of the wood work, so you end up with people posting all sorts of different tips and tricks for solving a particular problem in an alternative way, all within the confines of Rails. So in that sense, Rails makes a good subject for articles.
