The Very Worst Uses of Windows 816
bigplrbear writes "I found an interesting article revealing the many places that Microsoft products reside, and what they're used for, ranging from elevators to ticket scanners."
From the article: "Thanks to VMWare Windows is spreading throughout the datacenter. And, of course, there is only one operating system to use if you are dependent on Microsoft apps like Outlook, Word, and Excel. While I have joined the chorus of security folks who rail against the Microsoft Monoculture I still cannot believe some of the uses for Windows. Some of them are just downright silly, some you may claim are criminally negligent." Note: I'm making no claim of criminal negligence!
Misleading slightly (Score:4, Insightful)
I'm all for having a "lol" at stupidly overcomplicated systems being used for the most mundane of tasks, but this article is a little sketchy on some of the details.
For example, one line states "Why not program some stripped down embedded system for that task?" when it doesn't even indicate what version of Windows the system he's talking about uses - there IS an embedded version of Windows available for such tasks, you know.
The article is still a good read, though, but I'd take what it's saying with a pinch of salt and don't just immediately start bashing Microsoft, after all it's not their fault if a sysadmin makes a stupid design choice or 10.
Re:Medical equipment (Score:5, Insightful)
Medical equipment: I confirm. My cousin is an engineer for General Electric, Medical section. As far as I know he services cardiac echography equipment. From what he told me, they all run Windows. Of course, this isn't life threatening, but I do know he's hardware guy and it wouldn't be the first time he calls me for a software problem in his job.
While not in this case, a BSOD may mean real "D" these days in a hospital.... Sad, but true...
While I agree this is questionable, I don't think they are connected to the internets (at least I hope not). So, the whole virus/worm fear is probably irrational.
Re:Misleading slightly (Score:2, Insightful)
Power draw (Score:5, Insightful)
Another problem with overbloated systems running simple tasks is the huge draw of electricity. How much power could we save (and, therefore, money) by using bloated systems less for simple things?
An obvious observation, but I thought I'd make it.
Diebold Windows CE (Visual Basic for Applications) (Score:3, Insightful)
I nominate the Diebold Windows CE (Visual Basic for Applications) voting machines to the list.
After all, Diebold could have done worse and used Windows XP, or Windows Vista (not that it was out at the time), but I still nominate Diebold to the list for having chosen VBA (not that there is anything wrong with VBA, VBA has its uses -- it's just that it's really a poor choice for making supposedly secure and transparent voting machines).
SERVER WARS (Score:1, Insightful)
i beg to differ...
Re:Obligatory... (Score:1, Insightful)
That's the truth of the matter and Windows isn't even a particularly good desktop OS. Any 'engineer' choosing Microsoft is demonstrating total lack of ingenuity.
Management OTOH are complete fucking idiots, they'll always go with the inferior solution from the hardworking salesman. One day we'll have managers who'll think, "this salesman is working harder than the others because he knows his product isn't as good". Until then suffering Windows is unavoidable.
Re:Obligatory... (Score:4, Insightful)
Management OTOH are complete fucking idiots, they'll always go with the inferior solution from the hardworking salesman. One day we'll have managers who'll think, "this salesman is working harder than the others because he knows his product isn't as good"
In my experience management tends to go for the product that has the best clicky-pends and coffee mugs and complimentary dinners. That being said, the same management is in a sealed off part of the building with high security locks and a separate parking area with a security guard and barbed wire fencing. I wonder what they know that they don't want us to know.
Re:Medical equipment (Score:5, Insightful)
I would assert criminal negligence (Score:4, Insightful)
I have no reservations about it. Given the constant stream of complaints that Bill Gates himself had about the quality and stability of Windows, I'd say it is pretty safe to assume that Microsoft is WELL aware of problems with Windows. And for Microsoft to actively push their OS as a platform upon which important, significant and even critical systems and services are run without disclosing the KNOWN risks of using Windows under such circumstances is criminal negligence or even worse.
Once again, resorting to the old "car analogy", if an auto manufacturer were caught pushing their dressed-up SUVs as actual ATVs, I think it's safe to say that various consumer protection agencies and possibly the department of justice might get involved.
How does Microsoft get away with this? Simple -- they are the only game in town and as such is typically viewed as "the best we have." To complain that the best is not good enough would be considered by most to be a wasted effort.
"Critical Mass"
Microsoft achieved it and now most tech people know only Microsoft Windows and will deploy only Microsoft Windows for any given task.
It's good that some people like the NYSE has found Windows lacking and that better alternatives exist for their specialized tasks.
I don't think anyone will argue that Windows on the desktop is acceptable for a lot of people, especially those people who don't have people like me to help them use other systems. If they are on their own, trying to use Linux or even MacOS might leave them out in the cold or under rather EXPENSIVE support costs. (A lone user can barely throw a stone without hitting someone who can deftly advise them to reboot and reinstall.)
But to put Windows in SPECIALIZED applications and devices makes no sense. "Compatibility" isn't an issue there. "Usability" isn't an issue there. "Stability" and "reliability" are often the most important considerations with cost as a third or fourth. (I don't have a second most important consideration, but I'm pretty sure the fifth is "profit!!")
Re:Ho ho ho! *snort* (Score:2, Insightful)
Aside from the fact that putting drivers in user mode increases reliability, you've got a good point.
Re:Obligatory... (Score:5, Insightful)
You can't expect people to just up and leave software that they're familiar with. I reference college students where I work. We have two rooms, similarly laid out. One room has HP DC7600s, the other Intel iMacs. People chose the room with the HPs showing the typical Windows screensaver over the Macs (which dual boot!) - why? Because it's friggin familiar. And you can't change that by saying the software is crap, because there isn't a usable alternative that appeals to the masses.
Re:There can be only ONE (Score:5, Insightful)
What you can't get for mac is Access...
What can an app written in VBScript+Access do that an app written in Python+SQLite can't?
Re:Obligatory... (Score:5, Insightful)
You can't expect people to just up and leave software that they're familiar with.
While that sounds good it doesn't wash. It depends what you are setting up to do. If you want a permissive, bug ridden system where most of your company's bandwidth is used for P2P and every three months your clients call you to tell you their computer has slowed to a crawl, go ahead and use Windows.
If you are running a class where you are developing software that runs on Windows, then use Windows. Fine. If you want to run a Windows Only App, and it won't run in Wine or there is no Mac equivalent, then no probs, you win, go for Microsoft.
But if you want a system where the idea is to minimize the cost of installing and maintaining terminals, maximize the portability of people's computer setups, and give people enough freedom to play without crippling everyone else's system, then go for a thin client model using Linux or BSD. For most people there is no 'familiarity' problem in clicking on an icon, doing stuff and then going 'File -> Save' then 'File - Quit' or finding a the little X in the top right corner.
And who ever said you had to use a mac?
Re:Obligatory... (Score:4, Insightful)
>Management OTOH are complete fucking idiots
Management is always somebody else, isn't it?
You never get promoted and that's somebody else's failure.
Re:Medical equipment (Score:3, Insightful)
Re:Medical equipment (Score:4, Insightful)
yes, but you make decisions based on available information, provided by that monitor.
Re:Public BSODs (Score:5, Insightful)
Because the CEO pushed to be a microsoft partner and is too stupid to understand what his engineers are telling him.
It happens a LOT.
Re:There can be only ONE (Score:4, Insightful)
What can an app written in VBScript+Access do that an app written in Python+SQLite can't?
Execute without a complete rewrite?
Might not be so crazy (Score:5, Insightful)
Windows 3.11 wasn't a truly multitasking operating system, so that, if an application was doing something in between Windows messages, it genuinely owned the whole machine. If you are doing a near real time system, you probably don't want to lose a time slot in the middle of a roller coaster ride so that some other daemon could fire off and do something else. So yeah, Windows 3.11 might actually work rather well, so long as the application wasn't trying to allocate too many resource handles.
Actually, I wonder why MS wouldn't release a non-preemptive Windows, just for this purpose. It would be a lot more reliable for some applications.
Re:Obligatory... (Score:4, Insightful)
Being a manager is hard enough without gitch religious trolls twitching their flaming tech tongues in a business vacuum.
There are bad managers / administrative departments out there. Lots of them. They are as good as the facts and information they receive, sure, but they are also as good as their intelligence and integrity. Someone once asked me "why are our admins so freakin' stupid and incompetent?" to which I answered "because if they weren't they wouldn't be working here for wages but at successful company X with its expanding markets and sweet result driven bonuses."
Re:There can be only ONE (Score:3, Insightful)
Re:The scariest moment of my life... (Score:4, Insightful)
It's a DIEBOLD ATM with a _headphone jack_
The headphone jack is an assistive device. It's sometimes called a "talking ATM". The idea is that a blind person can be prompted through the screens. (Notice the braille dots near the jack.)
But yeah, the domain not available thing is funny.
Re:There can be only ONE (Score:3, Insightful)
Re:The alternatives suck harder (Score:1, Insightful)
If you have more than a month uptime on any system, you are not applying the patches correctly
There, fixed that for you.
It is a common myth that Linux systems don't require rebooting. I manage several RHEL4 and 5 machines, and Red Hat regularly releases updated kernels, which means that you pretty much have to reboot them.
Sure, you can have some ancient version of Unix/Linux that works as long as hardware doesn't fail, but you better not connect it to the Internet.
Re:One word: Accountability (Score:4, Insightful)
With Windows, if something goes wrong, you can contact the hardware manufacturer (If it's hardware/driver-related) or Microsoft if it's software related. And if they won't help, you can sue them. You can't say the same about *nix, where the prevailing attitude seems to be "It don't work, you're on your own to find a fix"
Read a EULA lately, there is a line voiding Microsoft of any responsibility. *nix, plenty of paid for support out there, Novell (SuSe), Canonical (Ubuntu), Red Hat (think this one is obvious) and those are just distributions. A lot of the bigger more important packages have commercial backing and support. I should mod you flame bait, but never attribute to malice that which can be adequately explained by stupidity.
Re:Ho ho ho! *snort* (Score:4, Insightful)
Re:Obligatory... (Score:5, Insightful)
The last person to use our lab equipment for P2P had his associated UNIX account probshelled for 6 months. 6 months of no e-mail, no internet, no lab access.
And for the record, our DeepFreeze'd machines along with hard-disk images results in one machine out of 50 going bad in about a 6 month period.
I don't know where you work, but those symptoms sound more indicative of user (or administrative) stupidity.
Re:Medical equipment (Score:5, Insightful)
Sue them for what? Microsoft makes no guarantees. Read your license agreement.
Re:Medical equipment (Score:4, Insightful)
Re:Obligatory... (Score:5, Insightful)
Why is a computer necessary? A plastic sign would do just as well.
Poor Quality Writing (Score:5, Insightful)
Google? (Score:3, Insightful)
Re:Obligatory... (Score:4, Insightful)
Until you have to lay someone off, you can eat a dick. You don't know what the fuck you're talking about.
Good management will make decisions that don't negatively affect the productivity and profitability of their department while keeping their staff happy AND employed.
I happen to think my team members' livelihoods are more important than my opportunity to appear ingenious. If that makes me look like a fucking idiot to you, fine - I DON'T ANSWER TO YOUR SUBORDINATE ASS. The people I DO answer to fully understand why I made the decisions I made, and they approve.
I can't afford to move my team over to Linux without having either alternate placement for my existing windows based team, or adequate funding and time to make them productive on the new systems - so it ain't happening.
Only a truly shitty manager would think it was worth it to release a team of productive, honest employees to implement a system that is only "better" in a debatable sense.
Re:Obligatory... (Score:5, Insightful)
It's worse for use as a desktop OS than some of the other examples in that list. Building controls, manufacturing controls and SCADA networks are, for instance, examples where Windows is actually passable. Why? A very controlled environment and lack of Internet connectivity. The main source of memory leaks and degradation over time is third-party sources, whether applications or drivers. Windows still has a significant number of inherent security flaws, but in these applications the systems should not be connected to the general Internet. This makes it a lot more difficult for an attacker to access the system.
The control over installed third-party systems and lack of external systems connectivity means that Windows tends to be a lot more stable in these environments than on an average desktop PC. The greatly reduces the potential for the jokes about "viruses" and "Trojans" on these systems the author joked about. It's not necessarily the best tool, as a custom Unix or Linux OS can provide much better general uptime and the ability to potentially fix any issues yourself, but it can be an adequate tool.
Re:Obligatory... (Score:4, Insightful)
Regardless of what else I may do, I am certainly not a Windows expert.
I am taking no extraordinary measures in the day to day operation of my gaming PC.
I run as a limited user.
I patch Windows monthly.
I don't run software that claims to put "HAWT NUDE CHIXXXORZ" "RIGHT ON YOUR DESKTOP!".
It's simple, really.
Re:Medical equipment (Score:4, Insightful)
Many organizations buy into the luster of colorful brochures, happy sales reps, and the idea of the universality of Windows. They just assume there's a guarantee too.
Besides, Linux is a fad, and you know it's made by hackers, and hackers are evil, and it's a variant of UNIX, but it might be illegal too so you'll get in trouble with SCO or Novell or HP or somebody for using it, and besides no two Unixen are the same, etc. etc. etc.
Re:Obligatory... (Score:5, Insightful)
It's simple, really.
So simple that nobody does it, for reasons unknown to anyone.
Are you trolling or just stupid? (Score:5, Insightful)
With Linux there is no accountability.
I don't know if you're a troll or an idiot, but the end result is the same. This is utter and complete bullshit.
My company wouldn't have several dozen fully-paid-up RHEL server licenses if we weren't damn sure who was accountable. We'd slap CentOS or something similar up and save a few bucks.
And if Linux isn't good enough for you, you go with something solid and reliable like Solaris or maybe AIX or possibly (depending on the application) a stripped-down high-reliablility embedded OS. You don't go with some rinky-dink toy like Windows. That's bordering on negligence right there. You can't sue Lego if you rebuild your car's chassis using their plastic bricks, and then get in a auto accident and discover you have no crumple zone. It's not Lego's fault you tried to do something insanely stupid. Using Windows for any sort of critical app where people's lives may be at risk is nearly as stupid and negligent as driving around with nothing but small plastic bricks between you and the SUV in the next lane.
(This story so obviously needed a car analogy.) :)
Re:Obligatory... (Score:5, Insightful)
Agree that it is silly to deploy full OSes for anything like these examples from the article provide.
One thing to note is how many companies are STILL using Win9X based Windows for simple deployments, as most of the examples of the BSOD is the Win9X version. OS/2 is still used at a lot of terminal based installation from banks to cash registers, and not only sadly outdated but overkill and underkill at the same time when you consider the hardware it is running on that has been updated.
One thing the article misses is that there are 'small' and stable versions of Windows that would make a better replacement for most of these usage example. (One of the examples is talking about Windows Embedded but the author doesn't realize such a thing exists, as they are referencing the system as 'Windows' when it is a newer Windows Embedded system.
The funny thing is that Microsoft themselves would not support or endorse the usage of Windows (especially Win9X) in the examples given in the article. This is where ignorance of the developers/implementors is the problem, not Windows or Microsoft.
When you can get Windows Embedded or Windows CE for a tiny fraction of the cost, and use any development from 'regular' Windows on these OSes/Devices there is no reason to be deploying a full OS install on devices or device type applications.
I know everyone would like to yell Linux or (insert your favorite OS here) is the best OS to use in these circumstances, but there are times when Windows is the right choice, and does work better, just not a full installation that is poorly done.
As for NT memory leaks and the guy having to go out to reboot the system. That is a bit of hyperbole that is obvious if you know anything about NT or used it even during that timeframe.
1) Windows NT always has had a scheduler
2) NT also has always had a very good set of scripting abilities from a .cmd or DOS .bat file to even VB Basic applications that ran on it when it shipped and took a few seconds to write it to do whatever you needed. (Hence MS adding VB scripting to Windows later on, as this was all too common already for VB to be used more as a scripting tool than as an application development environment.)
So if this guy was going to a physical location to reboot a box, he is either really stupid, insane or lying. Pick one...
At the very least you could put a restart application in the Task Scheduler and have NT freaking reboot itself. Let alone that the chances are the person was using Win16 applications on NT (especially at this timeframe as Win32 development was not easy or widespread at the time.)
So if the application was Win16, just freaking reseting the subsystem would be a reboot for the application and this is without rebooting the entire OS because of the Win16 leak that was contained.
So ya, this part is made up, bad memories, or someone that was really young and stupid not knowing any better, and you can't blame that off to Microsoft, even if it makes them try to feel better about their work...
Comment removed (Score:3, Insightful)
Re:Obligatory... (Score:5, Insightful)
While that sounds good it doesn't wash. It depends what you are setting up to do. If you want a permissive, bug ridden system where most of your company's bandwidth is used for P2P and every three months your clients call you to tell you their computer has slowed to a crawl, go ahead and use Windows.
Bullshit. Every single "problem" you listed there is indicative of incompetent administration, not the system. Where I work, we have upwards of 5,000 Windows XP desktops, 250 Windows 2003 servers, and a few Redhat Enterprise servers. We don't have any of the problems you listed. Re-imaging PCs is extremely rare because we don't let the users do anything TOO stupid, and the Cisco Catalyst switches prevent any traffic getting out except through our properly configured firewalls. If you're having the problems you list with a Windows network you run, you'd better quit and let a REAL admin take over.
Re:Medical equipment (Score:3, Insightful)
I've seen them. The laptops are in their offices, or connected over VPN's or dialups, even unauthorized dialups. And increasing numbers of medical devices have printing, TFTP, email, and other file transfer capabilities precisely to distribute patient information. with Windows variants in place,they're more vulnerable to remote manipulation: it's a serious danger.
Re:There can be only ONE (Score:3, Insightful)
You do not need to be a programmer to write a few simple databases and it has a nice interface.
Because it makes economic sense, lemming (Score:4, Insightful)
Because, while it might offend your sense of only using the _perfect_ match for the job, the Real World is still driven by money. A cheaper mis-match that works, beats an expensive solution that uses the minimal computer and OS imaginable, just to make a point.
Machines are cheap, people are very expensive. So if you need another half a gigabyte to run Windows there, but you can use existing skills and libraries to make that app, you might actually save millions in the process.
Yeah, you could program most stuff on DOS. And put up with incompatible and glitchy graphics libraries just to have that arrow cursor and some minimal widgets for your app. You could write your own interrupt-based thread simulation, 'cause DOS didn't come with any support for that. And write your own spinlock semaphores at that, and wonder why your app deadlocks. You could still do your own pointer arithmetic to put up with 16 bit addressing in a world of gigabyte-sized data sets, and do your own shitty XMS/EMS block copying just to address more than 640 KB. You could even reimplement most of the network protocols and half the other libraries, because nobody else ported those libraries to DOS. Etc.
Yeah, you could do that, just to willy-wave about your app not needing a full-featured OS at all.
Unfortunately, all that costs money and time. Money and time for your programmers to learn those old, quirky, half-arsed libraries instead of using something they already know and their IDE already supports better. Money and time to debug all the bugs you've introduced in the process. Etc.
And if you think that your reinventing the wheel will be more robust than Windows in the process, well, I can tell you that you might be in for a surprise. Most of the people who rant about how MS should be shot at dawn for having bugs, write far far far worse and less secure code, and some can't or shouldn't write code at all. Which isn't supposed to mean that MS writes good code, but, well, mostly think George Carlin's "Just think of how stupid the average person is, and then realize half of them are even dumber." It applies to programmers too, and doubly so to those who get hired just because they're the cheapest retrained burger flippers and someone thinks that's a cost cutting measure. About two thirds don't even know the language they're supposed to program in, according to one study.
At any rate, if any company did that kind of waste of money just for some fucked-up jihad against MS, I hope the shareholders nail the management to a cross. Because that's certainly a breach of the fiduciary responsibility to make money for the shareholders. Companies are there to make money, not to fight OCPD-nerd crusades.
Re:Obligatory... (Score:3, Insightful)
Re:Medical equipment (Score:3, Insightful)
No they are not. They are however usually connected to a network (since pictures/data are transferred via ipv4). If the hospital chooses to secure it's network it's fine, if not well can't really blame the maker of the device.
I guess most people would be scared if they knew how much hospital equipment is running on windows. However looking at the number of incidents, there aren't really that much reason to be afraid of windows. The real culprit is the software designers (and hospital staff).
Software errors in medical devices has killed people since before Microsoft made it's first OS.
Having a platform more programmers are familiar with might not be such a bad idea...
Re:Obligatory... (Score:4, Insightful)
But that's not Microsoft's/Windows' fault.
It's the games developers' fault.
OK, maybe early versions of Windows didn't encourage strict setting of access permissions - and that has allowed bad games developers to get away with it for too long. Versions of Windows for the past 8 years or so are much better at this, but Microsoft are really between a rock and a hard place with it. With Vista, they've started essentially FORCING people not to run with admin rights all the time (with UAC etc), because the gentle encouragement since W2k hasn't worked, but lots of people moan about that. So, what are they to do?
AFAIAA, all the Windows applications made by Microsoft will run with the appropriate level of user permissions. The problem is with everyone else's applications.
The only reason Linux is 'more secure' than Windows is because all the dumb Windows users are using Windows. If they all moved over to Linux, there'd be millions of Linux boxes logged in as root all the time, with thousands of viruses being written for Linux, Linux based botnets etc etc.
A lot of the reasons people state for why 'Linux rules' are primarily BECAUSE it's not widely used. If you want Linux to keep its good rep, don't encourage average home users to use it!
Records not devices are the problem (Score:3, Insightful)
You would be surprised how much medical equipment is connected to the internet.
No I wouldn't be surprised because I see such devices regularly but I'm not worried about it too much either. The medical devices themselves really aren't the problem. The problems hospitals have with internet connectivity and are mostly related to accessing medical records, scheduling and ordering medicines. When the computers that control those go down THEN chaos ensues [medical-journals.com].
The stuff that is working on acutely ill patients is typically overseen directly by medical staff so if something is not working right it normally is noted quickly. Critical devices like IV drips are typically stand alone so a virus is not a significant concern.
They supposedly have a firewall and a VPN, but their IT department is not so bright,...
My experience with hospital IT staff is that the guys who run the overall network and the critical databases are (usually) pretty bright but the monkeys they hire to maintain the PCs and sometimes man the helpdesk are borderline incompetent. It varies greatly from hospital to hospital though. One time I had the IT staff at a hospital I was working in send TWO guys to swap out a SIMM and I had to walk them through it. But the guys who ran the network were usually quite competent - though extremely overworked.
Re:Obligatory... (Score:3, Insightful)
I have looked at the TCO, and it doesn't pay off. For disclosure though, I don't run a tech department - so my costs involve different things.
I have to be cognizant of the desired skills my team brings to the table and the experience they have using those skills, the ability to jump from one user environment to another frankly isn't one of them.
Re:Seriously? Server OS. (Score:2, Insightful)
It's not a conspiracy, it's that some people, while fine with legitimate criticsm of Microsoft and Windows, are getting a little sick of the frantic tinfoil-hat bullshit that gets thrown around instead of rational cricism around here. For instance, if you routinely use words like "Windoze" or replace the letter "S" with a dollar sign, you might be part of the problem.
Re:Obligatory... (Score:3, Insightful)
What you mean by OS?
a) a Kernel
b) a OS (kernel+tools)
c) Complete software system what is refered as "OS"?
Re:DeepFreeze DeepSchmeeze (Score:4, Insightful)
Indeed, but I've found few of these applications that didn't have better written counterparts.
Re:Obligatory... (Score:3, Insightful)
I don't know where you work, but those symptoms sound more indicative of user (or administrative) stupidity.
Yes, and that's exactly where Microsoft makes most of their sales. That's why they're the market leader.
If you design your system for intelligent users or administrators, you will always have a fringe-market product.
To make the traditional /. auto analogy, can you imagine the sales figures for an auto that was designed for smart, attentive people with a good understanding of auto mechanics?
Re:Obligatory... (Score:3, Insightful)
Re:Obligatory... (Score:3, Insightful)
I'm going to have to question your assertion of quality management when you talk about people's subordinate asses.
If you think that a windows based team can't move over to linux with minimal hassle, or that windows is only debatably "better" for ATM machines despite the virus outbreak that took down nearly half of the ATM's in the country, then you are exhibiting exactly the behaviors which grandparent poster (inelegantly) decries.
If you've hired a team of MSCE certified "programmers" who only know how to program on Windows, you've screwed up right there. Programmers should be general purpose. Otherwise it's like hiring "architects" who can build track houses, but have no idea how to lay out an office space.
Similarly, Windows exhibits behaviors which are quite inefficient from an engineering standpoint. RAM and system requirements for one, which add thermal issues and introduce more points of failure. System stability is better than before, but succeptability to trojans and various other widely known attack vectors makes it a poor choice for security-conscious applications. Cost of data breaches start in the millions and go up significantly. And similarly, network facing applications should avoid Windows due to the high risk of viral infection. Again, see the country-wide ATM outages not too long ago.
Depending upon the job, a switch can greatly reduce per-unit hardware and software costs, as well as reducing future liabilities. The switch shouldn't be terribly hard on your development team, as C is C and platform-specific hooks can be learned quickly, and it makes them more valuable as employees. All of this is positive for the subordinate asses beneath you.
Re:Obligatory... (Score:1, Insightful)
Don't give me that line of guff.
What about those OpenVMS [or insert other OS] guys you turfed years ago when you moved to an all Microsoft shop? Wasn't their livelihoods just as important too?
And you would stick with a microtarded OS (I'm taking Vista here) that will cause your users endless frustration and loss of productivity (yes, Vista will) because you put your own departmental interests over those of the users in your greater organisation?
Sounds like you work for the same IT department that I suffer under.
Good luck to you. Because ultimately your bosses answer to those subordinate asses you refuse to listen to. Once you p-off enough users, you'll be out of there.
Re:Obligatory... (Score:3, Insightful)