Thursday, March 04, 2010

Joel’s Taking it Offline

I’m not sure if I should actually write this post. Everyone else who reads his blog is probably doing the same thing, and I’ll just be one voice amongst a million. But I’ve already started typing, I might as well finish…

Joel Spolsky has decided to stop blogging at Joel on Software. Which gives me mixed emotions.

On the one hand, it was a great blog, with many great, classic posts on software development. Many of those classic posts became part of the books, Joel on Software and More Joel on Software. I can’t remember how I first came across Joel’s blog, but as soon as I read it, I was hooked.

On the other hand, Joel hasn’t been writing that much on the blog lately anyway. By lately, I mean, oh… a year? Two years? More? The thing is, I started following him too late. However it was that I came across Joel’s blog, it was through some link to one of his classic posts, which I read, and thought, “Ah, now there’s an intelligent post on [whatever it was about].” Then I read his first book, and enjoyed it thoroughly all the way through. So I added his blog to Google Reader, and prepared myself for the brilliance that would inevitably follow. Only to find that he rarely posted, and when he did, it was either a post about Stack Overflow, or a link to his latest column on Inc. Magazine. It turns out that Joel seems to have done most of his great writing before I ever got on the bandwagon. (I did like the articles for Inc., don’t get me wrong.)

So I’m sorry to see him go, and I wish him luck, but at the same time, he’s got good reasons for stopping, and he hasn’t posted as much in recent times so I guess I’m not missing much anyway.

I just wish there was a slew of other bloggers out there for me to read, ready to take his place.

Wednesday, March 03, 2010

Another Wave Concept Video

The last video I posted illustrated how a bot might be put to good use in a wave, along with a clever way that wave technologies could be embedded within a larger business process.

Today I include a video from SAP with a prototype for a system called Gravity, which illustrates a clever way that an extension can be built for Wave for integrating Wave with other systems.


I can easily see Sparx Systems coming up with an extension for Enterprise Architect UML models (or similar extensions for Rational Rose or other UML tools), or extensions for embedding Microsoft Office documents/spreadsheets/presentations, or a million other ways of integrating software with Wave through extensions.

Or, to go back to the previous example, Salesforce.com envisioned embedding a wave in their ticketing system, but they could also have gone the other way, and created an extension to embed a trouble ticket into the wave. When you load a wave, the extension could dip into the trouble ticketing system to load the information.

Friday, February 12, 2010

Chromium OS

Back in September of 2008, I wrote that I’d downloaded Google Chrome, to give it a try. I didn’t really get why Google had created a new web browser—especially since Firefox already exists; why not just make changes to that?—but I figured I’d try it out anyway. And then I never wrote about it again, but since then Chrome has become my default browser. I use it all the time, only using Internet Explorer when I have to for work, and occasionally using Firefox, but not that often. Why? Two main reasons:

  1. It’s cleaner and sleeker looking than IE or Firefox. Take a look at the screenshots below to see what I mean; Chrome takes up a lot less real estate than the other browsers, leaving more room for the browser window itself.
  2. It’s noticeably faster, especially when it comes to JavaScript. And this was Google’s main purpose in starting an open source browser; obviously all of Google’s sites depend heavily on JavaScript to function, so they spent a lot of time on optimizing the JavaScript engine, to make those sites run faster. Gmail is faster in Chrome than Firefox or IE; Wave is much, much faster, but Wave is a special case, because it’s very much a web-based application, even moreso than Gmail.

    Even preparing the screenshots below was noticeably faster in Chrome than Firefox or IE. (In fact, IE was terrible for this test; opening each new tab took seconds even before I’d loaded anything, plus a few seconds more to load the actual web page.)
chrome

ff

ie
So for reasons of speed and aesthetics, I have been using Google Chrome as my default browser pretty much ever since I first mentioned it, in that initial post. Because all of Google’s applications are web-based, and heavily dependent on JavaScript, they had a vested interest in making available a browser which would render those sites quickly, and provide a good experience to the user while on those sites.

But can we take that a bit further? Why yes, we can—what about netbooks? Those laptop-like things that are cheaper and more stripped down than full-blown laptops, and are only meant for those who want to surf the net? Is there any way we can improve those? Google decided that yes, these can be improved, and they came up with a new open-source operating system, called Chrome OS. (As mentioned, it’s open source; the open source project is called Chromium OS, while the final, Google-branded version that you would see on a laptop, would be Chrome OS. Just like the open source version of the browser is Chromium, while the Google-branded version is called Chrome.) As the name implies, the operating system basically is a browser.

I’ll let Google explain:


What are the benefits of this? The main benefit is speed. When you boot up a netbook running Chrome OS, you’re up and running in seconds. When I say “up and running,” I mean literally just a few seconds between the time you press the power button on your device, and the time that you’re surfing the internet. And I can verify these claims; I downloaded a version of Chromium OS that runs on a USB drive, just to try it out. As I was expecting, it’s incredibly slow overall; the OS wasn’t meant to run on a USB drive like that, and neither was it intended to run on a “regular” laptop, it was intended to run on a netbook, with a solid-state drive, and a very specific set of hardware. And yet, even with the horrible overall performance, when I pop in that USB drive and and press the power button on my laptop, it’s less than 30 seconds before I’m logged on and surfing the net. If I’m getting ready for work in the morning, and want to quickly log on to check my email or something, I can boot up from that USB drive, check my email, and shut down, all in the amount of time it would have taken to see the Windows splash screen if I were booting into Windows. In fact, if my desktop computer (which runs Windows Vista) has gone into sleep mode, it would be quicker to boot up cold into Chromium OS on my laptop than it would be to “wake the computer up” and log back in.

Here are some stats from my laptop, on how many seconds it takes for each stage of the bootup process:

Operating SystemSplash ScreenLogon ScreenAble to Open BrowserReady to SurfTotal Time
Windows XP648105463:25
Ubuntu 95418559
Chromium OSN/A22N/A325

startup time

Note that these stats are actually skewed a little bit, because I have encryption software on my laptop; when I boot it up, I have to log onto the encryption software first, and then I get my boot loader which lets me choose Windows or Ubuntu. (The USB drive bypasses all of that, and just boots right to Chromium.) I did my Windows and Ubuntu timings from the time when I was at the boot loader, after I’d logged onto the encryption software. So there are two important impacts to this, in terms of these numbers:
  1. Since the hard drive is encrypted, Windows is running a bit slower than it otherwise would have. It’s not actually that bad—I’d been expecting it to be slower, when I had to install the software—but based on my memory of how it behaved before the encryption software was installed, I’d estimate that we could probably shave 30–45 seconds off of the total number for Windows XP, if the drive wasn’t encrypted.
  2. Contrarily, this means that these numbers don’t include the initial hardware loading time in the Windows and Ubuntu stats, which they should, but do include them for Chromium, which they shouldn’t (since Chrome OS wouldn’t normally have that phase of startup on a real netbook). So the Windows and Ubuntu numbers should be a bit higher, whereas the real numbers would actually be lower for Chrome OS. (See the demo videos, such as the one below, where they show someone booting a netbook cold into Chrome OS; it really is just a few seconds.)
Interestingly, I was surprised to find that Ubuntu actually shuts down a bit quicker than Chromium:

Operating SystemShutdown Time (seconds)
Windows XP58
Ubuntu 911
Chromium OS16

shutdown time

So how did they get it so fast to boot up? Again, I’ll let Google explain:


Incidentally, if you’re interested in more videos on Chromium, see the Google Chrome Channel on YouTube.

Now, I’m already seeing people around the net who are questioning the need for this OS, but most of the arguments against it show that they don’t understand the intent behind the operating system. Actually, it really means that they aren’t behind the idea of a netbook in the first place; at most, they might like the idea of a cheap, less powerful laptop, but they don’t get the whole netbook concept. Remember, the netbook was never intended to be your primary computer; it’s meant to be a secondary device, for lightweight internet-based stuff, not the only computer you have. If you’re only going to buy one computer, make it a desktop or a laptop and put Windows or Ubuntu or something on it; but if you’re also going to get a secondary device, for browsing or bringing with you to check your email and Facebook from Starbucks, then make it a cheap netbook. If you can get behind that concept, then you can start thinking about whether Chromium OS would be a good operating system for that device; if not, then your arguments against Chromium OS aren’t against the OS itself, but the actual concept of the netbook.

Here are the two most common arguments I’ve seen against Chrome OS, and my rebuttals:

“The whole operating system is browser-based? What if I want an image editing program, or a video editing program, or an IDE? I can’t do everything on the internet—computers have to do things other than just browsing the web!” You’re absolutely right, but netbooks aren’t intended to be the only computers you’ll ever use. If you want to edit photos, or create movies, or write computer code, use your desktop or your laptop for that. That’s not what netbooks are intended for, and it’s not what Chrome OS is intended for. (This argument really boils down to, “if Chrome OS can’t do everything, then it’s useless!” which is just silly.) But if you just want to get on the web, and check your email or check your stocks or catch up on your news or burn a few hours on Facebook or the myriad other things people do online, that’s what a netbook is for. And for the situations where netbooks are useful/intended, Chrome OS is a great operating system for that netbook to use.

“What if I don’t want all of my data on the cloud? What if I want to control my data?” Really, this argument is a variation of the first one; if you’re not the type who has your data on the cloud, then Chrome OS isn’t for you. But are you sure you don’t already have your data on the cloud? Maybe you’re not using Google Docs or Google Wave, but don’t you use Gmail, or Hotmail, or Yahoo mail? Or Facebook? For that matter, I bet even your email acount from your ISP, and even your corporate mail servers, have web-based interfaces that you can access. I have ten email addresses that I can think of off the top of my head, including my work addresses, and they’re all either web-based, or accessible by the web. But set aside the idea of having your “data” on the “cloud,” because it just clouds the issue when you start thinking in terms of information and data. The real question is: How much of your time do you spend browsing the web? You can use a netbook running Chrome OS and never touch a Google site like Gmail or Google Docs or Google Maps; if you’re in a situation where you just want to browse the web, and that’s it, that’s what netbooks are for, and, again, I think Chrome OS is a great operating system to use for that netbook. For anything else, use a real computer, and by all means, don’t use a browser for everything.

So that’s my longer-than-necessary post on Chromium OS. A lot of this post focused on speed, rather than the features of the OS, but that was on purpose, because speed is the main driving force behind Chromium OS. It is, after all, as close as possible to being just the Chromium browser, with as little “operating system” as possible getting between you and the internet.

Monday, February 08, 2010

Google Wave In Use

Here’s a video from Salesforce.com, showing a great way that Wave technologies could be used in a customer service manner.

Monday, February 01, 2010

Skip Intro

There are a lot of websites out there that start off with a Flash animation introduction, and then somewhere on the page—usually right under the animation—they have a link that says “Skip Intro” for those who aren’t interested in the animation. Well Google has introduced an interesting feature to their search results; see the first item on the screen:



Such a simple feature, but I bet I’ll be clicking that every time I see it, instead of the regular search result.

I wonder if people will now be looking for ways to get around that, so that people won’t bypass their animations from the Google search results? Then again, if they already have the ‘Skip Intro” link on their site, then maybe they wouldn’t care if people bypassed it directly from the Google search results; they’re trying not to annoy people who don’t want to see the animation, so people will be even less annoyed now.

Friday, January 29, 2010

Prescience

I have to admit to rarely having been very prescient about new technologies. I understand technology very well, but when it comes to predicting what will take off and what won’t, I’m often off the mark.

Some examples:

  • I never thought Facebook would take off the way that it did. I figured it would be very popular for a while, and then everyone would move onto something else, as they did with MySpace and the various other social networking sites that had come before it. But the Facebook API (among other things) proved me wrong, and, despite my predictions, it’s still quite popular.
  • I underestimated how popular the iPhone would be, and then overestimated how popular the Palm Pre would be. In a radius of twenty feet from where I’m currently sitting at work there are probably a dozen iPhones, but not a single Pre. (Despite the fact that the Pre keeps winning awards for being so darned great.)
  • I was initially right about the Y2K bug, but then gave in to the hype and became as wrong as everyone else. When people first started talking about the Y2K problem, I said, well, it’s no big deal; maybe some reports will be wrong, and say 1900 instead of 2000, but other than that, problems will be extremely rare. If I’d stuck with that, I could have claimed I was prescient, but eventually all of the people who claimed that the sky was going to fall got to me, and I started to think it might actually be a big problem—only to have the clock turn over at 2000, and nothing happened, as I’d originally predicted.
  • I’ve written before (I think) about the fact that I never really cared when Google was launched. Big deal, another search engine, who cares; I already have my hierarchical list of sites on Yahoo!, what do I need another search engine for? Here we are today, and Google is so useful that many if not most people use it for their default page when they load their browser.
These are some examples; there are others. And here are two more.

I’ve already written about Google Wave, and how I think it has the potential to be a paradigm-shifting technology, which might, in time, replace email. (And IM. And documents—but now I’m really dreaming.) And I’d like to be right about it—if only so that I could claim I was prescient—but everyone else seems kind of underwhelmed by it. (Someone described it to me recently as “a solution in search of a problem”—I’m not of that opinion, obviously, but I can definitely understand the sentiment.) There’s still time, don’t get me wrong. I haven’t lost hope in it. But I would feel better if others were sharing my enthusiasm, and as of yet, they’re not.

Then, yesterday, Apple launched the iPad, which is a tablet-sized device, kind of like a big iPhone. And I’m seeing a lot of hype about it, but I’m thinking… so what? It’s a tablet. Big deal. It’s an iPhone, but bigger. (Or, if you get the version without 3G, it’s an iPod Touch, but bigger.) There have been tablets before, and none of them have ever taken off, because people don’t seem to want to use their computers like that. In fact, I remember when I first heard about Tablet PC from Microsoft, and, in another case of non-prescience, was very excited, assuming that it would be the next big thing. Here we are a few years later; have you ever met anyone who had a Tablet PC? I haven’t. I just did a Google search for “Microsoft Tablet PC”, and on the first page of results, the only pages on Microsoft’s site were one in Taiwanese, and one from Microsoft Support, so it’s not exactly a feature that Microsoft is pushing hard. So I’m not seeing the big deal about the iPad, but who knows? Maybe Apple will have implemented it in such a way that people really will find it useful. But at this point, I’m thinking that I’d rather be using a netbook than an iPad.

I should mention that some people have similar feelings about “netbooks.” Who would ever want a netbook, they ask; why not use a laptop, if you want a laptop, or your phone, if you want portability? I don’t agree with them on that; I think that netbooks actually are a good idea, for a lot of situations (and am kind of excited about Google Chrome OS). I think there’s a good market for an in between device, that’s more comfortable than a phone, but just for browsing the web and checking email, therefore not requiring the power (or cost) of a real laptop. (I wasn’t prescient or non-prescient about netbooks; by the time I’d even given them any thought, they were already very popular.)

So I’m thinking that Google Wave is going to be revolutionary, but, based on my history of trying to predict the future, am probably wrong. And I’m thinking that the iPad is no big deal, but for the same reasons, am probably wrong.

Friday, January 15, 2010

Google Web Tools

A while ago I had a post in my Beautiful Code series, on Computer Generated Code. There, I was referring to things like the C pre-processor, which runs through a source code file and generates additional source code, which is finally sent to the compiler. Or, in more extreme cases, using another tool altogether, like awk, to do the same thing, but with potentially a lot more flexibility (with the power of regular expressions at hand). These days Java programmers are doing something similar with Annotations. The article also mentioned code that generates further, optimized code.

Last Fall, I came across a variation on this, in the form of the Google Web Toolkit (GWT), which is a set of tools created by Google for creating rich HTML-based applications, specifically ones that make use of JavaScript and AJAX and JSON to do complex things in the browser.

One of the disadvantages to using a scripting language like JavaScript for development is that it is not a “strongly typed” language, and neither is it compiled, so some development errors will not be discovered until the testing phase. With a compiled, strongly-typed language (such as C++ or Java), some errors can be caught at compile time and fixed quickly, which reduces the number of bugs to be discovered during the testing phase. Another issue is that things often work slightly differently from browser to browser, so often you find yourself building JavaScript code that does things like, “if Firefox do this, but if Internet Explorer version 6, do that, but if IE7 do the other…”

GWT tries to combine the benefits of using a strongly-typed language—in this case Java—with the aforementioned benefits of improved user interface via AJAX. In a GWT application, code is written in Java, and UI is built using a GWT library, very much in the same way that a Java Swing application would be built. Once the application has been built and tested, it is “compiled” into JavaScript, with versions optimized for various browsers. In other words, a version is produced that will be optimized for IE6, and another version for IE7, and another for Google Chrome, and another for Firefox, etc. When the user accesses your application, the GWT JavaScript runtime figures out what browser you’re using, and downloads the correct code (and only the correct code) for your environment.

In addition, any JavaScript which is created is also optimized, whereby extraneous whitespace is removed, comments are elided, and even variable names are shortened; by compacting the JavaScript in this manner, it’s quicker for the browser to download the code, which improves performance even more. For example, a JavaScript function that might normally be written like this

//adds two numbers together, and returns the result
function addTwoNumbers(firstNumber, secondNumber) {
addedNumbers = firstNumber + secondNumber;
return addedNumbers;
}
Might end up looking like this, instead:
function a(a,b){c=a+b;return c;}
Obviously the first version is easier to read, and therefore easier to maintain. As a developer, I would never write code like the second version. But because JavaScript is a scripting language (meaning that it is not compiled into machine language, it is interpreted by the scripting engine at runtime), it means that every byte from that first version gets sent across the network to the browser, comments and whitespace and all. The second version, however, is much smaller, meaning that it will take less time for the browser to download it over the wire. (In this case, the optimized JavaScript is 32 characters, vs. 177 characters for the more maintainable version—something like 82% smaller. Code with a lot of whitespace and comments, and code with long variable and function names, will end up looking a lot smaller in the optimized version, because there’s more stuff that can be stripped out and reduced.)

With GWT, we get the best of both worlds, because the developer works with easy to read, maintainable Java code, but the GWT “compilation” process spits out the more optimized version in JavaScript, to send across the wire.

A typical GWT development lifecycle will be similar to this:
  1. Developer begins developing in Java, using the Google Web Toolkit (quite probably in Eclipse, using the GWT Eclipse plug-ins)
  2. Developer tests code using the provided runtime; at this point the code is still Java code, allowing the developer to set breakpoints and debug
  3. Once the development is complete, the developer “compiles” the GWT application, to create the JavaScript, HTML, and CSS files
  4. These JavaScript, HTML, and CSS files are included in the larger web application
Of course, as development proceeds, the developer may be repeating steps 2–4.

The GWT compilation process can be controlled using normal Ant built scripts, so the overall build process for Java applications can be modified to include a build of the GWT code, and inclusion into the appropriate location in the larger WAR/EAR. For non-Java projects, you can simply “compile” your GWT code, and include the generated files (HTML and JavaScript and CSS and images) in your application.

It’s similar to what we talked about in the Computer Generated Code post; the code that you maintain, and actually work with as a developer, is strongly-typed, clean Java code, with all the comments and whitespace and readable variable names that you are used to. But the code that is actually produced for use at runtime is highly optimized, unreadable code, intended to be seen only by a machine, not a human.

The limitation will be how good GWT is at turning your Java code into JavaScript code. When I did a Proof of Concept application back in the Fall, for an AJAX application we were intending to build at work, I did two versions, one in “raw” JavaScript, and another using GWT. I found that the performance of the “raw” version was better than the GWT version—but, that being said, because of the nature of the GWT libraries, I ended up having to change how I did some things, so it’s not like the code was the same in both cases. It wasn’t a strict apples-to-apples comparison.

For the real application, we decided to use GWT anyway, though, for two reasons:
  1. Our developers are more familiar with Java than JavaScript, so the benefit of maintaining Java code instead of JavaScript was a big one. Especially since the application is a Java EE application; our Ant scripts could simply be updated to include steps to compile the GWT code, and then copy the resultant output files into the main application’s WAR file.
  2. A lesser reason is that there is a possibility that further optimizations might be introduced to GWT, improving the way it produces its JavaScript code. It’s possible that an updated version of GWT might produce even better JavaScript output. (Although it may also force us to change the way that we write our Java, so we can’t expect it to just magically make our code faster.)
GWT has been used to build numerous products/projects—including Google Wave, I might add—so it’s being used by real people to solve real problems. But there are also people who are skeptical about it, and when I was researching the best AJAX libraries to use for my project, I saw mixed reactions to the GWT way of doing things. However, I think it’s another great example of doing something similar to what we discussed in the Computer Generated Code post. Writing code in a manner that is more developer-friendly, and outputting code that is more machine-friendly (and, in this case, network-friendly).

Saturday, January 09, 2010

Google Wave

It’s been a while since I wrote a fawning post about how great Google technologies are, so it’s time I remedy that, and write a new fawning post about how great Google technologies are. Enter Google Wave. I started reading about it yesterday, and I think—I’m not sure, but I think—that I’m going to be blown away by this technology.

In a nutshell, Wave is a mashup of email, collaborative document writing (a la wikis), and instant messaging. In some ways this is simply incremental change to existing technology, but I think it’s one of those new ways of looking at things that has the potential to be a paradigm shift. To see what I mean, let’s take a very abbreviated look at the history of documents, email, and instant messaging:

  1. In the olden days, before computers were invented, people used to write documents using a pen, or with a typewriter, or using similar technologies. If they wanted to send a copy of that document to someone else, they would bring it to them, or send it by mail. That person, when they’d received the mail, could read the document, and mark it up using a pen or pencil, and mail it back to the original person. S/He could read those changes, and, if s/he so wished, write/print/type up another version of the document, incorporating any of the changes that s/he wanted to incorporate. If the people needed more immediate feedback than mail could provide, they could use a technology called the telephone to talk to each other, over great distances, for immediate feedback.
  2. Computers brought electronic versions of these technologies. Word processors and spreadsheet programs and presentation software replaced paper documents (or, at the very least, made it easier to create them—people still had a habit of printing them out, from time to time). Electronic mail, or email, replaced mail. We developed something called instant messaging for immediate communication, for those times when email was too slow, so that we can have a real-time conversation.
  3. These technologies changed how we communicate; instant messaging is largely replacing phone calls, even as it incorporates phone-like features (like voice chat) and improves on them (like video chat). Email is largely replacing physical mail, and the contempt we have for the speed of physical mail is apparent in its new moniker, “snail mail.” Email also changed the way that we correspond with each other; when you send an email, you can send it to multiple people, and when one replies to an email, the reply usually incorporates a copy of the original email, so that a conversation can be maintained. Email introduced the concept of reply all, which means that everyone can be included in the email conversation, and provide their input (if necessary). Emails can also be forwarded to others, even if they weren’t originally included, or, when replying to an email, you can simply add new people to the reply, if you think they should know about the conversation that’s happening.
  4. These technologies also changed the way that we wrote documents; with the ability to do everything electronically, we now had the ability to email a document to someone else, as an attachment, for them to read electronically, and then send a reply email back, with their comments on the document. Electronic documents made it much easier to incorporate changes, rather than having to write or type out another version of the document by hand.
  5. Soon the people making word processors and spreadsheets and presentation software started incorporating features into their products that made it even easier to do this. Things like track changes and the ability to add comments made it very easy to see what changes others were suggesting, and software got very good at merging different versions of documents together, even tracking who had made what changes.
  6. Looking for a way to keep our documents together in one place, people began creating document repositories. More than just a glorified file folder, these repositories included features like having multiple versions of a document, and workflow capabilities, and the ability to lock a document while editing it, so that nobody else can, until you’re done and you “check in” your changes.
  7. Even with these advances in editing, some people felt it wasn’t enough, and the wiki was born. A wiki was a web site that anyone could edit, and in some ways strove to replace the document. The obvious example is Wikipedia, the online encyclopaedia that anyone can contribute to, but wikis have also been used for things like documentation for software projects. (Rather than having a series of documents that must be kept up to date, the documentation for the project is a [potentially] always up to date web site, that can easily be searched and updated.)
  8. Despite the advent of the wiki, the vast majority of people were still creating documents, and emailing them back and forth as attachments, and using their track changes features to make changes. (Or they were simply replying to the original email, and saying things like, “You spelled a word wrong on page 4, paragraph 6. The diagram on page 9 is incorrect.”) Then Google came along with Google Docs, and gave us technology to put a document online, and let multiple people edit it at once, collaboratively. Google Docs turned documents into mini wikis. Now, instead of emailing a document as an attachment, for the person to edit and send back, forcing you to incorporate the changes, you would simply email (or IM) a link to the document, and the person would edit the document itself.
And this is about where we stand today. Wikis still exist, but aside from Wikipedia, they aren’t that prevalent. Despite the fact that I and others like me think Google Docs are cool, most of us (including myself) are still using applications like Microsoft Office to create our documents, and most of us are still using email to add these documents as attachments, to send to others. Interestingly even when we have a document repository—like Sharepoint, for example—we’re often still sending the documents as attachments; we could just send a link to the document in the repository, but in many cases someone doesn’t have access to the repository, and the document author usually isn’t the repository maintainer, so it’s much quicker to just email a copy of the document than to go through the red tape of getting the person granted access to the section of the repository that they need, to read the document. Email is, by far, the most prevalent means of communication, but instant messaging has also become an indispensable tool, both for work and personal use.

But still, even with the advances in technology we’re down to email (a replacement of snail mail, with some obvious improvements), instant messaging (a replacement of the telephone, with some obvious improvements), and electronic forms of documents (with some obvious improvements in how they’re created, but still, at the end of the day, are very much centred around the end product: the document.) Wikis are on the fringes, as a potential replacement for documents, but they haven’t gained traction as such.

So all of this to say, what is Google Wave? As mentioned, in some ways, it’s incremental technology, combining documents, email, and instant messaging into one technology. That was my first thought, when watching the hour and twenty minute long video where it was introduced. (Just in case that link expires, here’s the direct link to the YouTube video.) You can create a document, and multiple people can collaborate on it—just like Google Docs, you might say. You can receive notifications in your “inbox” when there are changes—just like in email, you might say (with a bit of an improvement). If people are online at the same time, you can see the changes they’re making as they make them, and you can send each other messages—just like instant messaging, you might say. Just like email, you can send someone a message, but when they respond to that message, they’re not limited to the usual message/response format we’re used to for email.

But here’s where the paradigm shift came in for me: email, documents, and instant messaging are all electronic versions of things we already used to do; with Google Wave, we have a potential replacement for email, documents, and instant messaging, creating a new paradigm that’s based on what computers can do, instead of simply trying to do the same old things we always did, with incremental improvements. (See this post on the Google Blog for an expansion on this.) With Google Wave, the line between an email and a document and an instant messaging conversation becomes blurred; what, really, is the difference between an email and a document? For the most part, just the length, and the means by which one can share it.

Today, when I want to communicate with someone, I have a few options:
  • For a quick conversation with a quick answer, I can open my IM client, see if the person is online, and start a conversation. If I want, I can include multiple people in the conversation (although most IM clients will limit this to around a half dozen people or so).
  • For something a bit more detailed, I can write an email, and send it to the person or people I want to communicate with. They can read the email, or, if required or desired, they can respond to it, and add their thoughts or make corrections on my original thoughts.
  • For something that I want to make more permanent and/or official, I can write a document, and email it as an attachment or put it in a document repository. Others can read the document, and, if required or desired, they can send an email back to me, with their thoughts or corrections. If they have permission, maybe they can edit the document itself, in the document repository, and their changes will become part of the document.
Three different ways of communicating my ideas, depending on the nature of those ideas. With Google Wave, all three of these would be something called a wave. I want to communicate something to a person or people, so I create my initial communication, it shows up in their inbox, and they can communicate back in the manner that they see fit; changes to the content, comments off to the side of the content, private messages to some people who are part of the wave but not to others… whatever makes sense. If the conversation becomes detailed/important enough, it will be shared and seen by more and more people, just like a document might in today’s world. If not, it might be a simple short communication between two people, just like an IM conversation might in today’s world.

We currently have three levels of “permanence” for our communications, from the throwaway IM conversations to the slightly more permanent emails—which are still locked in our inboxes, to be seen only by us and people we forward the emails to—to documents, which become artefacts and semi-permanent records of our thoughts or findings on a subject. Waves make these distinctions obsolete, and the only distinction in the wave world is how many people the information is shared with. (One question in my mind, however, is whether waves will have the immediacy of instant messaging; I can easily see that we might no longer need a distinction between email and documents, but when I get an IM, in today’s world, it’s something immediate, that I respond to immediately; will that still be the case, if it’s just one more wave hitting my inbox? I’m not sure.

Email has been around since the beginning of the internet, and, as mentioned, is the most prevalent form of communication on the internet. With Google Wave, we may have a serious contender for a new form of communication, with the potential to replace email. We may also have a new way of doing wiki-like things that will be more popular than wikis ever became.

It should also be mentioned that Google is doing this all open source, and creating generic protocols that can be used; this isn’t just a closed system, where you’d have to sign up with Google to get access. You can create a corporate “wave server,” similar to how we have corporate email servers today. And, just like email today, you’d have the ability to add people to your waves that aren’t on your corporate wave server (just like you can send emails to anyone on the internet), but also not give them access to waves that they shouldn’t have access to.

Unfortunately, Google Wave isn’t yet completely open to the public; you can just sign up, and they’ll let you know when you can join. So I’m going to sign up, and play with it when they let me in. Of course, it won’t really do me any good until I know someone else who uses it.

Friday, December 18, 2009

Backing Up Your Data

There seems to have been a bit of a meme going around lately about backing up your data.

The first post I read was from Joel Spolsky, advising that talking about backups isn’t good enough, we should be talking about restores.

I then read a post by Jeff Atwood about his recent horror story in losing a ton of data from his blog, because of a lack of backup strategies, and then another post by someone else (whom I can’t currently remember) which was similar to Atwood’s, in that they lost a bunch of data from their blog because they hadn’t backed up. (And reading between the lines, I think Atwood felt even more stupid, because of a previous post of his, in which he outlined an extremely simple, yet effective, backup strategy.)

All of these posts seem to be telling me something, and telling me loud and clear. And yet I’m still not backup up my data.

Oh, that reminds me. My pastor sent an email yesterday, asking how to do something on the church web site, and I sent him some instructions, which may or may not have been clear; maybe I should back that up, right now before even clicking Submit on this blog post, just in case things go badly…

There. That only took a second. I should do that more often.

Wednesday, November 18, 2009

Software serna Loves: MSN Messenger and Google Talk (and Pidgin/meebo.com)

You might be surprised to see Microsoft software on my list; I’m a bit surprised too. But I have to admit: I really like MSN Messenger. I’ve also been using Google Talk, a bit, and like it too. (Except that they still have a bizarre problem where you can’t use it without using a Gmail account.)

Part of this isn’t anything specific to MSN Messenger or Google Talk, though; part of this is just a fascination with chat software in general. They don’t call it “instant messaging” for nothing—there is a part of me that still gets a sense of childlike wonder that I can type something into my chat client, hit Enter, and have those words show up instantly in someone else’s chat client. In fact, I remember when I first started using MSN Messenger, and all of the people around me at work always had their sound on, so when I’d log in first thing in the morning I could hear all of their chat clients pinging to indicate that I’d just come online, again, virtually instantly. I work with people in various offices here in Toronto, people in Montreal, people in Québec City, and people in India; if we didn’t have chat software—primarily MSN Messenger—I can’t imagine being as productive as I am.

Now, this is normally where I’d start talking about the features I like about a particular piece of software, but honestly, when it comes to instant messaging, I don’t need or want a lot of features. Really, there are just two things I care about: it should be easy to chat, and it should be easy to send/receive files. (And even sending/receiving files is more of a convenience than anything; if I have to, I can send an IM to tell the person to check their email.)

It’s nice to be able to create a display picture, but not essential. It’s nice to be able to set a status message, but not essential. (Although we sometimes use the status messages in MSN for work; if I scan down my contact list, I’ll usually see a number of people with statuses that say things like “working from home this morning” or that type of thing.) It’s fun to be able to use emoticons—and even custom emoticons—but again, not essential. MSN Messenger has emoticons and custom emoticons, and when I use that I use a lot of emoticons in my chatting, but Google Talk doesn’t have emoticons, and I don’t miss it at all. (Maybe that’s because I’m an old-school chatter; it took years for my MSN Messenger buddies to get me to even turn on my emoticons, let alone start using them heavily.)

One feature I’m surprised I don’t use is the ability to do video chatting. This is a great feature, in theory, but I’ve never actually used it. Both MSN and Google can now do video chat—even the web-based version of Google chatting can do video conferencing (I’m not sure about the web-based versio of MSN). Maybe if I ever get a laptop for work that has a webcam built in I’ll start using it, but something tells me that even then, I probably won’t.

In terms of interface, I think I like Google Talk better than MSN Messenger because it’s cleaner and simpler (and doesn’t have advertising!), but both get the job done in much the same way:

  • If you want to chat with someone, simply double-click their name in your contact list, and up pops a chat window.
  • Chatting is simply a matter of typing your message, and hitting Enter to send the message to the other person or people. This bears mentioning because one of the first chat clients I ever used was called ICQ, and you used Ctrl+Enter instead of Enter, which wasn’t quite as satisfying. Based on my previous post on IrfanView, it’s no surprise that I like the simplicity of just hitting Enter to send the message. (Ctrl+Enter makes it seem more like an email than an IM message. You shouldn’t have to put that much thought into an IM message; just type as fast as you can—without worrying about spelling—hit Enter, and be done with it.)
  • Along the same lines, when you’re done with a chat, simply hit Esc to dismiss the chat window, and it will disappear.
  • If you want to send a file to someone, simply drag it to the chat window. If someone sends you a file, it will show up as a link that you can click to either accept or ignore, and when you accept the file will begin downloading to your computer.
  • Although they have different ways of doing it, both MSN Messenger and Google Talk will notify you when you get a new email to your Hotmail or Gmail account (respectively). That being said, MSN Messenger seems to integrate much better with Internet Explorer than any other browser (surprise surprise), while Google Talk doesn’t care what your default browser is.
In terms of differences between the two:
  • In MSN Messenger, you can add multiple people to your chat conversation; I don’t think you can currently do that in Google Talk.
  • Google Talk has a nice “windowshade” feature, where you can click the titlebar of your chat window, and the window will “roll up” into the titlebar so that that’s all that’s showing. (Clicking it again will “unroll” the window so you can see it again. When you have the chat window rolled up like that, you can still see the last message the other person has sent to you, so you can do this to free up some real estate on your screen, but still easily continue the conversation when necessary.
So similar to my post on IrfanView, what I really like about my chat clients is that they don’t get in my way, and they just let me get on with my chatting. This is especially important at work, where the whole point is that you want to get a quick answer to a quick question, and then move on. Something like this:

sernaferna says:
How big do the log files get before rolling over?

someone else says:
5MB

sernaferna says:
thx!

someone else says:


Then you’re done; hit Esc, the chat window goes away, and you go on about your day. Not only is your answer immediate (unlike email, where you may have to wait a while for the person to respond), but you also don’t have any extraneous emails sitting in your Inbox or your Sent Items. I don’t know about you, but if I were to have this conversation over email, I may or may not delete the emails I got from the other person, but I’m sure I wouldn’t go back and delete the ones I’d sent from my Sent Items—but those are emails that I would never, ever need to go back and find. (And since most people compose their emails in HTML these days—plus have signatures automatically appended to their emails—the size of those emails can get crazy; looking through my Sent Items, I didn’t see a single email that was less than 3KB, whereas the entire fictional conversation above would have been about 65 bytes going across the wire.) Better still, your chat client can tell you if the person is currently online, and if they’re not, you can look for someone else who is, and get your answer from them.

Now, I’ve talked about MSN Messenger and Google Talk, but there’s a special mention I’d like to give, to Pidgin (and, by extension, meebo.com). I won’t go into too much detail on Pidgin, because I’ve already mentioned it on this blog, but it really is nice to be able to combine multiple chat accounts together in one interface, even if that interface is a bit more clunky than either MSN Messenger or Google Talk. And the aforementioned usability is all there for Pidgin, too: double-click a person’s name to chat; Enter to send message; Esc to dismiss the chat window; etc. Pidgin also has a spell check feature, which I always thought I would like in a chat client—I’m fairly anal retentive about my spelling, even in chat—but now that I have it, it turns out I don’t care that much. And although I personally haven’t used meebo.com, I have a colleague who uses it all the time, and says its great.

Tuesday, November 17, 2009

Comments

I’ve suddenly started getting a lot of spam comments in my various blogs, so I’ve taken the step of turning on the “word verification” feature for commenting. In the past I didn’t bother; whenever I got a spam comment I simply deleted it, and that was that. But lately I’m getting enough of them that it’s gotten annoying, so I’ve done this.

For the very, very few people who comment on my blogs, I apologize for the inconvenience.

Monday, October 19, 2009

Software serna Loves: IrfanView

IrfanView is a free image viewing application. It can also be used to edit images—and in fact has some pretty great editing features—but it’s primary purpose is for viewing. It’s named after its creator, Irfan Skiljan.



What makes IrfanView great?

First of all it’s fast. For all of the image types I’ve tried it on (JPG, GIF, bitmap, PNG, etc.), when you open an image in IrfanView, it opens instantly. There’s no millisecond or multi-second delay, as you wait for the program to initialize itself, or load libraries—just double-click the image, and IrfanView is there, showing it. Even for a very large image, which IrfanView might have to resize for you, it’s still much faster than any other image viewing application I’ve used. If all you want to do is look at an image—and that is probably what you’re doing, much more often than editing—having it load up quickly is a big benefit. In fact, even the “filmstrip” view, built right into Windows Explorer—which caches all of the images ahead of time—is only marginally faster for really big images, even with its cache, and is actually slower for medium or small images.

This makes IrfanView feel “lightweight.” I don’t have to hesitate before opening an image file, even a really big one, because there is no penalty for doing so; I won’t lose a ton of memory, my CPU won’t go crazy, and I won’t have to waste time waiting for the image to appear. If I want to open a Word document, or a Visio drawing, I might have second thoughts, and only open it if I have to, but I don’t have to give such considerations to opening an image.

Earlier, I mentioned resizing, and this is another handy feature built into IrfanView. You can tell IrfanView how you want to view the images that you’re opening, meaning:

  • Fit window to image (also called 1:1 ratio). The image will be shown at its normal size, with no scaling applied; if the image is small the IrfanView window will shrink down to the image’s size, and if it’s very big IrfanView will grow to the size of your screen, and give you scrollbars to see whatever doesn’t fit on the screen.
  • Fit images to desktop. IrfanView will size itself as big as your desktop, and if the image is very small it will be resized bigger to fill the screen, or if it’s very big it will be shrunk to fit on the screen. (Because of the nature of this type of activity, obviously small images can get very distorted when they’re expanded this way; medium-sized pictures—especially photographs—sometimes don’t look too bad. Sizing larger images to be smaller, however, gives very good results.)
  • Fit images to window. Similar in concept to fitting the image to the desktop, but fitting the image to whatever size your IrfanView window is. This is the only option in which IrfanView will not resize its window to the size of your image or your desktop.
  • Fit only big images to desktop, or Fit only big images to window. Similar to the above, in which very big images will be resized to fit the screen (or the window), but small images are left as they are.
There are some other options too, but these are the main ones. Personally, I usually have IrfanView set to “Fit only big images to desktop”; usually, if I’m looking at an image, I’d prefer to see the whole thing at once, but that doesn’t mean that I need smaller images expanded. And, as mentioned, you get very good results when you shrink an image to fit the desktop, it doesn’t become distorted or anything. If I ever change my mind—for example, if I want to see all of the details for a large image, and want to use the 1:1 ratio—it’s a simple menu to change the way I’m viewing the image, and IrfanView will remember the setting the next time I open it. I don’t have to open a Preferences dialog, and make the selection there, and click OK to save my settings; just change the view, and it’s done. Also, because of the speed of the application, there’s not a noticeable performance impact to having IrfanView resize the image.

If I ever want to zoom in or out of a an image, without changing IrfanView’s overall setting for viewing images, I can use the + key to zoom in or the - key to zoom out. (Or, if I want to look at a specific portion of an image, I can select it with the mouse, and then click the selected portion. IrfanView will crop the image to show just that section. It’s not a “permanent” crop—it doesn’t actually edit the image itself—it’s just for your viewing pleasure. You can “reload” the image to see the full thing again.)

This next feature might not seem like such a big deal, but it’s part of the overall lightweight feel IrfanView has: Pressing the Esc key closes the application. To me, there is just something so simple and elegant to pressing the Esc key, and having the application go away. It goes along with what I was discussing earlier, that you don’t have to think before viewing an image in IrfanView. Double-click it, look at it, and hit Esc. In your mind, all you’re doing is “looking at an image”; you’re not “opening a program”, and “selecting a file”, and “closing the program”. If you’re having large images scaled down to fit your desktop, you’re not even “using the scrollbars”. You’re just looking at an image, and IrfanView is not making itself known in the process. You can close any program using the keyboard—Alt+F4 will close any program in Windows—but there’s something holistic about a lightweight image viewing program that lets you simply hit Esc to dismiss it. In fact, maybe “dismiss” is the operative word here—you’re not “closing a program” you’re “dismissing” the image you were looking at.

A similar feature is the ability to do an impromptu slideshow, using the left and right arrow keys on the keyboard. If you have multiple images in a particular folder on your computer, and open one of them in IrfanView, you can use the left and right mouse keys to view the next and previous one. (In other words, double-click the first image and it will appear in IrfanView; press the right arrow key, and IrfanView will show the next image; hit the left arrow key, and the first image will be shown again.) Most image viewing applications have a slideshow feature—and IrfanView does as well— but there’s something so intuitive about the ability to simply view the next image by hitting the arrow key. Personally, I never use the slideshow feature in any image viewing program, even IrfanView, because I find it so much easier to simply scroll through the images myself, at my own pace, instead of after a predetermined number of seconds. (Inevitably, when using that type of slideshow, I find myself having to manually go back and look at an image, because the slideshow moved on before I was done looking, or find myself impatiently waiting for the next image to appear when I don’t care much about the current one.) I suppose if I were doing a tradeshow it might be nice to have images automatically scrolling past the screen as eye candy, or maybe it would be nice to have something like that playing at a party (maybe with pictures from a recent trip), but for my own use, I simply use the left and right keys.

Along the same lines, you can view an image in “full screen” mode—meaning that only the image will be shown, not the rest of your applications and your Windows taskbar and your desktop—by simply hitting Enter. Again, so elegant! When you’re done with full screen mode, hitting Esc again will bring it back to normal. (As with using the regular window, you have options as to how you want the pictures to be scaled (or not scaled) in full-screen mode, but in this case there is no menu, so you really do have to use the Preferences dialog to set this.)

Now, although IrfanView is primarily built for viewing pictures, it has some editing features that I’ll just briefly mention:
  • Of course it can easily crop images, but so can any image manipulation program out there, and most image viewers. (I mentioned the ability to “temporarily crop” an image for viewing, but you can do a “real” crop as well, and save your changes.)
  • It has the ability to do a batch rename of a bunch of pictures. For example, suppose you go on a trip to Florida, you get all the pictures off your camera, and have them in a directory, but they’re all named something like IMG00079.jpg, IMG00080.jpg, IMG00081.jpg, etc. You can use IrfanView’s batch rename function to give them all more meaningful names; maybe Florida_01.jpg, Florida_02.jpg, Florida_03.jpg, etc.
    • For a simple rename of one particular file, another handy keyboard shortcut: simply hit the S key, and IrfanView will bring up the “Save As” window, so you can give the image a new name (or save it in a different format; e.g. you could use this to convert a JPG to a GIF.)
  • You can very easily rotate an image, using the R and L keys (to rotate right and left, respectively), for those cases where you tilted your camera to the side, so your pictures are sideways.
  • There are many settings for adjusting the brightness or contrast of the picture, editing the colour scheme, applying effects like blur, etc.
  • Similar to the batch rename feature, I can also generate a set of “thumbnails.” If I have a number of images in a directory, I can have IrfanView go through that directory, and for each image, it will create a “thumbnail” image—a smaller version of the image. This might be useful if you were creating a website, and you wanted to have small previews of the pictures, and when someone clicks the preview you show them the real, full-sized image.
  • Finally—and I never discovered this feature until I was writing this post!—IrfanView can do screenshots which include the mouse. It’s very easy in Windows to do a screenshot—use the PrtScn key to get the whole desktop, or Alt+PrtScn to get just the active window—but you can’t get the mouse that way. If you want to get a screenshot which shows the user using a particular menu, for example, you can’t do it. So until now, I’ve been using other programs like Snagit for that type of work, but they cost money. I’ve now realized that IrfanView can do it too, and it’s free.


I’ve mentioned the simplicity of the keyboard shortcuts a couple of times; maybe you’re wondering why I think it’s such a big deal that you can rotate an image right in IrfanView by hitting the R key, instead of Ctrl+R or Alt+R. Why I’m so thrilled to be able to close the application using the Esc key, instead of Alt+F4. (Of course, you can still use Alt+F4 if you want to.) The thing is, it really is useful to have the keyboard shortcuts in IrfanView so simple, and every application would—the only reason most applications don’t do this is because they can’t. Almost all applications require a combination of the Alt key or the Ctrl key and some other key for their keyboard shortcuts because the keyboard is usually being used for other things, so you have to differentiate the user typing from the user entering a command. But for an image viewing program, you’re not using the keyboard for anything; any time you hit any key, it’s a command. The thing is, developers are so used to using Alt and Ctrl for keyboard shortcuts that even for other image viewing programs, they do the same thing—Irfan had to think outside the box not to use Alt and Ctrl (in most cases), and I’m glad he did. The only time he resorted to using Ctrl or Alt or Shift is when a shortcut key was already taken, and he had to differentiate. “I’d like to use R to ‘reload’ an image, but I already used R for ‘rotate right’ so I’ll use Shift+R to ‘reload’ instead.”

In summary: IrfanView is a lightweight image viewing program which doesn’t get in the way, and does everything possible to make it easy to view images. And yet, even with its simplicity, it also provides some powerful features for day-to-day image editing. It’ll never be Photoshop, but of course it doesn’t try to be.

It took me a while, on Ubuntu, to find a comparable image viewing application. I didn’t even care about editing—I’d use GIMP if I had to edit anything—I just wanted a lightweight image viewer, that I could dismiss with the Esc key and navigate back and forth with the left and right arrow keys and go to fullscreen mode with the Enter key. (In other words, I wanted IrfanView for Linux.) I finally did find such a program, and it’s GPicView. It’s even more lightweight than IrfanView, in the sense that there are no editing capabilities, although it doesn’t make it any quicker to load than IrfanView. (You use F11 to go full-screen, instead of Enter, but that doesn’t matter—it’s still just one key, rather than a multiple-key combination. It even lets you rotate left and right using the L and R keys, just like IrfanView!)

I highly recommend IrfanView for day-to-day viewing of images. Any time a program can get out of the user’s way, and simply get its job done, it’s well worth the download. The fact that it’s free, lightweight, a small download, and has never caused me any issues after years of use are all additional points in its favour.

Software serna Loves

sernaferna PermaPost

I’ve been thinking about this for a while: I’m going to do a series of posts on software that I enjoy using. There’s a lot of software that I use every single day because I have to, and some is good and some isn’t. For example, I have Microsoft Outlook running at all times; as soon as I boot up my laptop in the morning I open it, and it’s the last thing I close when shutting down. Outlook is a great PIM application, which I use both at home and at work, and I’ll probably continue to stick with it (when I’m on Windows)—but it won’t make this list. This list is for software that goes above and beyond.

There are some programs that are just so well designed, so well done, that I really enjoy using them. These are the programs that I immediately install whenever I get a new computer, because I don’t want to live without them. Maybe they make my life simpler, or maybe they’re just easier to use—or more enjoyable to use—than their counterparts.

In other words, this will be a series of posts in which I unabashedly gush about certain programs.

Here’s the list (which will grow, as I add posts):

Wednesday, October 14, 2009

On Obama’s Nobel Peace Prize

There’s been a lot of discussion lately about the fact that Obama won the Nobel Peace Prize. It’s the rare sort of issue that unites both liberals and conservatives: “Barack won the Nobel Peace Prize?!? He hasn’t done anything!” And I don’t have much to add to that. But I will quote a post on The Nation’s blog, from Katrina Vanden Heuvel:

I think those who argue that the Prize is cheapened are just plain silly. The Prize doesn’t go to only those who have succeeded in their efforts, nor is it a lifetime achievement award. Instead, it is often and wisely given to endorse and encourage those who are working to bring about a better and more peaceful world. As Thorbjorn Jagland, the Committee’s new Chair, said: “It’s important for the committee to recognize people who are struggling and idealistic, but we cannot do that every year. We must from time go into the real of realpolitik. It is always a mix of idealism and realpolitik that can change the world.”
It’s not a prize they give to people who have done something for peace—at least not always—but a prize that is sometimes given to someone who has promise of doing something for peace, which is what they’ve done in this case.

And, to put things in perspective, another quote from that same article:
Finally, for those who are really worried about the devaluing of the Peace Price (and this crowd includes people who’ve been bashing peace for decades), remember that Henry Kissinger is a previous winner. (Or, as Maureen Dowd put it, “Any peace prize that goes to Henry Kissinger but not Gandhi ain’t worth a can of Alpo.”)
Not that I’m arguing that they were right to award the prize to him. I’m reserving judgement on that. I just wanted to reemphasize an alternate point of view. And frankly, Maureen Dowd is right: They never gave the award to Gandhi, and they gave it to frigging Henry Kissinger. Kissinger! Frankly, if they felt that Henry Kissinger deserved a Nobel Peace Prize, then I don’t really have a lot of faith in their judgement.

My point? I have none.

No, wait! My point is this: Take the award away from Obama, and give it posthumously to Gandhi. And take Kissinger’s award, put it in a lead box, coat it in cement, throw it in the ocean, and pretend that it never happened.

Tuesday, October 13, 2009

Blog Comments

I read a couple of blog posts today discussing the topic of comments on blogs. Two sides of a debate, if you will (except I don’t know if anyone’s actually debating the issue).

First there was a post by Jeff Atwood over at Coding Horror, called Finally, a Definition of Programming I Can Actually Understand, in which he’s very much in favour of comments. A representative quote:

As I said in How To Advertise on Your Blog Without (Completely) Selling Out:

It’s an open secret amongst bloggers that the blog comments are often better than the original blog post, and it’s because the community collectively knows far more than you or I will ever know.

Indeed, the best part of a blog post often begins where the blog post ends. If you are offended by that, I humbly submit you don’t understand why blogs work.

A blog without comments is like Amazon without user reviews. Is it really even worth using at that point? The products themselves are commodities; I could buy them anywhere. Having dozens of highly relevant, informed user reviews means I’ll almost always buy stuff from Amazon given the chance. It’s a huge competitive advantage.

Jeff’s making a pretty good case that comments are an integral part of the medium of blogging; that blogs aren’t essays, per se, they’re forms of communication, and if the communication is one-sided, then it’s broken.

On the other side of the coin, we’ve got Joel Spolsky from Joel on Software fame, in an article called Learning from Dave Winer in which he argues that comments are basically just noise. I’ll post another representative quote (which actually starts with its own quote, from Dave Winer):
“…to the extent that comments interfere with the natural expression of the unedited voice of an individual, comments may act to make something not a blog…. The cool thing about blogs is that while they may be quiet, and it may be hard to find what you’re looking for, at least you can say what you think without being shouted down. This makes it possible for unpopular ideas to be expressed. And if you know history, the most important ideas often are the unpopular ones…. That’s what’s important about blogs, not that people can comment on your ideas. As long as they can start their own blog, there will be no shortage of places to comment.”

The important thing to notice here is that Dave does not see blog comments as productive to the free exchange of ideas. They are a part of the problem, not the solution. You don’t have a right to post your thoughts at the bottom of someone else’s thoughts. That’s not freedom of expression, that’s an infringement on their freedom of expression. Get your own space, write compelling things, and if your ideas are smart, they’ll be linked to, and Google will notice, and you’ll move up in PageRank, and you’ll have influence and your ideas will have power.

So on the one hand we have Jeff Atwood with his assertion that comments are an integral part of the medium, and you’ve got Joel Spolsky with his assertion that comments are mostly noise, and don’t add anything to the discussion—that if you really had something to say, you’d get your own blog and say it there. And that the magic of PageRank would take care of adding structure to the conversation.

Long time readers (if any) will probably not be surprised to hear that I’m mostly with Joel on this one. But the conversation got me thinking. In fact, it was Atwood’s post that I read first, and only got to Spolsky’s post because Jeff linked to it. (In fact, my wife’s organization has started a blog, and I was planning to send her the link to Atwood’s post, along with a link to The Corporate Weblog Manifesto. I probably won’t bother anymore; I’ll just send her a link to this post, and say “read the posts that I linked to”.)

So I did some more thinking on the subject. I think it comes down to what kind of a blog you’re trying to create; if you’re trying to build a community, then of course Atwood’s right: comments are an integral part of that, and Atwood makes a good case that spending some time with them is an important way to build that community. Others will have their own blogs, and will also contribute to the discussion that way, but comments allow for a much more immediate way to do that. On the other hand, if your blog is more of a personal thing, and a way to get your own opinions voiced, then Spolsky is right, comments will generate more noise than usefulness.

Which also explains why I am more closely aligned with Spolsky when it comes to my blog. This blog is not intended to be a community; it’s intended for me to spout my own personal opinions, for my own personal use. In fact, all of my blogs are really more for my own benefit than anyone else’s; if nobody ever reads the serna Bible Blog it’s cool with me, because I’ll still be getting my own use out of it. Same with the serna Book Blog. I write all of my blogs as if there are readers, but I don’t really care if there really are. (That’s right: still no stat counter on this or any other of my blogs.) That’s not to say that I discourage comments, but I must say that any time I do get notified of a comment—on any of my blogs—I immediately get a bad feeling in my gut, and only after I’ve read the comment and found it to be positive (and/or helpful) does the feeling go away. When I get an email from Blogger saying “so and so has left a new comment on your post such and such”, my initial reaction is always “oh no, what now…” And that’s despite the fact that most of the comments I get these days are helpful and/or positive.

It extends even to blogs that I read; I rarely read the comments on any blog. I’ll look on Google for other bloggers who are posting about the same topic, but I don’t look down to see what the commenters are saying. Some blogs are better than others, of course. Some have active communities, where the comments will provide useful discussion and a frank exchange of ideas. (Ironically, the majority of comments I get on this blog are in that category—or, at the very least, friendly.) Other blogs will have a maelstrom of noise so powerful that after reading them it’s hard to have intelligent conversation to anyone about anything for thirty minutes after; you find yourself afraid to compliment a fellow employee’s shirt for fear of having someone jump out beside you and tell you you’re a fool and don’t know what you’re talking about and Microsoft sucks.

Perhaps it’s a nature vs. nurture discussion; maybe Jeff Atwood simply “grew up” with friendly blogs that had intelligent conversations happening in the comments, while Joel Spolsky and I “grew up” with blogs frequented by trolls with nothing better to do with their time than telling us that we’re fools.

Monday, September 28, 2009

The search feature on this blog

Every time I create a blog—and how sad is it that I can even use that phrase; most people only ever have one blog—I do my best to keep Blogger’s little “navbar” at the top, so that you can use the search feature. (The one exception is the serna Book Blog, where I just couldn’t make it fit.) Really, it’s not even for your use, it’s for mine; if I want to refer to a previous post I’ve written, I want to be able search for it, and find it quickly.

But there’s one problem with the feature: it doesn’t work. You’d think that implementing a search feature for a blog should be easy; I’m not even looking for PageRank or anything, just a simple text search, but it just plain doesn’t work. Since I started this blog, there have been isolated incidents when it did work, but lately it hasn’t worked at all.

And when I say “it doesn’t work” I mean it doesn’t return any results. I can go to that little search box and type in a word, and Blogger will tell me I got no results; I can do the same search on Google, and tell Google to only look at results from this blog, and Google will find the results. How can an external search engine find results when Blogger’s own search can’t?!? (To do this in Google, use the site keyword; e.g. to search this blog for the word “multitask” you’d search for this:


Now, this blog has been March of 2005, but I won’t go back that far. Let’s just assume that the feature has only been broken since I updated to the “new” Blogger, in January of 2007. (I love the irony of linking to a post that I’d meant to delete, and never did.) Even if the feature has only been broken since then, that’s still two and a half years that the search feature hasn’t worked. And, as I say, I always ensure when making updates to the blogs’ templates to keep that “navbar” handy for my readers, because I’m always assuming that some day Blogger will fix it. It only occurred to me today that two and a half years is plenty of time to fix something as simple as a text search, so if they haven’t done it by now, they probably never will.

If I ever get a couple of hours of spare time, I guess I should remove all of the navbars, and implement search boxes on all of my blogs, that use Google instead of Blogger’s search.