Back for a while to the world of (near) real-time software applications, I’m reminded of one of the most difficult software development tasks: debugging device drivers. Mainly when there is a lot of previously existing code, and few unit tests. Yet, that wouldn't be such a problem if I could get to a clean state quickly.
Despite several available virtualization solutions, one of the main problems faced nowadays with restoring operating systems to a previous state is not only the time it takes to boot a certain configuration, but the time it takes to shutdown a running operation system, gracefully. By now, I know about all the possible explanations (drivers, cleaning page file, antivirus interference, etc.). I can understand those explanations. What about those that cannot do it?
Are customers supposed to just accept that, after any confirmation about unsaved work, a running operating system may take at times 5 minutes or more to just “stop”? That is quite unbearable, and some of the “optimizations” I’ve read about, like disabling the cleaning of the page file, are creating security issues that most customers are likely unaware of. A shame on us, developers who allowed this to happen.
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment