pie

Another recent Lomo-esque JS library: http://vintagejs.com/

NYC provides a list of insurance options here:

http://nyc.gov/hilink

Some of the lowest-cost options are offered through Freelancers Union:

https://be.freelancersunion.org/benefits/

Is this a remote proxy to a local database? API-oriented development may be a flexible model, but how does this yield acceptable performance?

Oh, Wired... This article does not cover audio files at all, and there's a single passing mention of MP3 players. It's a rambling history of a company that markets to the "audiophile" gadget crowd. Reads like straight PR.

Accurate results for technical topics brought me to Google, and all the extra query formatting that's required these days is somewhat irritating.

Another peeve is that the search box on the results page (with Instant disabled) routinely drops input or moves the insertion point.

There are additional interesting map details at Google's crisis map:

http://crisislanding.appspot.com/

As someone running 5 server processes in development for one project, this hugely simplifies all the terminal juggling on my local box, and centralizes the associated commands as part of the codebase. It's a little like a "bundler for processes!"

There appear to be a few kinks to be worked out; for example Foreman fails to kill off Redis (for me) as described in this closed bug report:

https://github.com/ddollar/foreman/issues/15

Not a huge deal though. I'm happy to be using it for development.

This reminds me, Derek Sivers seems to be putting together a project along similar lines: http://karmalist.com/

Offhand, I can think of Zoho Creator: http://www.zoho.com/creator/

It's an amusing idea, but I'm not sure how interesting this is without a performance history or measures against similar automated predictions.

My apps on Heroku seem to be running fine, with just a tad more lag than usual.

I came here to say this too. Other headphones have come and gone, but I always have a pair of MDR-7506 around. They are incredibly sturdy and well designed, and while they may shape the sound slightly, are very detailed (including decent bass) even at low volumes.

I can confirm that Paperclip does work with Rails 3. Some recent merges and updates broke it for awhile, but I think things are back to normal now. (If not, a pre-March fork of the rails3 branch will do in a pinch.)

More discussion going on over here: http://news.ycombinator.com/item?id=1361543

I think at the most basic level the "installation" process simply sets up shortcuts to existing web apps in Google Chrome.

There's the ability to install serverless (static file based) things too; the example given is browser-based games.

More documentation on Unicorn is always nice, since it feels a little sparse in places, and sometimes I'm left wondering whether I've overlooked something in my production setup.

Could have used a little more discussion on signals (e.g. USR2 for reloading code) or possibly other daemon control type issues, which I recall doing the most fiddling with.

I'd still like to hook Unicorn up to Munin or Nagios (for historical stats, not process monitoring), but haven't found any resources on the subject.

I have worked for a university and several organizations that have had basic guidelines like this. It's much more important in large organizations when many small departments or individuals are creating branded things.

One sees this basic type of thing in press kits and even (er, kinda) "link to us" or "powered by" graphical widgets, but the focus on consistent color and typography are things I think could stand to get some more attention. This type of reference is especially helpful for non-designers who aren't immediately inclined to think about consistency and branding.

I use chef for about 10-15 slicehost nodes at work (in production for about 3 months now). It's worked well thus far but requires writing some bootstrap scripts for installing chef on a fresh instance and a fair amount of diving into the DSL (and sparse areas of documentation) depending on your needs.

I also developed all my recipes from scratch (didn't use any of the preset opscode stuff, though those are great examples of what can be done and very useful for standard installations of things). I haven't worked with the new recipes mentioned either, but it looks like chef is beginning to grow into some of the potential created by some of the recent infrastructure enhancements.

The whole ordeal probably took about two weeks of learning, tuning, and testing, but it could be MUCH quicker for more standard and homogenous server stacks - you can start with recipes used by Engine Yard and 37signals, for example.

Doesn't describe many common upgrade scenarios; it's much more about starting a new Rails 3 project.

The official upgrade plugin might be a good place to start:

http://github.com/rails/rails_upgrade

I really liked the idea of Facebook Lite, but it always felt significantly slower, and content was often quite stale, rendering a product that seemed awkward to use and possibly even incomplete.

This eventually drove me back to regular Facebook. Guess it's time to stop hoping for improvements so I can switch back.

I don't use my real name on facebook either, and I know many other folks who do the same. Indeed, I might prefer to use my real name on NewsTilt but NOT facebook.

As with many of the login complaints, this is probably only an issue for a small minority of your target users.

Yep, keyword bookmarks have had a significant impact on the way I search with a web browser. Their use eliminates the layer of complexity of visiting search hub services (like DuckDuckGo or YubNub) and feels more responsive than using a separate search box in the browser.

I've done DuckDuckGo searches with "d" for a little while now.

Exact correctness aside, I call solo artists "bands" just to keep things simple.

In Aphex Twin's case, he makes it pretty clear that he's just one feller, so I didn't realize it was a common misconception. There are plenty of other similar Warp artists too, like Squarepusher.

I also call certain folders full of MP3 files "albums." Heh.

This is quite old, but still fascinating.

Aphex Twin and Plaid are great bands and even took the time to include easter eggs in their songs.

I don't even want to think how long it would take to tag 4,000 albums properly either. This fear alone keeps me away from database-backed music systems.

This basically states that Puppet is more established, which is an important point, but not exactly a conclusive "win" for everyone.

Unless I misunderstand #9 ("explicit dependency management"), Chef does indeed have this. It has resources that can both "listen" and "notify," just like in the Puppet example given, and things are executed in dependency order unless execution is specified as "immediate."

I agree with the point about Chef's Rails-oriented deployment. It's a little frustrating having to negate the default Rails settings while doing a PHP deployment.

To me, the major downsides to Chef are quirks/instability as changes are made during active development, and somewhat sketchy documentation in places. Still a great system though.

(Also: check out the reply from Adam Jacob, lead dev of Chef, in the comments. I noticed this after posting here.)

I agree - if I saw "sponsored link" in a review, I would assume that the review itself was somehow sponsored.

Perhaps some other type of notice would be more appropriate, but I can't think of what that would be.

Simply links to a PDF, sans any analysis:

http://www.google.com/webmasters/docs/search-engine-optimiza...

Of course... right when I was getting ready to launch a site meant to evolve into an app marketplace. Leave it to Google's serendipitous timing.

Fortunately this is a complex space with plenty of room for competition and complementary services.

You can observe this same multi-factor effect in restaurant or product reviews.

When a restaurant serves one customer unsatisfactorily or a product is delivered in poor condition, the rating suffers substantially. This rating no longer represents the quality of the thing itself but also the individual's experience.

The same is true with a cook's experience preparing a recipe. Depending on the reviewer's bias, a recipe rating might describe circumstance and culinary skill better than the quality of the instructions.

As other folks here have mentioned, there's also the issue of average reviewers being not-so-great at representing their true opinions with linear rating systems, but that's a whole other topic.