alias_method_chain in models
As people know, there's been a fair bit of back-and-forth between me, the apparent foe of alias_method_chain, and folks who feel that alias_method_chain is a perfectly reasonable API that people should not blindly hate. There are basically two use-cases for alias_method_chain: Organizing internal code Modifying existing code Using alias_method_chain to organize internal code is an interesting disc
A Tale of Abort Traps (or Always Question Your Assumptions)
For a few months now, the bundler team has been getting intermittent reports of segfaults in C extensions that happen when using bundler with rvm. A cursory investigation revealed that the issue was that the C extensions were compiled for the wrong version of Ruby. For instance, we would get reports of segfaults in nokogiri when using Ruby 1.9 that resulted from the $GEM_HOME in Ruby 1.9 containin
Gem Versioning and Bundler: Doing it Right
Recently, an upgrade to Rake (from version 0.8.7 to version 0.9.0) has re-raised the issue of dependencies and versioning in the Ruby community. I wanted to take the opportunity to reiterate some of the things I talked about back when working on Bundler 1.0. First, I'll lay out some basic rules for the road, and then go into some detail about the rationale. Basic Versioning Rules for Apps After bu
Using SproutCore 2.0 with jQuery UI
One of the goals of SproutCore 2.0 is to make it trivial to integrate the tools you're already using together with SproutCore. One way that we do that is to make it possible to drop a SproutCore app into a small part of your existing page. Greg Moeck did a great job demonstrating this functionality on the SproutCore Blog a couple of weeks ago, and I'd definitely recommend checking it out if you're
What's Up With All These Changes in Rails?
Yesterday, there was a blog post entitled "What the Hell is Happening to Rails" that stayed at the number one spot on Hacker News for quite a while. The post and many (but not most) the comments on the post reflect deep-seated concern about the recent direction of Rails. Others have addressed the core question about change in the framework, but I'd like to address questions about specific changes
May « 2010 « Katz Got Your Tongue?
Yehuda Katz is a member of the Ruby on Rails core team, and lead developer of the Merb project. He is a member of the jQuery Core Team, and a core contributor to DataMapper. He contributes to many open source projects, like Rubinius and Johnson, and works on some he created himself, like Thor. Anyone in the lobby or heading here soon? I'm heading out to #gothamjs shortly I wrote somewhat extensiv
Understanding JavaScript Function Invocation and "this"
Over the years, I've seen a lot of confusion about JavaScript function invocation. In particular, a lot of people have complained that the semantics of this in function invocations is confusing. In my opinion, a lot of this confusion is cleared up by understanding the core function invocation primitive, and then looking at all other ways of invoking a function as sugar on top of that primitive. In
Understanding "Prototypes" in JavaScript
For the purposes of this post, I will be talking about JavaScript objects using syntax defined in ECMAScript 5.1. The basic semantics existed in Edition 3, but they were not well exposed. A Whole New Object In JavaScript, objects are pairs of keys and values (in Ruby, this structure is called a Hash; in Python, it's called a dictionary). For example, if I wanted to describe my name, I could have a
New Hope for The Ruby Specification
For a few years, a group of Japanese academics have been working on formalizing the Ruby programming language into a specification they hoped would be accepted by ISO. From time to time, I have read through it, and I had one major concern. Because Ruby 1.9 was still in a lot of flux when they were drafting the specification, the authors left a lot of details out. Unfortunately, some of these detai
A Proposal for ES.next Proposals
Over the past few years, I have occasionally expressed frustration (in public and private) about the process for approving new features to the next edition of ECMAScript. In short, the process is extremely academic in nature, and is peppered with inside baseball terms that make it nearly impossible for lay developers to provide feedback about proposed new features. In general, this frustration was
How to Marshal Procs Using Rubinius
The primary reason I enjoy working with Rubinius is that it exposes, to Ruby, much of the internal machinery that controls the runtime semantics of the language. Further, it exposes that machinery primarily in order to enable user-facing semantics that are typically implemented in the host language (C for MRI, C and C++ for MacRuby, Java for JRuby) to be implemented in Ruby itself. There is, of co
Announcing Amber.js
A little over a year ago, I got my first serious glimpse at SproutCore, the JavaScript framework Apple used to build MobileMe (now iCloud). At the time, I had worked extensively with jQuery and Rails on client-side projects, and I had never found the arguments for the "solutions for big apps" very compelling. At the time, most of the arguments (at least within the jQuery community) focused on brin
Amber.js (formerly SproutCore 2.0) is now Ember.js
After we announced Amber.js last week, a number of people brought Amber Smalltalk, a Smalltalk implementation written in JavaScript, to our attention. After some communication with the folks behind Amber Smalltalk, we started a discussion on Hacker News about what we should do. Most people told us to stick with Amber.js, but a sizable minority told us to come up with a different name. After thinki
JavaScript Needs Blocks
While reading Hacker News posts about JavaScript, I often come across the misconception that Ruby's blocks are essentially equivalent to JavaScript's "first class functions". Because the ability to pass functions around, especially when you can create them anonymously, is extremely powerful, the fact that both JavaScript and Ruby have a mechanism to do so makes it natural to assume equivalence. In
Tokaido: My Hopes and Dreams
A few weeks ago, I started a kickstarter project to fund work on a project to make a long-term, sustainable binary build of Ruby. The outpouring of support was great, and I have far exceeded my original funding goal. First, I'd like to thank everyone in the community who contributed large and small donations. This kickstarter couldn't have been as successful as it has been without the hundreds (65
Tokaido Status Update: Implementation Details
Hey guys! Since my last update, Tokaido was fully funded, and I've been hard at work planning, researching and working on Tokaido. So far, we have a working binary build of Ruby, but no setup chrome. Because the binary build already exists, Terence Lee was able to experiment with it at a recent Rails Girls event, with great success: Our @hone02 made such improvements to the installment last night
August Tokaido Update
It's been a while since I posted anything on my blog, and I figured I'd catch everyone up on the work I've been doing on Tokaido. Components Tokaido itself is made up of a number of components, which I am working on in parallel: Ruby binary build, statically compiled A logging and alerting UI Remote Notifications for Rails 3+ Integration with Puma Express Integration with code quality tools Resolv
I'm Running to Reform the W3C's TAG
Elections for the W3C's Technical Architecture Group are underway, and I'm running! There are nine candidates for four open seats. Among the nine candidates, Alex Russell, Anne van Kesteren, Peter Linss, and Marcos Cáceres are running on a reform platform. What is the TAG, and what do I mean by reform? What is the TAG? According to the TAG's charter, it has several roles: to document and build con
Extend the Web Forward
If we want to move the web forward, we must increase our ability as web developers to extend it with new features. For years, we've grabbed the browsers extension points with two hands, not waiting for the browser vendors to gift us with new features. We built selector engines, a better DOM API, cross-domain requests, cross-frame APIs. When the browser has good extension points (or any extension p
An Extensible Approach to Browser Security Policy
Alex Russell posted some thoughts today about how he wishes the W3C would architect the next version of the Content Security Policy. I agree with Alex that designing CSP as a "library" that uses other browser primitives would increase its long-term utility and make it compose better with other platform features. Alex is advocating the use of extensible web principles in the design of this API, and
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
