Undo, redone. Aza Raskin reminds us to Never Use a Warning When you Mean Undo. The article got a lot of attention the past few days, which is great. It’s often a simple change that makes apps much easier to use. As a reminder, and for those who like the simplest thing that could possibly work, here’s my implementation of an Undo button for Rails.
“Industry” standard. Rob Weir teaches us how to stack a committee. Public demo courtesy of Microsoft Corp:
As you can see, at the start of the year, V1’s membership consisted of seven organizations, six of whom on Friday voted “Disapproval, with comments”, and one (Microsoft) who voted “Approval, with comments”. The membership spurt came at the very end, in the last month, when 16 new members joined V1. Of these 16 new members, 14 of them voted, “Approval, with comments” on Friday.
Me too. I realize, by the time this post hits your feed reader, you’ve seen this quote from Bill de hÓra ten times. Here’s no. 11:
The relative verbosity of programming languages isn’t the interesting thing; nor is typing doctrine. What’s interesting is the culture of frameworks and what different communities deem valuable. My sense of it is that on Java, too many web frameworks - think JSF, or Struts 1.x - consider the Web something you work around using software patterns. The goal is get off the web, and back into middleware. Whereas a framework like Django or Rails is purpose-built for the Web; integrating with the internal enterprise is a non-goal.
…
It’s hard to explain sometimes just how time-consuming it can be to get Web things done on some Java frameworks. This post will be a handy thing to point at next time I’m lost for words :)
The problem with baseball. Speaking of handy things to point out, ‘ We Tried Baseball and It Didn’t Work is worth keeping on speedlink.
Chipping the web - Maid of the Seas — Chip’s Quips