What Microsoft has to learn...
This started as a response to Rob Gonda's "Will Microsoft ever get it?" post, but I think there's enough in here to actually build out it's own post:
I tend to break computer users down along the "Neophile" vs "Neophobe" axis. About a third of the computer users out there will use any new technology as long as it's new. These are the people who loved Vista, because it did new things that no OS before had done (or at least, not one that they had used). Most of them will upgrade to windows 7 just because it's new, and they want to try it. Usually within this crowd there's a certain tolerance to bugginess, because the "newness" outweighs the bugginess. In the most extreme case, these folks are Linux users, who run bleeding edge Gentoo releases and build packages of new software whenever they're released. These are the folks who are subscribed to the Freshmeat and Sourceforge new software feeds, and install new software daily. I'm one of these folks mostly.
Then there are "Neophobes", who hate new things simply because they're new. These are the people who say "I've got my toolset, and it works, and it'll take me weeks worth of time to learn something new, so why the hell would I want to upgrade to Vista?" These are the people who were running Windows 98 well into the 2003 timeframe. These people were angry enough that they were "forced" to upgrade to Windows XP, and this whole Vista thing just pushed them over the edge. A few picked up Macs, but then they'll be back on the Windows platform in a few years when Mac OS 11 comes out and they get pissed about the fact that there's now some weird desktop metaphor change that they aren't used to and they'll start reminiscing about good old windows, and how easy everything was there. There's a fair number of these folks in IT too. Ironically, this crowd also hosts a lot of Linux users who are more than happy with their green phosphor command prompt thank you very much. There's also a good amount of bug tolerance in this group because they would rather work with a software package that's buggy, but they know how to work around the bugs, than learn something new.
Then there's the middle ground. I call them the Pragmatists. They don't care whether it's new, or old, they just want something that works. There's almost no bug tolerance in this group. These are the folks who coined the phrase, "Don't use a Microsoft Product until the first Service Pack". This group is actually a fairly small portion of the general IT population, since they tend to get beaten up a lot by the other two factions. However, this group makes up the vast majority of the general, non-IT population. Most of these people won't bother even trying an application unless there's an obvious need at hand for it. Likewise, they won't bother with upgrading their OS until some outside circumstance forces it (They buy a new computer, with the new OS on it, they are forced to by their corporate IT policy, etc..) For most of these people, there's no reason to switch to Macintosh, or Linux, because even the huge changes in Vista don't significantly negatively impact them. Their Office stuff still works, though the toolbars took a bit of getting used to, and their email and web browsing work just fine, and that UAC stuff only affected them like 5 times when they were first setting up the computer, and then it hasn't popped up since then.
The problem with Vista is that Microsoft got too caught up in the Neophile point of view. They made so many radical changes to the OS that it completely alienated all of the Neophobes to the point where even the people who despise change, and want to keep things as static as possible are chosing to change to Macintosh rather than learn the newness of Vista. And of course, whenever you make such massive changes to any large system, many bugs were introduced. This alienated a good chunk of the Pragmatists as well. What Windows 7 needs to do if it wants to succeed is move back towards the middle, to the Pragmatist point of view. New features are great, but don't let them overshadow reliability, and for god's sake don't drop massive user paradigm changes into your most commonly used flagship products first without getting people used to them in other products. The ribbon bar in Office may be a good idea, in the long run. It may make office easier to use, but you're terrifying about a third of your audience. It's just not a good plan.
^ TOPCold Fusion is NOT dead... ColdFusion is LIFE!
Over the last year or two there have been various reports that ColdFusion is dying, and that it's a forgotten technology. This has caused much furor in the CF Dev community, since a good many of them have built their careers on ColdFusion evangelism and ColdFusion development.
However, the recent TIOBE Rankings for April 2008 show that not only is ColdFusion not dead, but it's actually on the rise once again. While it still ranks below the likes of Ruby, Python, and C#, ColdFusion has surpassed Lua, ActionScript, and Groovy.
Of course, there are plenty who will argue the validity of using the TIOBE index, since it's based on Search Engine results, rather than actual market positions, or sales figures, but at very least, ColdFusion is doing a good job of generating posts about ColdFusion programming all over the internet.
^ TOPMozilla Prism
I took a look yesterday at Mozilla Prism. So far, i'm not particularly impressed, though I have to do a little more investigation into the webapp.js file and see what XPCOM stuff I can tap with it. As it stands, it seems like it's just a simple way to open up a chromeless browser window from the desktop instead of having to click a bookmark. Largely uninteresting, when compared to things like Google Gears and Adobe AIR.
Tonight i'm going to tap the Google Gears libraries a bit and see if there's anything in there that could be combined with Mozilla Prism to make something really cool.
^ TOPNot again.
So, after the Christmas 2003 incident, you would think my family would have the good grace to avoid Heart Attacks on holidays. Unfortunately, we apparently forgot to tell my grandfather. We got news this morning that he is in the Hospital in Minneapolis after suffering a heart-attack at some point last night. My uncle Gerry and my grandmother are there now, finding out more details. My parents, who are visiting my sister and I in California are looking into cutting their trip short and heading home today to be at his side, and to be there for him.
Apparently Grandpa Ness has been feeling "not well" for the last two weeks now, but he's a stubborn old coot, and only sought out medical help on Tuesday or so of this week. I can only pray that he hasn't let this go too long, and that this is just something that he can recover from, and learn a lesson from. Regardless, I'm looking into flights to Minneapolis right now, and figuring out what I need to do to be there.
^ TOP