Slashdot Mirror


NHS Awards Contract to Microsoft

ChocLinux writes "Microsoft has won a £500m nine year contract to supply software to the NHS, a week after the OGC (the government procurement body) released a report describing Linux as a viable desktop alternative for the majority of government users."

41 of 445 comments (clear)

  1. Candy by fembots · · Score: 5, Interesting

    I think "Microsoft has also agreed to carry out £40m of research and development to provide guidelines and toolkits that will allow ISVs to deliver an NHS-specific user interface" is the candy here.

    MS probably knows it can still compete in customised applications with its almost unlimited resources.

    --
    Play iCLOD Virtual City Explorer [iclod.com] and win Half-Life 2

    1. Re:Candy by metlin · · Score: 4, Insightful

      As much as I'd like to disagree, it's true - MS does have the backing and expertise to do something.

      UIs in Opensource are a really big problem - not because they aren't good, but because they're not _tested_ - UI testing costs money and is not as easy as most people would think.

      Most end users are not CLI geeks, and for them usability plays a _VERY_ important role. Which is why, I strongly support the development of an Opensource usability team.

      If there are usability geeks around here, maybe we could all pitch in and do something. What do you folks say?

    2. Re:Candy by metlin · · Score: 5, Informative

      IAAUD -- I Am A Usability Designer/HCI major.

      Usability design is not merely throwing together a bunch of buttons, fields and text. It's a whole lot more than that and involves some quite well thought and established principles, both quantitative and qualitative.

      The best designs are those that you do not notice and are really intuitive - there is a reason why usability experts get paid so much.

      What I suggested was start something of an Opensource UI consulting group, where a bunch of usability experts could pitch in and help out the development of UIs and do some serious usability testing of interfaces.

      If you _ever_ worked in any half-decent usability project, you'd realize that the time and effort that goes into the precise positioning of a button involves a whole lot more than meets the eye.

    3. Re:Candy by Sputum · · Score: 5, Insightful

      Did you see the CBS election coverage? They had a guy in the "Data Room" with this awesome touch-screen interface. He could navigate it really quickly too, and it looked natural.

      I've been asked a few questions about voice-recognition too.

      People have latched onto the whole 9-key typing of SMSs pretty well. But you're right, people only want to learn things once.

      If you have the choice between a normal bike or one that will take a little while to get used to, which one you gonna choose?

      On the other hand, if the other one has a motor, people will see the benefit and make the effort to switch.

      There's a sort of friction thing going on. Once you overcome static friction the resistive force isn't so much...

      --
      "What we imagine is order is merely the prevailing form of chaos"
    4. Re:Candy by Sputum · · Score: 3, Interesting

      That's a bitchin' idea, and it'll work because it's intuitive, and "Format" being the default button will only hammer home the point.

      You know how you see an ellipsis (...) after some menu options?

      That's meant to mean the menu item will open a dialog. It's been an Apple Interface Guideline for years I think, and it seems to be fairly consistent now across platforms. I wonder how many people notice it?

      --
      "What we imagine is order is merely the prevailing form of chaos"
    5. Re:Candy by djupedal · · Score: 3, Informative

      close the error dialog (which actually is an error monolog in most cases anyway).

      Right, it's not a 'dialog'....it is what's known as a 'modal' window, meaning it floats over the action, as an interrupter/error/alert, not offering an alternate path according to the program's normal flow.

      If it were designed to act and react the same as a 'dialog window' (representing a flow with choices to proceed), it would then present a similar impression to the user, and thus not serve the purpose intended, which is to act as an alert, to which you say 'OK', I got it, let's go back to work. (and then try something else...something else that is not tied to the halt brought about by the alert).

    6. Re:Candy by ajs318 · · Score: 4, Interesting

      One of the things I first started noticing with the strange KDE/Gnome hybrid I ran on my first "proper" Linux box {this was in the KDE2 days, i.e. before KDE was actually any use by itself}, was the way that the button to get rid of a requester, especially one bringing bad news, was usually labelled "dismiss".

      I actually think it's quite sensible. After all, once I've read the message and maybe written it down on a convenient piece of scrap paper, there's not much else I can do apart from get rid of the requester. If I was wearing a tinfoil hat and looking out for black helicopters, though, I'd say labelling the button as "OK" was a way of getting users tacitly to approve of error messages such as "This program has performed an illegal operation and will be shut down" and accept them as a fact of life.

      --
      Je fume. Tu fumes. Nous fûmes!
    7. Re:Candy by Combuchan · · Score: 4, Insightful

      UIs in Opensource seem to be a problem for those who are new to opensource software. While I applaud opensource programmer's efforts in creating easier software which invites more users, I can't help but feel that "tainting the userbase" can come with serious unintended consequences. As you move towards user friendly software, you run the risk of alienating users who like user spiteful software.

      When Microsoft introduced "task oriented" design (such as with folders and control panel applets), they didn't forget about the old users, leaving the option to revert to "classic" views. For the most part, my Windows XP desktop at work looks like Windows 95, and I like it like that.

      Gnome, on the other hand, strived so much for usable software that they alienated their userbase, and thus we have GoneME--indeed, their Project Goals are admirable.

      So much is focused on making opensource pass the Mom test, but I'm afraid of it failing the experienced users test in the process.

      --sean

      --
      "[T]he single essential element on which all discoveries will be dependent is human freedom." -- Barry Goldwater
    8. Re:Candy by squiggleslash · · Score: 4, Interesting
      I've noticed Firefox implements a prime example of why OK and Cancel are bad ideas.

      "A script on this page is causing mozilla to run slowly. If it continues to run, your computer may become unresponsive. Do you want to abort the script? [Cancel] [OK]"

      If you read these as actions, then CANCEL will cancel the script, and OK will say no, the situation is OK. If you read these as direct, literal responses, to the question, then CANCEL means cancel the script, and OK means... erm, OK, abort the script.

      If you're a software developer for the Mozilla team, however, you read it as "OK means yes, CANCEL means no, that is the natural order of things."

      Better wording would have changed the question to "Do you want to continue running the script?", and better still would have been to change the buttons to "Continue" and "Abort script" (as per your suggestion that "Format" should be the button on a disk formatting dialog)

      I should submit a bug about this.

      --
      You are not alone. This is not normal. None of this is normal.
  2. Costs by tuxter · · Score: 5, Insightful

    Only because the roll-out and retraining of hundreds of I.T. staff would have cost them millions in time and lost productivity. This is not entirely surprising, and the primary reason that Linux and open source OS's are not being adopted by the main stream large organisations. It has nothing to do with the stability,functionality and quality of the actual products.

    1. Re:Costs by metlin · · Score: 4, Insightful

      True.

      Most people forget the overhead costs of switching to an entirely new system.

      However, it's worth noting that this is more of a short-term decision than a long-term one. If they did switch to Opensource solutions now, it would cost them money in the immediate future, and loss of productivity.

      However, 5 years from now, once the people are quite used to the new system - it would be a breeze. However, 5 years down the line, the same argument would be used to once again not switch to Opensource.

      It's a vicious circle, and you would have to break out of it at some point of time or the other.

    2. Re:Costs by metlin · · Score: 4, Insightful

      But that argument will keep getting used, unless there is a gradual change that happens, as you said.

      See, you would need to expose people to the new system, and unless you do, you will never make it popular.

      People are used to Windows because it's popular. Why do they want Windows? Because they are used to it.

      Unless other alternatives slowly start creeping in, it's going to be next to impossible.

      Yes, you'd have to break the user-base at some point of time or the other, but it needs to start _somewhere_.

      Not unless we all want to be using Microsoft products 10 years down the line, too. :-) Remember, 10 years down the line, it would be 19 years of being stuck to the same vendor.

    3. Re:Costs by Unordained · · Score: 4, Insightful

      It's funny to hear people talk about how users are accustomed to Windows and won't like to switch. Our software is Windows-based, we use linux in the server room. But our users really don't know how to use Windows -- we still wind up teaching them that yes, you can move windows around; you can minimize/maximize them; tab goes between controls; you can drag icons; no, "my documents" is not the only place on your hard drive; no, you shouldn't open any and all files, ever, by first opening Word and then going to "file", "open" ... and these are people who have been doing data-entry (on computers) for a decade or more. They don't even catch on to the basics from just sitting there using the operating system for eight hours a day. I think we, as programmers, have lost touch with what it means to get accustomed to something new. We think of it in terms of knowing where everything is in the menus, knowing how files will be laid out after a fresh install, knowing where the configuration panels are, etc. Our users ask us to come and find things in the menus for them, like, say, how to print mailing labels -- something that's in the menu, quite obvious, but they won't see because they refuse to explore. They also refuse to read labels, captions on buttons, or any text longer than three words that you throw at them -- but that's another matter. It's not that they're not capable of learning, they just don't want to. You give them OpenOffice, and they'll use it for six months, and then ask to switch back -- not because they couldn't do anything in particular or because stuff was laid out slightly differently, but just because they don't like the idea of running something other than "real" (Microsoft) Office. Sometimes, I think we should just do the "cold turkey" thing and let them deal with it. I think that's the only way they've made it as far as they have -- at some point they had to move from DOS to Windows, I'm pretty sure they didn't like that either. But they did it, and they usually don't look back by now.

    4. Re:Costs by plankers · · Score: 4, Insightful

      I totally agree with you. It's just that people follow the path of least resistance, not what might be better for them in the long term. I've been through a number of migrations of enterprise systems, from one product to another, and the users complain about everything. It isn't surprising to me that IT management wouldn't want to do anything "radical" that would cause people to complain more. Yeah, I know, and you know, that it isn't necessarily that radical, but it's the whole "sticking your neck out" thing, and that's what Linux feels like to a lot of people right now, at least on the desktop. Nobody gets fired for buying Microsoft, it seems.

      Again, I agree with you, and I think that this behaviour is lame. As more work is done by corporations like Red Hat and SuSe on the desktop, as SCO dies and burns in hell, as organizations that are less "risk averse" start switching to Linux on the desktop, things will get better because the stodgy organizations won't feel like they're sticking their necks out so far.

      Now, if IBM were to switch their desktops internally to Linux, and publish their results...

    5. Re:Costs by Tim+C · · Score: 4, Interesting

      People are used to Windows because it's popular. Why do they want Windows? Because they are used to it.

      You're forgetting one more point - all the software they use runs on Windows. Sure, most of it may well have an equivalent alternative for Linux, but in my case that's certainly not all.

      Sure, that's not true of the average office worker, who really only needs email, web access, a word processor and maybe a spreadsheet, but that's the thing about averages; they don't apply to everyone...

    6. Re:Costs by ykardia · · Score: 4, Interesting

      Linux on the desktop will happen, but it will start with call centres, budget airlines, etc, i. e. in situations where the set of software that people are using is small and standardised and there is a lot of pressure to reduce costs, where people need small amounts of training on the software, and where staff turnover is high (you are loosing the knowledge that people have of existing software anyway when they leave).

      Once it starts getting used extensively in these kind of environments, it might gain sufficient critical mass to overcome the "we use Windows because it is popular" trap.

    7. Re:Costs by jeremymiles · · Score: 4, Insightful

      Let's not forget the indirect costs to the workers. People have Windoze machines at home, and they take stuff home to work on it there. They would be using different programs / interfaces at home and work. The program I work with the most (SPSS) is not available for Linux (or Macs, or anything else). (I have made attempts to switch people in my department to the open source R http://www.r-project.org/ as as alternative, but when they saw the interface, they laughed.

      --
      GENERATION 26: The first time you see this, copy it into your sig on any forum and add 1 to the generation.
  3. For the non-british (e.g. me) by jx100 · · Score: 5, Informative

    NHS - National Health Service
    OGC - Office of Government Commerce
    £500 million - $924 million

    1. Re:For the non-british (e.g. me) by Mithrandir · · Score: 3, Informative

      Independent Software Vendor

      Basically any company you can purchase a software "solution" from. May be a single app, or a collection of applications bundled into a single set of services.

      --
      Life is complete only for brief intervals in between toys or projects -- John Dalton
  4. Sales cycle takes time, effort, contact by wombatmobile · · Score: 4, Insightful

    .

    Even if Linux is better/cheaper/faster...

    Decisions like that one from the NHS take a lot of time and effort. The sales cycle is measured in years. Microsoft excels at this process. They have people talking to people and organizations constantly, feeding them material to show their bosses and committees.

    Who is making the corresponding effort for Linux?

  5. Great deal for the department by Dancin_Santa · · Score: 5, Insightful

    So Bleasdale, open source advocate in UK, gets it absolutely right. The current system is already based on MS products, and to try to replace that with Linux all at once would cost more than the half a billion pounds that the new Microsoft license costs.

    However, NHS probably doesn't need all those licenses and MS has them over a barrel with regards to the number of licenses (though expanded by almost 100% in this latest contract). The great number of "cheap" licenses is a disincentive to move to other currently non-supported platforms.

    The key here is that Microsoft has no hold on them to stay with Windows in the long run. Every 3 years the contract comes up for reapproval and during that time if NHS deems it worth switching some systems to Linux, then they can renegotiate for fewer MS licenses at that time. After 9 years, you'd hope that NHS has implemented a solid system framework that can handle a heterogeneous environment of Windows and Linux systems.

    That said, I fail to see how choosing Linux doesn't result into 'lock in'. At least to any extent greater than with Microsoft Windows. Support for Windows can be had from any consulting agency, pretty much. Support for Windows by private consulting companies is far greater in numbers than support for Linux. Linux of course is not tied to a single vendor, but then again it isn't really that big a deal whether the money goes to Redhat or Microsoft, is it?

    The fact is that they will need service on the systems whether they be Windows or Linux. In the short term, Linux is more painful because of the upfront application porting costs involved in switching, but in the long term Linux is still more expensive because of the higher cost support fees demanded by non-Windows consultants.

    This contract is a win/win for all involved. NHS gets the systems it needs, Microsoft gets a boatload of money, and Linux advocates are not barred from introducing Linux systems into the NHS systems.

    1. Re:Great deal for the department by the_weasel · · Score: 4, Funny


      You forgot about the public. The NHS pissed away $800 million of public money that could have been spent on making people well, instead of lining the pockets of Microsoft and whoever had to be paid off to land the deal.


      What a stupid comment. Obviously the NHS should be able to run their IT infrastructure for free. This is because it will be powered by hopes, and dreams, and maintained by leprachauns.

      Then we would all join hands and sing about rainbows.

      Meanwhile, back here in the real world.....

      --
      - sarcasm is just one more service we offer -
  6. So? by anicklin · · Score: 5, Insightful

    The contract was probably written and approved long before the study was made available... So why try and stir up yet another controversy with such a starkly contrasting headline?

    From personal experience, government contracts like that can often take years to design and bid.

  7. Okay by TWX · · Score: 5, Insightful

    Well, I'm not terribly surprised that a contract would be awarded to Microsoft, especially if they are the current provider, but nine years!? That's more than a bit extreme. Three would have made sense, as that's the average lifespan of a Microsoft OS before Microsoft starts reducing support when the new release comes out.

    A lot can happen in nine years. Nine years ago we we had just been formally introduced to Windows 95. Most of our programs were sixteen bit and didn't support long filenames. The average hard disk drive size was something like 400MB. Most new computers had eight, maybe sixteen megabytes of memory. 14400 bps modems were the shit, and vampire-tap thicknet and token ring were the most common network types. Hell, arcnet and Banyan Vines were still viable.

    The biggest thing is that Microsoft wasn't the absolutely overwhelming player that it is today. Many of the big box stores that carried computers had just as many Apple Performas and Quadras as all of the PCs of different brands combined on display. OS/2 could be found on a few machines set up as customer displays displays. Microsoft was not the overwhelming monopoly that it subsequently worked to become. With the headway that non-Microsoft platforms have been making (along with the convergent evolution of Apple's OS along with the other POSIX-alike OSes), nine years from now Microsoft might not be the juggernaut that they are today.

    Already Microsoft is suffering from the rot that any middle-aged empire goes through, just look at the constant, gaping holes in IE, IIS, and Windows that leave users burned by automated attacks time and again. Eventually the right people will become pissed off and the rate of corporate adoption of non-MS software will increase further than it already has.

    Nine years is just way too long.

    --
    Do not look into laser with remaining eye.
  8. something uplifting please by Anonymous Coward · · Score: 5, Funny

    Dear Slashdot Editor,

    Please approve only uplifting stories the rest of the week. I think we've had enough bad news already.

    Sincerely,

    Bummed about Bush

    "The next 4 years could have been great leaps. Now they will be small steps."

  9. Here's how MS does it... by vik · · Score: 4, Interesting

    A few years ago, pirating MS software in the government sector was relatively commonplace. Along comes Microsoft and says: "Either you commit to our systems, or we force and audit and retrospectively sue your arse off for breach of copyright."

    Lo and behold, government departments find themselves locked into expensive Microsoft "deals" thereafter, even though FOSS would be more beneficial to them.

    Paranoid delusions? Well, it's not a decision based on the quality of the code, or the support, and it's not the TCO.

    Vik :v)

  10. Windows didn't win contracts its first 10 years by Saint+Stephen · · Score: 5, Insightful

    Windows 1.0 came out in I think 1984, Windows 3.0 came out in 1989. How many large-scale industrial contracts did Windows win then? Zero. How did Windows get to this point? It started with replacing departmental level servers and workgroups, and proved itself there for ten years or so.

    So, Linux should do the same. Can't expect to be birthed ready to run a marathon.

  11. Not the right time or situation by Omniscientist · · Score: 4, Insightful

    This isn't the right situation to even think about implementing open source software. The system is already running on MS software, and it would be financial suicide to switch the whole thing over to an entire new system, due to labor costs, retraining, etc. As much as I dislike microsoft, if I was making the decision here and I already had a big system based off MS's products, I'd choose to stay with MS.

  12. BSOD by Magickcat · · Score: 3, Funny

    Thankfully none of the medical equipment is going to be running Microsoft products. Otherwise, people would really get the blue screen of death.

    --

    Si tacuisses philosophus mansisses. If you had kept quiet, you would have remained a philosopher.

  13. Re:Stop saying Linux is ready by Coryoth · · Score: 3, Insightful

    Modded troll in minutes. Record time. Congratulations to those who choose to cover their ears and chant "la la la la la".

    In part because it was largely an anecdote that ran counter to a lot of peoples experiences of modern distros. I could tell you horror stories I had with trying to install Windows on a machine and failing to get it to boot properly for hours trying all manner of things - the problem eventually solved by booting the damn thing with GRUB instead of the windows bootloader. That doesn't mean Windows sucks nor that it isn't ready for the desktop, it just means I had a sucky experience.

    If you could actually cite some clear specific reasons (as opposed to vague "everything is unstable/broken/hard" or anecdotes of something not working right for you that usually works fine for everyone else) people might actually listen. You could try making arguments about the ease of 3rd party software installation, or the current infancy of the efforts to provide compatability between KDE and GNOME apps, or the lack of certain significant applications for various major fields (accounting, CAD, whatever), or the lack of Linux support from hardware manufacturers. Then again, all of those issues are undergoing steady improvement, or could change rapidly if there was any significant uptake of Desktop Linux, so maybe they don't let you rant quite the way you want...

    Jedidiah

  14. Doesn't suprise me a bit by SmallFurryCreature · · Score: 5, Insightful
    England is a nation living of its past reputation. To be fair I am dutch and we are living with our head in the sand hoping troubles will go away and that things like political assination, massive corruption, racial tensions happen elsewhere. But back to england.

    England changed massivly during the second world war. Although food supplies became for more limited because they were now rationed out the fast majority of people actually got a better diet. It also saw the start of the National Health Service. The idea that everyone should have access to the same kind of good medical care without having to pay huge bills. To the americans, this is not such a bad idea because healthy workers can worker harder and longer.

    However a NHS is also expensive. Of course the long, intelligent and complex view is that like a public transport system or social services they kinda pay for themselves. While they do not make a profit it is because they reduce the cost of others. A NHS makes sure people are sick less often and don't die so early so they can pay taxes as workers for longer. This is simple. Every kid costs the state money. The same amount wether this kid is a tax payer for 20 years or 40 years. Public transport takes people of the roads. For all those car drivers cursing about money spend on trains while you are stuck in traffic. Just imagine how long the jam would be if the people in the train were on the road with you.

    However certain types of goverment seek election by promising to lower taxes. This works on the simple minded voter. You can't of course lower taxes without spending less and the NHS or public transport are easy targets. Invest a little bit later. Freeze salaries. What will it hurt for 1 term of office eh?

    England now has an NHS wich is a shadow of its former self. "Efficiency" programs have the amount of managers running out of control while the NHS is bleeding developing nations of its nurses while british nurses are going stateside (language is a problem but the pay is better). Health care has gone down the crapper again with it costing more and more for those who are least capable of paying for it.

    Funny thing is that all those cuts on the NHS happened to lower taxes. I wish I could have everyone who voted for lower taxes and who ended up with a higher monthly burden flogged in public for being to stupid to live. Get a clue, it don't matter what you taxation is. What matters is the monthly bill. Simple example. $100 tax bill + $0 medical bill vs $50 tax bill $100 medical bill. Doesn't tax an economic genius to figure out wich is cheaper eh?

    Anyway Blair is a MS fanboy and the NHS is famous for making the totally wrong decission. Buying MS at huge costs because it is cheaper seems business as usual.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

    1. Re:Doesn't suprise me a bit by jrumney · · Score: 4, Funny
      Scotland+England+Ireland+Wales = UK

      Somehow I don't think that was what the IRA had in mind when they fought for a united Ireland.

  15. So what? by Anonymous Coward · · Score: 3, Interesting

    So what? It's not like Red Hat will answer the phone, or return your phone calls, even when all you want to do is throw money at them.

    Exercise for the reader: figure out who your Red Hat rep is and ask them for a price quote on one of their products. Get this done within two weeks. Ready... go.

  16. This seems like a pretty sweet deal... by barfy · · Score: 3, Insightful

    Essentially it seems like that they are getting operating systems, office products, servers/server software for about 60 pounds per machine per year, which I presume includes some level of support and 40 million of custom software.

    Open Source if not quite ready for prime time, is already showing its power in competetive situations..

  17. Re:There's also plenty more too it by beuges · · Score: 3, Informative
    while microsoft discontinues support for old systems, they go to extraordinary lengths to ensure that the API has always remained backwards compatible with all previous versions, to such an extent, that sometimes features have to get dropped because they would break backwards compatibility. for examples, read raymond chen's blog.

    actually, judging from the numerous "warning to users of [x] - [y] doesnt compile under new kernel" posts everytime news of a new kernel gets posted to /., it seems to me that ms's backwards compatibility record is alot better than linux's

  18. NHS IT is too fragmented. by Dr_Barnowl · · Score: 4, Informative
    The largest problem with the NHS infrastructure is their application base, rather than their server platforms, although many of those are antiquated beyond belief.

    I mean, this is an organisation that only recently ditched X.400 email. Most of their practices are either paper-based, or use outmoded legacy systems that no-one understands anymore, because the coders responsible for their creation have been downsized long ago.

    Hardly anything is designed with interoperability in mind ; I have personally resorted to screen-scraping chunks of VT100 terminal output because the other supplier had no handle on their ancient pathology system (and possibly didn't even have the sourcecode).

    The resistance to change is enormous, and not without justification; the overall experience of NHS professionals of IT projects is bad.

    And why? Healthcare is almost certainly one of the most challenging problem domains for IT projects in existence. Not only does it require the reliability and robustness of the banking industry, the informational complexity of the subject matter exceeds most other problem domains in human usage. Even the everyday things like the prescription and administration of drugs are horrendously complex ; the computerisation of a full medical record is something that I would describe as more challenging than a dozen Manhattan Projects.

    In all, this is an area where the potential benefits are tremendous - even a small reduction of the estimated 70% of working time that a junior doctor spends doing paperwork instead of caring for patients would be an enormous boon. An hour a week saved per ward (very realistic even with basic electronic prescribing systems) essentially amounts to an average sized hospital getting a free doctor. In a cash-strapped, overburdened NHS, every little thing helps.

    The potential for public benefit is enormous, and I would suggest that this should be a matter for public research. Instead of pouring these funds into the pockets of shareholders of enormous foreign companies, gov.uk should found a number of public projects, all bound over to interoperate freely, all open-source, and trial them.

    But unlikely to happen, with the corporates back-handing government so effectively. With the recent funding changes for NHS IT, the funds are effectively placed in the hands of a very few huge monolithic corporations, who then decide who to subcontract to. As a result, smaller, more innovative companies are either shoved out of their niche, bought out, or try to compete on an equal footing with the giants and get crushed in the scrum. Money will haemorrhage into the pockets of foreign shareholders (iSoft, Schlumberger-Sema, etc.).

    Yet another reason I'm glad I no longer work for the NHS.

  19. Linux is making inroads by bass_wulf · · Score: 5, Informative

    Maybe the NHS Trust I work for, as part of the Web Development Team, is an exception, but Linux is making inroads here. For example, while our Intranet presently runs on IIS and we do have a large number of third party applications that require IIS, signficant areas (like our homegrown document publishing system) take advantage of having a Linux server in the mix.

    Likewise, I often get involved with extracting useful data from huge data sources and Linux provides me with an efficient and effective way to do that. It's not just me, either. Our network still has a Novell backbone and that is of course moving towards Linux, thanks to SuSE.

    It is, of course, a far cry from Linux on every desktop but the penguin is definitely in there, helping to get the work done.

    Wulf

    --
    Soundcheck Poem: 1 2 was a racehorse and 1 1 was 1 2. 1 2 1 1 race and 1 1 1 1 2.
  20. Background by BenjyD · · Score: 4, Informative

    Just in case anyone has forgotten, here's a quick summary of recent major state-funded IT projects in the UK:

    Immigration service document system (1999) - 18 months late, cost £77m, scrapped after 2 years because system couldn't cope with load

    National Insurance system (1997) - delivered late, didn't work, caused a 14 million record backlog, delayed pensions payouts in 1999 and lost 5.2 million people's tax files

    Passport office(1999): new system less efficient than what it replaced, caused a backlog of half a million applications, price of passport put up by 30% to fund development of replacement system

    Air traffic control(1999): six years late, crashed three times in eight days after installation, complaints from controllers about difficulties with the system.

    So, combine the system that created those blunders and Microsoft, a company with a terrible track record on reliability and honesty. I hope I don't need to go to hospital any time soon.

    Source:http://www.computerweekly.com/Article1023 33 .htm

  21. Re:Tell That To The Underpaid Doctors & Nurses by hoofie · · Score: 3, Insightful

    >>GPs and other health workers that are leaving the NHS in their droves for the private health sector.

    Where's your research for this statement? My wife is a Surgical Matron at a hospital with responsbility for four wards and a lot of staff. She hasn't lost ONE member of staff to the private sector.

    The private sector is not everything is cracked up to be for medical professionals. The management is often poor, and professional development may be limited for Nursing Staff [not much point in specialising in A&E in a Private Hospital - there isnt any]. Consultants are invariably employed by the NHS and top-up their income with private work. Their is no way their is enough private work in the UK to pay the salaries of all the consultants.

    My wife only got her own desktop pc in the last year. For the last 5 years before that she has had to ALL of her paperwork on our pc at home or else beg or borrow access to someone else's at work - and she STILL spent three hours on paperwork at home last night.

    The NHS IT infrastructure has been neglected on a national level for years - at last something is [hopefully] being done to correct that failing.

  22. NHS Massive changes by BrightCandle · · Score: 5, Informative

    The NHS has 9 years remaining of the largest IT project in the world today. The cost is somewhere in the region of £30 billion. The country has been split into different regions, each with a very large IT services company running the show (BT consulting, CSC, Accenture etc). Ther job is to integrate the old systems and bring on new ones to allow patient details to be shared nationally. It is a massive project, £500 million goes to Microsoft to ensure that they will support TODAYS operating systems to the end of the programme so they can get the hard job of getting it all up and working before the OS gets pulled out from underneith them. Once the system works they are in mantience mode and can port it onto the latest and greatest of the day. They have some very very old applications that only run in Windows inside of the NHS today, and they are part of the clincial application suite. The truth is that the NHS believes that Windows is unlikely to disappear in the next 9 years, I think that is a fair assumption myself. Unfortunately they have to think that long term since their software really is that complex. Besides it's all about value, redeveloping the current systems that do work will cost more than paying the licence fees.

  23. Re:There's also plenty more too it by sjames · · Score: 3, Interesting

    new kernel gets posted to /., it seems to me that ms's backwards compatibility record is alot better than linux's

    As someone who remembers downloading SLS Linux one floppy at a time from a BBS over a mighty 2400 baud modem, I recall that once I got the base installed, I used Minicom, gzip, tar, and bash in my efforts.

    To my knowledge, there is no SLS Linux anymore, BBSes are either gone, or moved to the Internet, 2400 baud modems are considered intolerably slow (and are only supported as a fallback protocol that is almost never used). I still use all of those apps. I used fvwm as my window manager once I had X up. Fvwm is still available today should I choose to use it. I can use it with gtk even though gtk wasn't even thought of when fvwm was the default window manager. I recently switched from XFree86 to Xorg. Nothing else had to be changed.

    When the Internet started to be available to non-university students, I got a shell account. I used Slirp to make it act like a slip account. It's still available.

    I still have a few disks with DOS/Windows software from the same era, but it's useless because it won't run on a recent Windows OS.

    Perhaps you don't hear much about it when a new Windows breaks old apps because it's not news. It's just par for the course. Or it may be that you don't hear about it because there's nothing to discuss. Nobody has the source, so nobody needs to know what to change to fix it. Nobody is deciding if it's worth the effort to update it because nobody has a way TO update it. It's just gone.