What's Wrong with "HTML5"
In the past year or so, the term "HTML5" has increasingly been picked up by the tech press as the successor to "DHTML", "Web 2.0" or "Ajax". When used by the tech press, it is becoming a generic term for "the next generation of web technology", except that the term "HTML5" is less precise than even that. Consider the first paragraph of an article about HTML published this week: HTML5 is the hot to
Bundler: As Simple as What You Did Before
One thing we hear a lot by people who start to use bundler is that the workflow is more complicated than it used to be when they first start. Here's one (anonymized) example: "Trying out Bundler to package my gems. Still of the opinion its over-complicating a relatively simple concept, I just want to install gems." Bundler has a lot of advanced features, and it's definitely possible to model fairl
Here's to the Next 3 Years
I officially joined Engine Yard on January 1, 2008, about a week before we announced our Series A funding, becoming its twenty-second employee. I was Engine Yard's very first "Engineering" hire, and I would spend the next year working on Ezra's Merb project, finally releasing Merb 1.0 at MerbCamp that October. When I joined Engine Yard, I had already been working on the jQuery project for a couple
Announcing Handlebars.js
For a number of years, I've been about as active in client-side development (through jQuery) as I have been active in server-side development (through Merb and then Rails). Recently, I've released a couple of libraries (jQuery Offline and Rack::Offline), designed to make it easier to build applications that can withstand both flaky connections and a complete lack of connectivity. Of course, those
Automatic Flushing: The Rails 3.1 Plan
preamble: this post explains, in some detail, how we will implement a nice performance boost for Rails developers. Understanding the details might help gain the full benefits of the optimization, but you will gain some benefits even if you have no idea how it works. As you've probably seen, DHH announced that we'd be looking at flushing in Rails 3.1 to improve the client-side performance of typica
Threads (in Ruby): Enough Already
For a while now, the Ruby community has become enamored in the latest new hotness, evented programming and Node.js. It's gone so far that I've heard a number of prominent Rubyists saying that JavaScript and Node.js are the only sane way to handle a number of concurrent users. I should start by saying that I personally love writing evented JavaScript in the browser, and have been giving talks (for
Everyone Who Tried to Convince Me to use Vim was Wrong
A couple weeks ago, I took the plunge and switched to vim (MacVIM, to be precise). It wasn't the first time I tried to make the switch, and I had pretty much written it off entirely. Why? Because the past few times I tried switching to vim, I took the advice of a master vim user, and quickly sunk into the quicksand of trying to learn a new tool. In every prior attempt, I gave vim a few days before
My Common Git Workflow
A recent post that was highly ranked on Hacker News complained about common git workflows causing him serious pain. While I won't get into the merit of his user experience complaints, I do want to talk about his specific use-case and how I personally work with it in git. Best I can tell, Mike Taylor (the guy in the post) either tried to figure out a standard git workflow on his own, or he followed
The Web Doesn't Suck. Browsers Are Innovating.
This week saw a flurry of back-and-forth about the future of the web platform. In the "web sucks" camp were Sachin Agarwal of Posterous (The Web Sucks. Browsers need to innovate) and Joe Hewitt (Sachin summarized some of his tweets at @joehewitt agrees with me). Chris Blizzard responded with a few narrow examples of what Firefox has been doing lately (geolocation, orientation, WebGL). On Hacker Ne
Using .gemspecs as Intended
When you clone a repository containing a Unix tool (or download a tarball), there's a standard way to install it. This is expected to work without any other dependencies, on all machines where the tool is supported. $ autoconf $ ./configure $ make $ sudo make install This provides a standard way to download, build and install Unix tools. In Ruby, we have a similar (little-known) standard: $ gem bu
Ruby's Implementation Does Not Define its Semantics
When I was first getting started with Ruby, I heard a lot of talk about blocks, and how you could "cast" them to Procs by using the & operator when calling methods. Last week, in comments about my last post (Ruby is NOT a Callable Oriented Language (It’s Object Oriented)), I heard that claim again. To be honest, I never really thought that much about it, and the idea of "casting" a block to a Proc
SafeBuffers and Rails 3.0
As you may have read, Rails adds XSS protection by default in Rails 3. This means that you no longer have to manually escape user input with the h helper, because Rails will automatically escape it for you. However, it's not as simple as all that. Consider the following: Hello <strong>friends</strong>! <%= tag(:p, some_text) %> <%= some_text %> In the above example, we have a few different scenari
The Building Blocks of Ruby
When showing off cool features of Ruby to the uninitiated (or to a language sparring partner), the excited Rubyist often shows off Ruby's "powerful block syntax". Unfortunately, the Rubyist uses "powerful block syntax" as shorthand for a number of features that the Pythonista or Javaist simply has no context for. To start, we usually point at Rake, Rspec or Sinatra as examples of awesome usage of
Using Bundler in Real Life
A lot of people have asked me what the recommended workflows for bundler are. Turns out, they're quite simple. Let's step through a few use-cases. You Get a Repo for the First Time You've just checked out a git (or other) repository for an application that uses bundler. Regardless of any other features of bundler in use, just run: bundle install This will resolve all dependencies and install the o
ActiveModel: Make Any Ruby Object Feel Like ActiveRecord
Rails 2.3 has a ton of really nice functionality locked up in monolithic components. I've posted quite a bit about how we've opened up a lot of that functionality in ActionPack, making it easier to reuse the router, dispatcher, and individual parts of ActionController. ActiveModel is another way we've exposed useful functionality to you in Rails 3. Before I Begin, The ActiveModel API Before I begi
Spinning up a new Rails app
So people have been attempting to get a Rails app up and running recently. I also have some apps in development on Rails 3, so I've been experiencing some of the same problems many others have. The other night, I worked with sferik to start porting merb-admin over to Rails. Because this process involved being on edge Rails, we got the process honed to a very simple, small, repeatable process. The
The Craziest F***ing Bug I've Ever Seen
This afternoon, I was telling a friend about one of my exploits tracking down a pretty crazy heisenbug, and he said he thought other people would be interested in hearing about it. So let me tell you about it. Before you continue, if you're not interested in relatively arcane technical details, feel free to skip this post. It's here mainly because a friend said he thought people would be intereste
Generic Actions in Rails 3
So Django has an interesting feature called "generic views", which essentially allow you to to render a template with generic code. In Rails, the same feature would be called "generic actions" (just a terminology difference). This was possible, but somewhat difficult in Rails 2.x, but it's a breeze in Rails 3. Let's take a look at a simple generic view in Django, the "redirect_to" view: urlpattern
?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+KatzGotYourTongue+%28Katz+Got+Your+Tongue%3F%29&utm_content=livedoor
After writing my last post on Rails plugin idioms, I realized that Ruby metaprogramming, at its core, is actually quite simple. It comes down to the fact that all Ruby code is executed code--there is no separate compile or runtime phase. In Ruby, every line of code is executed against a particular self. Consider the following five snippets: class Person def self.species "Homo Sapien" end end class
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
