はてなブックマーク

I’ve know that str.split had an idiom which split strings into characters (by default, bytes in Ruby 1.8) if passed a regular expression that matched a zero-width string, thus: string.split(//) What I didn’t know was that this idiom was sensitive to either the encoding of the regular expression (example: //u) or the value of KCODE. But that’s not the most important part.  The interesting thing is

Wanting to learn more about Google Wave, I ported the Wave Robot Python Client library to Ruby, mainly because I wanted to understand the protocol.  The current protocol is tightly coupled to the Java server implementation. >>> import waveapi.document >>> import waveapi.util >>> waveapi.util.Serialize([waveapi.document.Image('http://example.com/foo.jpg', width=100, height=100)]) {'javaClass': 'jav

At one level, Google Wave is clearly a bold statement that “this is the type of application that every browser should be able to run natively without needing to resort to a plugin”.  At to give Google credit, they have been working relentlessly towards that vision, addressing everything from garbage collection issues, to enabling drag and drop of photos, to providing compelling content (e.g., Goog

It is a name I don’t care for, but alas, one that likely will stick.  The concept is to provide explicit support in HTML for embedding metadata in content.  Both Microformats and RDFa do related things. As is common in distributed development, things haven’t exactly happened in chronological order. Ian abstracted out use cases.  Manu participated, Elias seems happy, and Shelley is continuing to re

Introduction Current state: HTML is being developed outside of the W3C by a number of browser implementers, excluding Microsoft. The prevalent feeling amongst those that do so is that if the W3C doesn’t adopt their spec, the W3C will look dull. Desired state: Many groups representing many different disciplines and constituencies contributing to HTML. Documents with the requisite amount of consensu

David Heinemeier Hansson: you can install Rails 2.2 through RubyGems. We now require RubyGems 1.3.1, so be sure to update that first Problem: $ gem -v 1.2.0 $ gem update --system ERROR: While executing gem ... (RuntimeError) gem update --system is disabled on Debian. RubyGems can be updated \ using the official Debian repositories by aptitude or apt-get Solution: $ wget http://rubyforge.org/frs/do

Roy Fielding: All of those points are rather small compared to my overall complaint that it isn’t appropriate to define a “REST” binding to a specific data model’s limitations. The whole point of REST is to avoid coupling between the client applications and whatever implementation might be behind the abstract interface provided by the server. First, by way of disclosure, I had an opportunity to pr

atom2json.erl converts a directory of Atom files to a directory of JSON files.  As with most real-life problems, this one has multiple layers. First one needs to settle on an XML to JSON mapping.  It turns out that there are many different approaches to this problem.  For now, I elected to do some generic XML-to-JSON mapping crap.  An RFC in this area would be helpful, particularly one that dealt

Alex Harden: I’m actually tempted to roll my own Planet and call it a day What would it take to convince you?  ;-) At the moment, it is a matter of downloading, editing a config.ini, optionally tailoring a template, and finally scheduling the application to run. As I run planet locally, I also have an additional step where I upload the results. Something that might make it easier to get started is

I’ve roughed in the consumer pieces to my OpenID implementation.  Except for the autodiscovery, all the pieces were things I could lift from my test cases, and in one case, from the server support for dumb consumers.  My implementation attempts to be smart consumer, but will degrade as necessary. Despite the fact that I can self-authenticate, I won’t feel confident about this until I get some real

Jon Udell: I’ve been checking out the LINQ technical preview, and it’s definitely an eye-opener. The following snippet does a three-way join across an XML data source and two CLR objects. The XML data source is the content of this blog. The objects are a dictionary of date mappings, and an array of strings. The output is constructed as XML. As an educational exercise, I’ve converted this to Ruby d

I spent four of the last six work days in all day meetings.  While the meetings were about other things (primarily GlueCode and Zend related, in case you were wondering), I saw several indications the basic fundamentals of REST are were not completely internalized.  Meanwhile, Don Box asked a very much related question. The starting point is usually that somebody has an API that is intended to shi

Prev Next RSS versions