Another interesting article on an Electric Vehicle

Zero Motorcycles cranks out whisper quiet electric bike – Engadget

 This is another interesting concept. Unfortunately, I have a problem with the whole concept of electric cars – at least with ones with batteries which need to be charged from the electric power grid. In terms of a solution to our energy problems, or to global warming, these really make no sense whatsoever. All they are doing is moving the problem from one place (vehicles) to another place (the power grid), where the environmental impact is potentially as bad or worse. If even a small percentage of our vehicles were switched to electric, the impact on the power grid would be enormous.

While I admire the idea behind this effort, I believe the environmental advantages are largely illusory.

Brainstorming is a bad idea?

Looking at the quote on Marc Andreessen’s blog post Why brainstorming is a bad idea, I am forced to concede to the evidence presented, even though I am a big fan of group brainstorming. I wonder, though, if similar studies/experiments have been performed using what I refer to as “structured brainstorming”, meaning (to me) group brainstorming using tools/techniques/games designed to drive idea generation? I wonder if the results would differ?

The Future of the Tablet PC (does it have one?)

Reading a post by Loren Heiny, Will the Tablet PC find a new advocate?, got me thinking (again) about the future of the Table PC – more worrying about whether the Tablet even has a future. I am worried that because of the complete mess Microsoft has made of marketing the tablet platform, without Bill’s continued visible support behind it, the Tablet will either disappear, or be relegated to a very narrow niche product.

I think I have mentioned (over and over) that I am a big fan of the Tablet PC. I think that in many respects it is far more innovative than anything to come out of Apple in the last 10 years or so. And in terms of the industry as a whole, it has opened up both a hardware and potential software market well beyond Microsoft (take note of that all you Apple fans – what has the ultimate closed source community at Apple produced that has benefited any business other than Apple?).

The problem now, of course, is that the Tablet is old news. It is 5 years old, has not lived up to early predictions that soon “every laptop sold will be a Tablet” (though in real terms has been reasonably successful), there is a shortage of really “tablet specific” or even “tablet aware” applications (notable exceptions of course are OneNote and MindJet MindManager). It has really missed the boat on the hype cycle it could have generated. And now, the primary champion of the platform, Bill himself, is no longer involved in day-to-day operations at Microsoft.

So, whither the Tablet PC? Loren makes a number of good points in the referenced article – and I will not repeat them here (hey, go read the original!). I agree whole-heartedly that the fact that those of us who support the Tablet PC have our work cut out for us if the momentum is to be maintained. I have been looking for projections about the size and growth of the Tablet PC market, but doing a Google search I do not see anything that is newer than about 2004. Are there any more current projections out there?

Another thought I had, beyond Loren’s observations, is around open source and the Tablet PC. The hardware specifications for the Tablet are fairly well defined. Unfortunately, the only software that supports it is Windows (not that I dislike Windows, but it means the entire Tablet PC industry is at the mercy of Microsoft’s decsions about continuing the platform). how about some of these really innovation open source types take the Tablet PC to new heights? Lets create a Linux-based (or not) OS, put a novel, Tablet-specific UI on it, and drive the Tablet market in that way? I know there are people out there who have put Linux on the Tablets, but I am talking more than just getting so it doesn’t crash, and works like a laptop with a funny shaped mouse. Something that really IS a Tablet computer. That would be a really innovative use of Open Source!

Thoughts?   

Vista Flops? I beg to differ….

I have been reading posts (blogs and in more traditional press) since Vista came out (well, since long before it came out, actually) about how bad it is, how unstable it is, about how nothing works, about how disappointing it is, and so on, blah blah blah….

Today, I came across this post Vista Flops, Users “Upgrading” to XP (there are number of similar posts in the same place, I will not link to them all).

I am rapidly coming ot the conclusion that people in the computer industry are the biggest whiners in existence – even worse then Canadians (just kidding – I AM CANADIAN). I have been using Vista as my primary OS since before the first release candidate. I use it on 5 computers (3 laptops, 1 desktop, and 1 Tablet). I have found it to be at least as stable as Windows XP (and more stable than many other versions of Windows in similar stages of their lifecycle). Performance is as good as I had under XP for most things. Overall, I have found it to be pretty good.

Are there things which I would like to have seen? Sure. Are there things that were in the original preview of Longhorn I saw at PDC 2003 that I wish were in the final version. Absolutely. I also recognize that features get cut and modified over the course of development, usually driven by the marketing department and feedback from those same whiny users.

The biggest complaint I have had about Vista is not against Microsoft so much as it is against the hardware and software community surrounding it. The availability and quality of updates to drivers and applications has been abysmal. A fair number of the devices I use (especially on my Tablet) were not supported when Vista was released, and some still are not and probably never will be. What happened – you guys get surprised by the release of Vista? Didn’t know it was coming. Come on – get with it. The same can be said for products from Apple (iTunes) and Adobe (Reader – the number one crashing product I have under Vista).

Get off it people – if you do not like Vista – do not use it. But please, stop whining about it!

Open XML versus ODF, Part III

Well, since I did not receive any pointers to more analyses from my last post, I went searching on my own (doing the work myself always being a last resort!) I have found a number of articles which were very informative and seemed well put together. I am still reading and re-reading some of them, so my opinions my changed, but they all seem to be at least thoughtful analyses.

ODF/OOXML technical white paper has a fairly detailed analysis, though from the outset the author admits that the underlying philosophy of the paper is

“We are of the view that the format appears to be designed by Microsoft for Microsoft products, and to inter-operate with the Microsoft environment. Little thought appears to have been exercised regarding interoperability with non-Microsoft environments or compliance with established vendor-neutral standards [11].”

This seems to be an underlying theme of most of the articles – to start with the purpose of showing “why ODF is good and Open XML is bad”, as opposed to being purely unbiased form the start. This paper appears to be relatively fair in its analysis, however.

I also stumbled across a number of articles related to errors in the spreadsheet formula portion of the OOXML documentation, such as Microsoft OOXML spec ‘dangerously flawed’. While I would agree that these flaws (if they exist – I have not searched for them, but I beleive they do) are important, you do not through out a proposed standard because of flaws like this, you fix them and move on. I would be relatively surprised if a 6000-page document did not contain any errors. I would see this as an argument against fast-tracking standardization, but not for throwing the Open XML specification out altogether.

Then there are the documents presented on http://www.noooxml.org/arguments. While I am sure there are some great documents on this site, for my purposes I excluded them from the outset, since the site is obviously biased. For similar reasons, I did not go searching around Microsoft’s web site, or Microsoft Blog’s for information supporting Open XML.

The wiki at http://www.grokdoc.net/index.php/EOOXML_objections maintains a substantial list of concerns with the Open XML specification. There are concerns in there with which I agree, and others with which I do not. It, also, starts from the premise that “Open XML is bad”, and so is not really an unbiased analysis.

One thing that struck me as interesting, is that outside of the purely Microsoft sphere of influence (the Microsoft web site, Microsoft blogs, etc.), I came across no information presented from a Microsoft perspective, or analyzing why Open XML is better or as-good-as ODF. It seems the Microsoft camp is focusing purely on “we would like to get this specification standardized”, rather than attacking the alternative.

This leads to the question, isn’t that the correct approach? Let the Open XML specification be standardized (with identified “real” problems fixed, and let Darwinism decide which format survives?  (I can hear the Open Source community crying already!)

But, isn’t that what having alternatives is all about?

"3D" browsing and searching

Came across a post today called Exploring the 3D Search, about an application called SpaceTime (www.spacetime.com). It is a browser and search front end, which presents the results in a 3D “stack”, and allows you to scroll through them in that way.

While I like the initiative of trying a new visual approach, as I have discussed previously, this is really just another way of presenting a list. It is a start, but still not what I am looking for in a really new, “next generation” search visualization.

It is definitely worth checking out, though.

Open XML versus ODF, Part II

Last Thursday, I posted a question about Open XML versus ODF, hoping someone could point me a a real, technical analysis of the strengths and weakness of the two formats. The one response I received, from Sam Hiser, pointed to an article entitled Interoperability: Will the Real Universal File Format please Stand Up? 

The article (and the other related articles in the same publication) was very interesting, well written, and raised some interesting points. Unfortunately, I do not agree that it constitutes a technical analysis of the two formats. There is a great deal of reference to features in OOXML which cannot be implemented by third parties without access to proprietary information from Microsoft, but there are few if any hard examples. The primary examples might be the inclusion of things like autoSpaceLikeWord95 and footnoteLayoutLikeWW8. I cannot see how Microsoft could avoid including items like this in order to support proper rendering of legacy documents. In fact, if Microsoft had not included backwards compatibility support in the specification, I could see them being equally criticized for it. As for implementing these features, this is only necessary if you want to render documents to look like old versions of Word.

Most of the commentary in these articles still comes down to “ODF is good because Microsoft is evil”.

In addition, there is a great deal of argument as to whether having more than one standard is a good thing or a bad thing. It is interesting to me that the open source community is extremely supportive of having alternatives, unless one of the alternatives comes from Microsoft.

So, I repeat my question (and clarify slightly): Does anyone know of an independent, unbiased analysis of these two document specifications?

Open XML versus ODF

I have been reading several articles and blog posts the last while on the approvel process for Open XML in various countries. These include Open XML – US V1 Committee Vote and IBM MotivationsMicrosoft guns Open XML onto ISO fast track, and Open XML Suffers a Setback on the Road to ISO Ratification . Setting aside the name-calling, accusations, insinuations and other vitriol which seems to pervade all discussion involving Microsoft and the open source world, I would like to better understand what the technical justification of ODF over Open XML might be (or vice versa). While I would not claim to be a technical expert in either format (though I know Open XML much better than ODF), the main arguments I have seen in favour of ODF are:

  1. It got here first
  2. It is not from Microsoft

I do not see either of these as useful arguments. Can anyone out there point me to real, meaningful, technical reasons why one is better than the other?

Innovation and Collaboration

Interesting post on consultaglobal called Innovation And Boundariless Design. I was really sucked in by the opening quote

“Innovation often arises out of crossing disciplines and combining technologies”.*

This is a battle I seem to have on a continuous basis – trying to convince people that innovation must be an interdisciplinary effort, and must involve people from almost every part of an organization, and outside the orgainzation. This is especially true if you are working towards wide open innovation of business processes, internal technologies, as well as new products. Good ideas and design input can (and must) come from everywhere.

Another aspect of this interdiscinplinary approach, and the cross pollination of ideas and technologies it encourages, leads to compounding of ideas in much the same way as one compounds interest – two innovative ideas combined together in a novel way lead to improved value much greater than either innovation on its own.

This (as well as the question of whether design for manufacturability comes before human factors, or vice versa) always reminds me of the old (?) idea of integrated product teams (I cannot recall where I first ran into this – whether it was in the telecom world or military projects). The fact remains that it is almost impossible to separate engineering, human factors, or any other aspects of design into entirely sequential steps – they must be integrated, collaborative, iterative activities.

As the referenced post points out, however, none of this matters unless the whole process brings value to some customer – it is not innovation if it does not bring value.

(*) Pushing the Boundaries of Design by Jessie Scanlon