Be more secure! Upgrade today.
Want better functionality? Upgrade today.
Save a developer! Upgrade today.
The save a developer thing is the impetus for this post.
The upgrade today mantra annoys me.
- Software rarely spends enough time in alpha and beta cycles to to identify all the issues.
- People have been so burned by using software in alpha and beta cycles, they are hesitant to try upgrades and help determine the issues.
- This lack of attention to the problems ensure, versions 1.0, 2.0, n.0 typically have a ton of unknown problems or are even less secure at times.
Unfortunately, the vendor who makes the application platform we run, Blackboard, has a philosophy to look at new web browsers while they are in beta but not actually work towards fixes for the new browsers until after the products are released. With most releases of Java or supported web browsers (Internet Explorer or Mozilla Firefox), Blackboard heard the complaints by the early adopters and released within a couple months an update which resolved the reported issues.
The students and faculty members fail to understand the issue. I think I do. Blackboard (like WebCT prior) understands there are differences between beta and final. Some of us argue these differences are usually minor. However, this is all asking someone to predict the future which we know is haphazard at best.
Long alpha and beta cycles allow more users to get involved, give those back to the developers, have them fixed before the version release. Burning users with buggy software ensures their lack of faith.