General discussion


Why do IT people really bash Windows?

I wrote about this in another thread in response to a comparison of windows question.

Anyway, it's a hot topic in my opinion so let me recap. Comment away. :)

Why does everyone "bash" Windows? I could sit here and bash linux, windows, mac os and anything else, but that is just pointless and pedantic.

The point is every operating system has it uses. You just need to choose what best suits your needs.

Anyone who claims to hate Microsoft Windows, Linux, Mac OS or any other operating system is not a true techie or network guru. You don't ever bash the OS, in fact if the OS crashes then it's your fault not the OS; Why didn't you make sure that it was using the right drivers, or the hardware is compatible or blah this and blah that, and so the list goes. Any OS crashes for a reason, not because it just feels like it. Compatability is there for a very good reason, why support something that is old when you need to keep moving forwards. Example, all leaded petrol car owners here in Australia can no longer purchase leaded petrol, they are forced now to use unleaded and an additive. Why? Because those cars are so old and they are few and far between now because unleaded cars are cheap enough to buy second hand as your first car. Get my point there?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Take a Linux administration course :)

by hellums In reply to What the hell...

Sounds like you're not very good at Linux or Unix administration. There are lots of training courses and books out there. 10:1 or 25:1 ratio of Windows to Unix/Linux crashes in my experience, which dates back to the late 80s. And when I have to patch a Unix app, I never had to reboot, unless it was related to networking or hardware.

Collapse -


by apotheon In reply to Take a Linux administrati ...

You shouldn't have to reboot for networking, either. Just restart networking.

# /etc/init.d/network[ing] restart


Collapse -

8 months is good ??

by pkr In reply to What unstable?

I have firsthand knowledge of an IBM AS/400 which kept churning for 4 years. Yes - FOUR YEARS. In the meantime we changed most of the internals, including all disks with the exception of the one with the system on. And that was the reason for shutting it down - replacing the system disk.
Natrurally it was never infected with viruses, worms, spyware et. al., even though it was on the net for the same period.
On another box we changed it from 48 bits to 64 bits, reloaded all apps and DB's without rewriting a single line of code. We did later, but for other reasons.
I wouldn't dare running an NT box for 8 months without patching - flirting with death.

Collapse -


by it.dude In reply to Angus, is your brain a si ...

Impressive! ....most impressive!

Haven't read a quality dress-down of M.S. for a while.

Thanks for the reminder of why it's better to INVEST time in learning Linux, than to WASTE time attempting to figure out the "Black Box", "super secret", " .... oh God, if hackers found out about this !!!" reason for my PDC and BDC to stop talking to each other.

I'm not going to write the novel of what kind of admin job I had been doing previous to the above issue. I will simply say that I had MS Updates done (manually installed while I watched), firewalls up, anti-virus running and updated. The two Server 2000 boxes were communicating one day, and the next had stopped.

The ultimate solution, I had to promote the BDC to PDC. Reinstall the old PDC so it fixed the problem and then set it up as BDC.

Since I've moved to Linux, I have to take the covers off once in a while to dust!!!
Admin is pretty borning unless I want to spend time tracking down the origin of an attempted Hack or brute force password attack.

Sorry Angus, ... there I go MS Bashing!

Collapse -

Love your post

by jrice In reply to Angus, is your brain a si ...

Your on the money. I support microsoft products and I use but I still dislike Microsoft as a company.

Collapse -

So in that case will you

by HAL 9000 Moderator In reply to Love your post

Be at the head of the Que when Visa sorry I meant Vista comes out as a production version and be one of the First Beta Testers that pays for the privilege of sorting out problems to M$?

That is one of my biggest bugbears with any new M$ OS we are nothing but Beta Testers who have to pay for the privilege to getting their products to actually work part way like M$ claims they will.

Col ]:)

Collapse -

All very good points.. except...

by Alacrity In reply to Angus, is your brain a si ...

Why is it that I ran my entire company for 4 years on NT 4 server and Windows 98 workstations. Then upgraded the workstations to Windows 2000. Now I have Small Business Server 2003 and Windows XP pro, SP 2 and have been running the server since LAST august with only the reboots needed for patches and those apps that INSIST you reboot even though you don't HAVE to. And my general workstations run for many weeks without problem. MS Office (Outlook, Word, Excel, Front Page, Publisher, power point - often all running at the same time), QuickBooks Pro, Hot sync software for Pocket PC enabled phone, Several web pages (hey.. I ain't ALL work) Symantec antivirus and /or Firewall, AVG, Spybot and/or Ad Aware, etc, etc. This workstation I'm on now hasn't been re-booted since the last Norton AV update forced me into it 3 weeks ago. My last install of NT 4 SERVER wasn't rebooted for nearly 3 YEARS!

I say it IS possible to produce a stable system using Microsoft products, I have 14 years of Proof! End users that I support (most have used my services for over 11 years) all START with a stable system and then muck it up so that I have to get it straight again, but that isn't MICROSOFT's fault! the USER messed it up. OR malware messes it up, but Microsoft products have treated me and the companies I support very well. From time to time I have to tell a user "No, That's not a good idea" becasue of some security risk left open in MS products. Sometime it takes Microsoft a lumbering long damn time to close the hole. My time spent building $30,000,000 CRAY computers taught me that simply slapping a "fix" on one place just might break something you don't know about in another place. I remember one system designer asking if he could "just move the edge connector 20 mils over" and got approval from his manager. that caused nearly THREE Million Bucks to be spent to correct the problem caused downstream from his department. Microsoft MUST be as sure as they can be that the "fix" they throw out to patch some hole does not create a new hole somewhere else.

My last point (made somewhere up above, I think) is that it IS possible to have a stable solid system using Microsoft products. If you are NOT able to do this, perhaps it's because your skills are not up to snuff. Actually I firmly believe that it's NOT your tech skills that are too LOW, but too HIGH..

Just my $.02

Collapse -

What I think you are missing

by HAL 9000 Moderator In reply to All very good points.. ex ...

Is that with a Nix server you don't have to reboot when you apply patches or new Applications only Kernel Upgrades.

Admittedly I do come from a Unix background and I'm not used to all the rebooting that Windows requires. Instead of considering several weeks up time as good I would be considering only several months up time because of a patch bad.

But if you've never used a Nix you'll never know what the unnecessary steps that you are going through and the extra money that you have to waste on security which shouldn't be necessary and is affecting your bottom line.

Col ]:)

Collapse -


by ungle In reply to What I think you are miss ...

Yo, dude. Windows is (effectively) the same. The only reason reboots are necessary is
a. You don't know what you're doing,
b. Sloppy packaging or
c. one of those MS patches that in the MS world is effetively a patch on the kernel.

I do agree with the several weeks bit, though. I recently was involved in a move of the Asia head office of the financial house I was working for at the time, and discovered one of the trader's PCs (extremely heavily used) had been up for 4 months.

Collapse -

B and C are very common

by jmgarvin In reply to Umm...

Typically EVERY patch MS comes out with patches the Kernel or Executive in some manner. There are TONS of sloppy packages out there and hundreds of drivers that force a reboot on install (you can't simply restart the service)

Related Discussions

Related Forums