avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • December 12, 2018, 03:56 AM
  • Proudly celebrating 13 years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: Why is Microsoft software so unreliable?  (Read 3158 times)


  • Charter Member
  • Joined in 2006
  • ***
  • Posts: 1,799
    • View Profile
    • Donate to Member
Why is Microsoft software so unreliable?
« on: July 19, 2006, 04:28 PM »
Why is microsoft software so unreliable?
How did we grow used to it?

My recent examples:
Hibernation and laptops:
Everytime I close the lid in my laptop, I have a good chance of not seeing my laptop come to life again. Having to reboot makes me miss some info and time.

Visual Studio:
No autosave, no temporary files
(but see http://www.codeguru....s/article.php/c3123/, solution pointed out here in this forum!)

Even with autosave 'on' and saving every minute, no temporary files. For the love of Pete, I cannot find temporary files anywhere. The 'autosaved' files offered in the left menu (we are used to those, right? that means we see plenty of crashes) are from several hours ago.

The intergalactic police should come and execute the responsables for so much suffering. Humanity would be better off without the careless programming that Microsoft practices.

Rant mode *off*.
PS: I have tried to move to Linux and actually spent about a year using it exclusively. But being a tweaker, I spent too much time doing unproductive things such as recompiling kernel, finding drivers, and looking for programs. It's not a solution for me.
« Last Edit: July 20, 2006, 04:25 AM by brotherS »


  • DC Server Admin
  • Charter Honorary Member
  • Joined in 2006
  • ***
  • Posts: 862
    • View Profile
    • linkerror
    • Donate to Member
Re: WHy is microsoft software so unreliable?
« Reply #1 on: July 19, 2006, 04:35 PM »
Microsoft's answer would be that it's all because of other non-microsoft software you have installed. :D

The problem is probably that Microsoft is too big, and they have a horrible business policy.
I'm sure they have both very good and very bad programmers, but when you have very large teams, the chance of the few very bad programmers doing something horrible increase significantly.
The other problem is that their business policy is to eliminate all compitition, so naturally, it they put in a few crashes into their software here and there that they can blame on third party software, that's all for the better. :P

Yeah in Linux it's easy to get bitten by the tweaking bug, just because you CAN. I've been using gentoo for the longest time and lots of time was always spent on compiling and configuring etc,... though usually once I have it as I want I can start being productive. On my other machine I installed ubuntu(dapper), which pretty much worked out of the box, I didn't even need to compile any drivers into my kernel. So that saves some time, offcourse now i'm stuck with a gnome desktop. I always used either fluxbox or afterstep. I haven't gotten around to changing it yet, I might actually switch back to afterstep later, but it works for now. I'm not gonna start fiddling around too much again now that I'm finally being somewhat productive ;D
« Last Edit: July 19, 2006, 04:42 PM by Gothi[c] »


  • Charter Honorary Member
  • Joined in 2005
  • ***
  • Posts: 9,134
  • [Well, THAT escalated quickly!]
    • View Profile
    • f0dder's place
    • Read more about this member.
    • Donate to Member
Re: Why is Microsoft software so unreliable?
« Reply #2 on: July 20, 2006, 05:39 AM »
Personally I've never liked autosave - it's better to get a good habit of "one-on-control-anoter-on-s" regularly. I don't even think about that keyboard combo anymore, happens automatically. IMHO more reliable than autosave. (Oh, and VS saves on project builds btw.)

Use of temporary files for saving is generally a good idea though ("atomic commit" in a way). If it's not implemented in VS, I guess it's because "what could go wrong when saving a ~100kb file?" - *shrug*.

As for your laptop, the ACPI stuff needed for that to work well has horrible implementations on a lot of systems, so it's not necessarily Microsoft's fault. Problems can also be caused by third-party drivers not supporting the Windows Driver Model power-saving stuff properly.
- carpe noctem


  • Coding Snacks Author
  • Charter Honorary Member
  • Joined in 2005
  • ***
  • Posts: 2,965
    • View Profile
    • Donate to Member
Re: Why is Microsoft software so unreliable?
« Reply #3 on: July 24, 2006, 02:33 PM »
Gothi[c]: Surely you haven't forgotten
apt-get afterstep
have you?  :o

Robust and discreet Autosave should be a feature offered in ANY app that involves document creation and modification. I learned that the first time I accidentally kicked the power box which was unwisely installed under our stations in high school computer class.

(Scene: Circa 1984 classful of Apple IIe's)

me- *kick*
computers- *bzt...*
me- "oops..."
computer class teacher- "Everybody remembered to save their work, right?"
class- *glaring at yours truly* "umm... no..."


  • Charter Honorary Member
  • Joined in 2005
  • ***
  • Points: 45
  • Posts: 3,409
    • View Profile
    • Donate to Member
Re: Why is Microsoft software so unreliable?
« Reply #4 on: July 24, 2006, 02:39 PM »
I am with f0dder on this one. I make it a habit of hitting CTRL+S and saving my work every so often. This takes all of half a second and works very well. Auto-save, while a nice idea, can cause problems (What if it auto-saves something you didnt mean to do?). Anyways, I dont think that the lack of an auto-save feature should deem microsoft's software "unreliable".