Slashdot Mirror


HPE To Spin Out Its Huge Services Business, Merge It With CSC (cio.com)

itwbennett writes from a report via CIO: Hewlett-Packard Enterprise announced Tuesday that it will spin off its enterprise services business and merge it with IT services company Computer Sciences Corp. (CSC) to create a company with $26 billion in annual revenue. The services business "accounts for roughly 100,000 employees, or two-thirds of the Silicon Valley giant's workforce," according to the Wall Street Journal. In a statement, HPE CEO Meg Whitman said customers would benefit from a "stronger, more versatile services business, better able to innovate and adapt to an ever-changing technology landscape." Layoffs were not a topic of discussion in Tuesday's announcement, but HPE did say last year they would cut 33,000 jobs by 2018, in addition to the 55,000 job cuts it had already announced. The company also split into two last year, betting that the smaller parts will be nimbler and more able to reverse four years of declining sales.

147 comments

  1. I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 1

    and we billed nearly $300 billion and delivered nothing. CSC is a rotten and dishonest company.

    1. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      And your ObamaCare system delivered even less. I have to wonder about the sanity of people that want even more government control of healthcare.

    2. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      Single payer would reduce costs through more control.

    3. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      That was million, not billion. CSC might be incompetent, but they're not that bad.

    4. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      And left the IRS with no anti fraud system.

    5. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      The republicans say big government doesn't work, and they constantly try to prove that.

    6. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      Which helped the typical white male that is the typical tax evader.

    7. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      But those republicans won't let us have that. Being so close to that but not being allowed that is our hell.

    8. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      If we fed each other the republicans would be defeated. Instead we fought amongst ourselves about inconsequential things.

    9. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      Which is exactly what the republicans wanted.

    10. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      With all of the efficiencies of the DMV and the compassion of the IRS?

    11. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      They think us all simpletons, bit we know.

    12. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      And government control of healthcare would give them the chance to "prove" that.

    13. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      Bernie had a plan to fix that but he wasn't allowed to put it into motion.

    14. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      Bit at least we'd have free healthcare in the meantime.

    15. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      Well the ruler of this corporation is a female Repukian so that prices she hates herself and others.

    16. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      That's how they be.

    17. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      It's a corrupt society so you can't help but to be corrupt within it.

    18. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      Where I come from, people come out swinging, but none of us argue against more government control of healthcare.

    19. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      What! Because we are poor Shall we be vicious?

    20. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      This. We need more government control of doctor's income in order to control costs.

    21. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      Republicans want us to die.

    22. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      Republicans make no sense.

    23. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      The only higher power the republicans believe in is the federal government.

    24. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      Their beliefs are a pile of horseshit.

    25. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      Too bad us working people are spending most of our lives trying not to starve that we don't have time to fight the republicans.

    26. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      The state AGs need to investigate every doctor to make sure they're not making too much money b

    27. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      And controlling the income of doctors is the first order of business for socialized and fair medicine.

    28. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      Even the least of their crimes is enough to justify putting them in the electric chair.

    29. Re: I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      And be easier on the IRS since there would be no ACA penalties.

    30. Re: I worked on the IRS's anti-fraud system... by Opportunist · · Score: 2

      I come from one of those hippie countries with socialized healthcare, and doctors' income is usually not really a concern here.

      What we did was kicking frivolous lawsuits out of the window where you could sue a hospital for a few billions based on "mental anguish" or similar bullshit, lowering their insurance bills and enabling them to provide FAR cheaper rates.

      We also made a distinction between necessary and elective treatment. Reattaching a severed finger is necessary. Moving your nose a few inches up because you think it's not pretty enough is not. The former is paid by your insurance, the latter not.

      And finally we got free routine check ups, the older you get the more frequent they get. Our insurances quickly caught on that it's A LOT cheaper to prevent some diseases from happening than to cure them.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    31. Re:I worked on the IRS's anti-fraud system... by Anonymous Coward · · Score: 0

      CSC are the carneys of government contracting. I'm leaving HPE and I'm very pleased with my timing.

  2. The remaining 1/3 will turn off the lights. by zapatero · · Score: 3, Insightful

    They spun of 2/3 of the company? The enterprise services? They already spun out all manufacturing to HPQ. What's left? Reselling VMWare?

    1. Re: The remaining 1/3 will turn off the lights. by Anonymous Coward · · Score: 0

      Sell the IP. Distribute the cash to the shareholders. That seems to be the plan.

    2. Re:The remaining 1/3 will turn off the lights. by Opportunist · · Score: 2

      HP is a real estate management and financial management company. They just sell electronics stuff so they don't have to deal with those pesky banking regulations.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    3. Re:The remaining 1/3 will turn off the lights. by Sique · · Score: 2
      The remaining HPE will be manufacturing the big iron like the SuperDOME and the ProLiant servers.

      The HP Inc. builts printers and end user equipment.

      --
      .sig: Sique *sigh*
    4. Re:The remaining 1/3 will turn off the lights. by Anonymous Coward · · Score: 0

      They're left with the catering staff I guess, so wait for new HP restaurants near you soon.

    5. Re:The remaining 1/3 will turn off the lights. by jsm300 · · Score: 3, Informative

      Huh? Full disclosure, I'm an HPE employee. Where did you get the idea that HPE doesn't have any hardware products? We spun of HP Incorporated which does the more consumer oriented products that most consumers associated with HP, so that is why they got the original logo. They make printers, laptops, notebooks, desktops and workstations, and a lot more. Basically now we spun off the former EDS that HP bought from Ross Perot some time ago. We're still a major player in hardware. Just go to the HPE website (www.hpe.com) and click on Products. We make servers, from smaller rack servers up to huge Enterprise scale servers. We make storage hardware, network hardware, etc. Basically, if it's something you'd find in a corporate data center, we make it AND support it.

    6. Re:The remaining 1/3 will turn off the lights. by Viol8 · · Score: 2, Insightful

      "We're still a major player in hardware"

      Yeah, just not "printers, laptops, notebooks, desktops and workstations, and a lot more", you know, the things that actually make money...

      "We make servers, from smaller rack servers up to huge Enterprise scale servers. We make storage hardware, network hardware, etc. Basically, if it's something you'd find in a corporate data center, we make it AND support it"

      You're still a runt of a company hived off from a once great corporation. No one cares about HP big iron any more, that died when HP decided HP-UX was yesterdays news and x86 was the way forward. Its IBM , Oracle or Dell + [linux distro of your choice] now.

    7. Re:The remaining 1/3 will turn off the lights. by merky1 · · Score: 3, Informative

      Actually, if HP did go straight to x86, they might have fared better. But they made a huge misstep with IA-64, and hung HP on a more obscure, unstable architecture than anyone else. At that point, they started leaking huge amounts of midn-share, and intel/linux was consistently 1/2 to 1/3 the cost.

      --
      --WooooHoooo--
    8. Re:The remaining 1/3 will turn off the lights. by Viol8 · · Score: 2

      Yeah, Itanium was a disaster, however PA-RISC was competetive. They could have kept developing it but I guess some clueless suit decided to save money and get into bed with Intel.

    9. Re:The remaining 1/3 will turn off the lights. by drinkypoo · · Score: 1, Informative

      Yeah, Itanium was a disaster, however PA-RISC was competetive. They could have kept developing it

      Not only was PA-RISC not competitive on a cost basis making it difficult to sell, but it's also expensive to develop a computing architecture. Doing it badly is part of what killed Sun; they developed a whole architecture they just had to throw away because PC processors surpassed the shit out of it before they brought it to market.

      HP could not afford to keep PA-RISC going. If they had just chosen to go to PC processors they would have done better than dicking with Itanic.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    10. Re:The remaining 1/3 will turn off the lights. by Anonymous Coward · · Score: 1

      Sad thing is neither company should have the name. Agilent should have kept the HP name and logo since that's what actually started HP.

    11. Re:The remaining 1/3 will turn off the lights. by barra.ponto · · Score: 1

      We spun of HP Incorporated which does the more consumer oriented products that most consumers associated with HP, so that is why they got the original logo.

      As an ex-HP from the long ago HP, I still think that the original logo really belongs to what is now Keysight Techonologies.

    12. Re:The remaining 1/3 will turn off the lights. by Anonymous Coward · · Score: 0

      Cheap commodity hardware from China is cheap commodity hardware from China regardless of who you buy it from. It's all ODM as none of the big IT consulting firms designs their own hardware anymore. It's all re-branded SuperMicro or Intel reference designs.

    13. Re:The remaining 1/3 will turn off the lights. by Viol8 · · Score: 2

      I think you're being a bit unfair to Sun there. Sparc , along with most old style Risc CPUs is more efficient with a smaller die size on a Mips basis than the dogs dinner that is x86 with its massive amounts of microcode and legacy baggage.

    14. Re:The remaining 1/3 will turn off the lights. by Desler · · Score: 1

      Huh? Full disclosure, I'm an HPE employee.

      Are your job prospects that poor? Why would anyone stick around at a company whose management is gutting it to make a quick buck?

    15. Re:The remaining 1/3 will turn off the lights. by Anonymous Coward · · Score: 0

      s/x86/itanium

      Fixed that for you

    16. Re:The remaining 1/3 will turn off the lights. by pnutjam · · Score: 2

      Out of the last 5 companies I've worked for, 3 have bought, by preference, majority HP servers, 2 have preferred HP network gear, and the others were more agnostic, but still have some HP hardware.

      HP servers and networking gear are still well regarded in the industry. Yes, you pay a premium ,but most businesses are happy to do so and get a quality product. I still seen Proliant G2's just being retired. Those EOL'd in 2007, but support has been avaliable through HP and third party vendors.

      Disclosure, I currently work for HPE, but this sale probably impacts me.

    17. Re:The remaining 1/3 will turn off the lights. by drinkypoo · · Score: 1

      Doing it badly is part of what killed Sun; they developed a whole architecture they just had to throw away because PC processors surpassed the shit out of it before they brought it to market.

      I think you're being a bit unfair to Sun there.

      It is a well-known fact that Sun threw an entire generation of UltraSPARC design in the wastebin because it was hopelessly outclassed in every way by x86-compatible processors. So no, I am being perfectly, completely, utterly, and in all other ways fair to Sun here. They failed badly. If they hadn't, they might still be with us today.

      Sparc , along with most old style Risc CPUs is more efficient with a smaller die size on a Mips basis than the dogs dinner that is x86 with its massive amounts of microcode and legacy baggage.

      zzzzzfail. You have no idea what you're on about. All modern processors are internally RISCy and the x86 decoder is a fucking footnote in die space compared to stuff like cache. And all modern processors of any complexity have microcode, and you have no idea how much.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    18. Re:The remaining 1/3 will turn off the lights. by davros74 · · Score: 1

      I agree. There was a time when workstation meant a computer used for technical/business stuff, and a PC was a "toy". And during those times workstations were Sun, HP, DEC, etc. I remember using HP-UX machines with "unheard" amounts of RAM (128MB), while a typical PC was still playing games with Expanded vs Extended memory in DOS, typically 4 or 8MB maximum RAM. Linux was not a thing yet. PC's could run Windows 3, but "real" work which needed a Unix workstation meant, Sun, HP, IBM or DEC.

      The Sparc/UltraSparc was a very good processor (and so was PA-RISC and the DEC Alpha) and supported 64-bit long before x86 did, but eventually the evolution of the larger x86 PC market grew to where x86 CPUs caught up to, and then outperformed the workstations of old, and made custom RISC processor development costly and irrelevant.

      As all the RISC CPUs migrated to IA-64, and then got beat by x86-64, there was also the movement away from the different Unices (HP-UX, Solaris, VMS, etc.) to Linux. It was the combination of x86-64 performance and cost improvements coupled with the explosion of Linux on PC hardware that made the old Workstation model obsolete (SPARC/Solaris, PA-RISC/HP-UX --> x86_64/Linux).

    19. Re:The remaining 1/3 will turn off the lights. by Viol8 · · Score: 1

      "All modern processors are internally RISCy "

      Bollocks. The x86 FPU and GPU instructions are risc like , the rest of it is not.

    20. Re:The remaining 1/3 will turn off the lights. by Waffle+Iron · · Score: 1

      Hint: Since the days of the Pentium II, the instructions and registers programmer perceives have had almost zero resemblance to the internal instructions and registers actually used inside the CPU.

    21. Re:The remaining 1/3 will turn off the lights. by Viol8 · · Score: 1

      So what? Thats the same in most modern CPUs. The point is that CISC instructions execute a lot more microcode and hence use more energy than RISC instructions and with CISC the compiler is more limited in what it can do with opcode order shuffling which is unfortunate since the compiler has a much broader view of the program than the CPU will in its instruction cache.

    22. Re:The remaining 1/3 will turn off the lights. by mlts · · Score: 1

      I personally have had good luck with HP/HPE stuff over the years. The Moonshot has yet to be duplicated by anyone, and for places that can't expand or add rack capacity, the only way to add more (other than machine upgrades) is to go with denser racks/blades. iLO holds its own, on the par with iDRAC.

      I do wish HPe would make some G9 MicroServers. For an entry level box in an environment where rackmounting isn't that feasible, they are nice little machines and are definitely worth it for price/performance.

      I definitely wouldn't say HP is dead, but HPe needs to toss something out there, enterprise-wise to get a nose ahead of the competitors. Moonshot and extremely dense rack/blades may be the best thing going for them, especially if they can perfect liquid cooling so that the blades can be far denser without worry about airflow.

    23. Re:The remaining 1/3 will turn off the lights. by rayzat · · Score: 1

      Starting with the Pentium Pro the internal processor core of Intel processors has been essentially 100% RISC. They take the CISC commands and break them into a series of RISC commands and execute. So externally you are correct the commands are 100% CISC but that goes away after decode.

    24. Re:The remaining 1/3 will turn off the lights. by Anonymous Coward · · Score: 0

      [...] on the par with iDRAC.

      Well, I guess that explains why Apple has been hoarding all of their gold lately -- Smaug has his own product line.

    25. Re:The remaining 1/3 will turn off the lights. by Waffle+Iron · · Score: 1

      The most commonly used x86 instructions need no classical microcode. They're no more complex than three RISC instructions (address computation, load plus ALU). They get split into corresponding micro-ops by hardware (not microcode), and are run concurrently in the various CPU logic units, just like modern RISC CPUs. An added bonus is the compact encoding is very beneficial to instruction cache bandwidth.

      I think that you're confusing the issue with the poorly-conceived 80286 era task-level instructions, which nobody uses anymore. That unused microcode languishes in an insignificant lonely corner somewhere on the die.

      If the compiler had more valuable insight into low-level instruction ordering than the actual CPU itself does, then the Itanium would not have been such an epic failure.

    26. Re:The remaining 1/3 will turn off the lights. by Anonymous Coward · · Score: 0

      Yeah, just not "printers, laptops, notebooks, desktops and workstations, and a lot more", you know, the things that actually make money...

      The low-margin run-rate stuff that wasn't making money? The reason they were spun off from the actually-profitable HPE business units?

      No one cares about HP big iron any more

      True, but big iron is very niche overall, these days. Low to mid tier is where the volume and the margins are at.

      Its IBM

      IBM hardware starts at i. Lenovo covers everything below that. Admittedly, the IBM i mid-tier and z big iron nearly has half the market share of HPE, but IBM + Lenovo are still solidly in second place.

      Oracle

      Doesn't even rank, you might find it in the "other" statistical category lumped in with random whitebox OEM chassis. Even Cisco ranks higher.

      Dell

      Distant 3rd place, only covers the low end of IBM/Lenovo or HPE's offerings. It will be interesting to see how things go as the acquisitions continue, though.

      The only bit I can agree with is:

      You're still a runt of a company hived off from a once great corporation

      HP's R&D has gone straight up its own pooper. With the loss of the services divisions, all you're left with is a company that shifts more tin than any other brand-name vendor and occasionally buys other companies, milks their R&D teams and IP for a short while before spinning off the talent and licensing out IP.

      The HPE restructuring was a bit weird though - it's 2 companies with nearly identical leadership and ownership. They've just drawn a line down the product silos and separated them, but maintained control. The story was the low-margin business was dragging down the enterprise sections, but considering the way HP and HPE have been forcing services down everyone's throats (and the margins services usually run at in IT) I'm surprised they've split it again.

      Unless it was decided that all that mere 20% margin server kit was dragging down the services numbers.

    27. Re:The remaining 1/3 will turn off the lights. by drinkypoo · · Score: 1

      Bollocks. The x86 FPU and GPU instructions are risc like , the rest of it is not.

      Alas, you have proven that you are spectacularly mistaken. Wait, not alas. Hilariously. The processor core is RISC-like, and x86 instructions are decomposed into series of micro-ops before actually being executed. This has been true of AMD since the Am586 and of Intel since the Pentium.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    28. Re:The remaining 1/3 will turn off the lights. by drinkypoo · · Score: 1

      If the compiler had more valuable insight into low-level instruction ordering than the actual CPU itself does, then the Itanium would not have been such an epic failure.

      And if anyone would have got it to work, it would have been intel; their compiler is top-notch and they are clearly pretty good at this silicon thing

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    29. Re:The remaining 1/3 will turn off the lights. by Anonymous Coward · · Score: 0

      Me again.

      HP is the last full-stack vendor (if you can ignore the Inc. vs E) - ProLiant, Procurve wired and wireless, 3PAR, desktops, laptops, printers, workstations and many many more. Their enterprise software offerings aren't half bad too, but they don't really go on about it - a shame. EDS was meant to IBM-ise HP into a majority services/consulting focus, but appears to have suffered due to mismanagement, poor marketing and the usual stories with big acquisitions.

      Dell is acquiring pieces like crazy to compete as a full-stack player, they've almost assembled a full house - but the products they buy tend to go the same way as Symantec's acquisitions. I get a bit sniffly when I think of the future fate of VMware and the rest of EMC. Dell aren't really that bad quality-wise, but they're a cheap label without a solid services backing and they insist on making everything have a Dell sticker rather than keeping good brands.

      At least they don't rebrand everything in bright orange and actively work at making products worse, like Symantec.

      I should probably lay of the rambling rants now.

    30. Re:The remaining 1/3 will turn off the lights. by Desler · · Score: 1

      The so what is the fact that you're laughaby wrong in your statements and characterizations. So you're saying that accuracy doesn't matter?

    31. Re:The remaining 1/3 will turn off the lights. by plopez · · Score: 1

      ES is dying and the industry is consolidating. It makes sense. What is left is mostly storage (including support for legacy tape drives!), networking, and software. And yes VMWare but also Open Stack.

      --
      putting the 'B' in LGBTQ+
    32. Re:The remaining 1/3 will turn off the lights. by plopez · · Score: 1

      They had the DEC Alpha and then gave it away to Intel for promises. So yes, it was the clueless suits.

      --
      putting the 'B' in LGBTQ+
    33. Re:The remaining 1/3 will turn off the lights. by Anonymous Coward · · Score: 0

      Actually, Compaq had already disbanded the Alpha before Carly came up with that brilliant idea of buying Compaq. And the decision to retire PA-RISC for Itanic was that of Lewis Platt.

    34. Re:The remaining 1/3 will turn off the lights. by Anonymous Coward · · Score: 0

      Why do you think printers and desktops make a lot of money? Are you new to the industry? Those things are commodities now, and I can tell you first hand that those businesses are suffering.

    35. Re:The remaining 1/3 will turn off the lights. by Guy+Harris · · Score: 1

      And all modern processors of any complexity have microcode, and you have no idea how much.

      What do you mean by "microcode" here? Do you mean it in the traditional sense, wherein the CPU's instruction-execution state machine is implemented as a set of microinstructions? If so, could you cite some papers indicating that, for example, the SPARC M7, or the POWER8, or the Itanium 9500, have microcode in that sense?

    36. Re:The remaining 1/3 will turn off the lights. by Guy+Harris · · Score: 1

      The processor core is RISC-like, and x86 instructions are decomposed into series of micro-ops before actually being executed. This has been true of AMD since the Am586 and of Intel since the Pentium.

      Pentium Pro, not Pentium.

      I infer from IBM's use of "micro-operation" in papers about recent z/Architecture processors that it's also true of z/Architecture. (BTW, two of the first implementations of the System/360 ancestor of z/Architecture, the System/360 Models 75 and 91/95, implemented the instruction set entirely in hardwired logic rather than microcode; the other models used microcode.)

    37. Re:The remaining 1/3 will turn off the lights. by drinkypoo · · Score: 1

      I agree. There was a time when workstation meant a computer used for technical/business stuff, and a PC was a "toy".

      And then the PC processors began to spank the workstation class CPUs on nearly every basis.

      And during those times workstations were Sun, HP, DEC, etc.

      All of which also built x86 Unix systems and sold Unix for x86 PC clones. You're also conspicuously leaving out IBM, which also made PCs and Unix for PCs and even something weird and in between, the IBM PC/RT; on which you could run AIX or BSD. It had an ISA bus and the most fancy-pants model had a whoppin' 16MB RAM.

      I remember using HP-UX machines with "unheard" amounts of RAM (128MB), while a typical PC was still playing games with Expanded vs Extended memory in DOS, typically 4 or 8MB maximum RAM.

      Sure. There was a time like that. PCs used cheap 8-bit SIPPs or SIMMs if they didn't actually use DIP DRAM like my first 32-bit PC, a 386DX25. It had 8MB of the stuff which took up something like 100cm^2. I was poor, so it was a hand-me-down. It was also my first Linux machine, but that's another story.

      Linux was not a thing yet. PC's could run Windows 3, but "real" work which needed a Unix workstation meant, Sun, HP, IBM or DEC.

      I'm not going to argue that Windows 3 was better than Unix. This is not about that.

      The Sparc/UltraSparc was a very good processor

      It was, but even by the time of the UltraSparc it was clear that it was a bit expensive for the level of performance. PCs were starting to catch up with it, and some of the UltraSparc workstations might as well have been PCs except for their processors. They had PCI buses, CMD IDE chipsets (and for that matter, IDE and not SCSI discs) and the build quality was not what it was in days of yore.

      eventually the evolution of the larger x86 PC market grew to where x86 CPUs caught up to, and then outperformed the workstations of old, and made custom RISC processor development costly and irrelevant.

      POWER is still going strong. But that underscores the point that it's costly; only IBM is managing it.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    38. Re:The remaining 1/3 will turn off the lights. by Guy+Harris · · Score: 1

      If the compiler had more valuable insight into low-level instruction ordering than the actual CPU itself does, then the Itanium would not have been such an epic failure.

      Perhaps leaving all instruction scheduling up to the compiler, as with Itanium, was harder than having the compiler schedule instructions (as is done by many compilers, including x86 compilers) and then having the processor reorder them (as is done on RISC processors) or chop them into micro-ops and recording them (as is done on x86 and z/Architecture processors).

    39. Re:The remaining 1/3 will turn off the lights. by drinkypoo · · Score: 1

      I infer from IBM's use of "micro-operation" in papers about recent z/Architecture processors that it's also true of z/Architecture.

      IBM is huge on microcode, they are more into it than anyone else. I always forget which x/ notation corresponds to which name of old, so I will just use the old names and you can figure out which is which. I presume that POWER itself when implemented for RS6k has about a normal amount of microcode; I know there is some. Last I looked, AS/400 systems even when they were still being called that were being implemented as a wrapper around POWER or even PowerPC, depending on model. They had literally no other platform for it to run on. And AFAIK that is basically true of all their hardware now, it's all POWER-based at some level. That is probably a very wise strategy, since there's probably no other way to get it to pay for itself. They saw what happened to the vendors which failed to maintain their own architecture and they've successfully found ways to keep it going.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    40. Re:The remaining 1/3 will turn off the lights. by Guy+Harris · · Score: 1

      I agree. There was a time when workstation meant a computer used for technical/business stuff, and a PC was a "toy". And during those times workstations were Sun, HP, DEC, etc. I remember using HP-UX machines with "unheard" amounts of RAM (128MB), while a typical PC was still playing games with Expanded vs Extended memory in DOS, typically 4 or 8MB maximum RAM. Linux was not a thing yet. PC's could run Windows 3, but "real" work which needed a Unix workstation meant, Sun, HP, IBM or DEC.

      ...the first of which had an, admittedly unsuccessful, 386-based workstation (along with their 68k and SPARC-based workstations).

      As all the RISC CPUs migrated to IA-64,

      They didn't. Only PA-RISC did.

      and then got beat by x86-64, there was also the movement away from the different Unices (HP-UX, Solaris, VMS, etc.) to Linux.

      Presumably you meant "(HP-UX, Solaris, AIX, etc.)"; VMS wasn't a UNIX, but AIX is one of the three remaining Big Server Commercial UNIXes, along with HP-UX and Solaris.

      It was the combination of x86-64 performance and cost improvements coupled with the explosion of Linux on PC hardware

      ...and the availability of 32-bit and later 64-bit Windows, and of versions of traditional "engineering workstation" software for Windows, so that you no longer needed a traditional commercial UNIX running on a RISC-based workstation.

    41. Re:The remaining 1/3 will turn off the lights. by Guy+Harris · · Score: 1

      Cheap commodity hardware from China is cheap commodity hardware from China regardless of who you buy it from. It's all ODM as none of the big IT consulting firms designs their own hardware anymore. It's all re-branded SuperMicro or Intel reference designs.

      I.e., all the HP Integrity system boards, including the Itanium-based ones, are Intel reference designs?

      (Obviously, neither Oracle's SPARC machines, nor IBM's Power ISA or z/Architecture machines, are based on Intel reference designs, as Intel don't make SPARC, POWER, or z/Architecture processors.)

      (I'm ruling SuperMicro out here, as I rather doubt they make any Itanium, SPARC, Power ISA, or z/Architecture boards.)

    42. Re:The remaining 1/3 will turn off the lights. by Guy+Harris · · Score: 1

      s/x86/itanium

      Fixed that for you

      If it ain't broke, don't break it by trying to fix it. When HP decided that Itanium was the way forward, that was "HP-UX on Itanium" for their machines, so they didn't "[decide] HP-UX was yesterdays news" at that point.

      Presumably by "decided HP-UX was yesterdays news and x86 was the way forward" the person whose statement you're "fixing" was referring to HP announcing Xeon-based Superdome servers not running HP-UX, and HP-UX not being ported to x86.

    43. Re:The remaining 1/3 will turn off the lights. by Guy+Harris · · Score: 1

      I infer from IBM's use of "micro-operation" in papers about recent z/Architecture processors that it's also true of z/Architecture.

      IBM is huge on microcode,

      So I guess they abandoned that whole silly "801" "RISC" project when they found it didn't have any microcode. Good thing they did, or they'd have ended up with a line of RISC processors.

      I presume that POWER itself when implemented for RS6k has about a normal amount of microcode; I know there is some.

      And how do you know this?

      Last I looked, AS/400 systems even when they were still being called that were being implemented as a wrapper around POWER or even PowerPC, depending on model.

      The predecessor to AS/400, System/38, was an interesting system. They had two layers that they referred to as "microcode" but, as Frank Soltis, one of the chief architects if not the chief architect, noted in one of his books on AS/400, that was a legal fiction for the higher level of "microcode". The underlying processor had a System/3x0-ish instruction set, implemented on a processor that used horizontal microcode to implement it. It then had something called "vertical microcode", made up of instructions in that System/3x0-ish instruction set, running from main memory. However, the uber-CISCy instruction set generated by compilers/a> doesn't get interpretively executed by the "vertical microcode"; instead, the "vertical microcode" translates the MI instructions into the same instruction set as the "vertical microcode" uses, and runs it from main memory as well.

      Soltis says this was done because IBM were worried that they might be forced to sell their OS software for use on compatible hardware, and they wanted to make sure that didn't happen with System/38, so they put the development of the low-level OS and binary-to-binary translation code under a hardware manager, and called it "vertical microcode", so they could claim it wasn't system software and didn't have to be unbundled.

      That continued with AS/400 - which allowed them to replace the old CISC instruction set with an extended PowerPC instruction set without breaking binary compatibility - the OS would just retranslate the MI instructions to PowerPC code and run that. (The result of the translation are cached on disk along with the "source" MI code; apparently, AS/400 allowed the "source" code to be discarded, presumably to save disk space, and if you did that, you'd have a problem switching to the RISC machines.)

      And AFAIK that is basically true of all their hardware now, it's all POWER-based at some level.

      Nope, the z/Architecture microprocessors natively run the z/Architecture instruction set; the designers of the z/Architecture and POWER chips might talk to each other and use some hardware in common, but the z/Architecture CPUs are not POWER-based.

    44. Re:The remaining 1/3 will turn off the lights. by Guy+Harris · · Score: 1

      And during those times workstations were Sun, HP, DEC, etc.

      All of which also built x86 Unix systems and sold Unix for x86 PC clones.

      Sun did, when they made the Sun386i running SunOS 4.0.x; it wasn't a big success (and wasn't PC-compatible). HP and DEC made PCs, but didn't port their own UNIXes to them, and so obviously neither ran HP-UX nor Ultrix nor Digital UNIX on them nor sold HP-UX nor Ultrix nor Digital UNIX for other people's PCs.

      You're also conspicuously leaving out IBM, which also made PCs and Unix for PCs and even something weird and in between, the IBM PC/RT; on which you could run AIX or BSD. It had an ISA bus and the most fancy-pants model had a whoppin' 16MB RAM.

      ...and a non-x86 processor (and it was the "IBM RT PC", not the "IBM PC/RT").

    45. Re:The remaining 1/3 will turn off the lights. by drinkypoo · · Score: 1

      ...and a non-x86 processor (and it was the "IBM RT PC", not the "IBM PC/RT").

      Yes, it had the first commercial RISC processor, in fact. And who cares what it was called, I had five model 135s, and I gave them away. There was just no point.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    46. Re:The remaining 1/3 will turn off the lights. by drinkypoo · · Score: 1

      If so, could you cite some papers indicating that, for example, the SPARC M7, or the POWER8, or the Itanium 9500, have microcode in that sense?

      It probably does not apply to SPARC, I am fairly certain that there is microcode involved at minimum in some POWER processor coprocessors but can't find a reference, there is absolutely microcode in Itanium and Intel has used it to fix errors.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    47. Re:The remaining 1/3 will turn off the lights. by Guy+Harris · · Score: 1

      If so, could you cite some papers indicating that, for example, the SPARC M7, or the POWER8, or the Itanium 9500, have microcode in that sense?

      It probably does not apply to SPARC, I am fairly certain that there is microcode involved at minimum in some POWER processor coprocessors but can't find a reference, there is absolutely microcode in Itanium and Intel has used it to fix errors.

      There's firmware , but it's not clear from what Intel says there that it's "microcode" in the conventional sense, as opposed to low-level Itanium instruction set (the instruction set formerly known as IA-64) code.

  3. Those who don't learn from history... by Tablizer · · Score: 1

    Tech mergers rarely work. Why are they gambling? Is there a hidden shell game here that make a few select executives and lawyers rich while screwing everything else?

    1. Re:Those who don't learn from history... by Anonymous Coward · · Score: 0

      Tech mergers rarely work. Why are they gambling? Is there a hidden shell game here that make a few select executives and lawyers rich while screwing everything else?

      Why do you even ask? There are always a few people that make a huge profit from this kind of events, even if it ends up being a complete disaster, which is likely in this case. And for screwing everyone else, the summary already speaks of ~88000 people losing their job.

    2. Re:Those who don't learn from history... by Anonymous Coward · · Score: 0

      It's as much a demerger as it's a merger, since it's being spun out of HPE and merged with a business in the same industry (b2b services), which in turn should allow for greater efficiency savings. There's been a few notable instances of such de-diversification in the IT sector, in recent years; aside from HP, IBM's another example. Maybe it's only some kind of fad among managers, but seeing how they're paid some insane salaries for their work, it could just be that they know what they're doing, done their work, assessed the market conditions, and determined this to be the right course of action in today's IT market.

    3. Re:Those who don't learn from history... by Anonymous Coward · · Score: 0

      It's as much a demerger as it's a merger, since it's being spun out of HPE and merged with a business in the same industry (b2b services), which in turn should allow for greater efficiency savings. There's been a few notable instances of such de-diversification in the IT sector, in recent years; aside from HP, IBM's another example. Maybe it's only some kind of fad among managers, but seeing how they're paid some insane salaries for their work, it could just be that they know what they're doing, done their work, assessed the market conditions, and determined this to be the right course of action in today's IT market.

      Know what they're doing? Hah, that's the joke of the year, I'd like to know what you're smoking. It must be some seriously good stuff!
      I'm old enough to know that these guys "strategic vision" are essentially a fad which changes every few years. There have been some exceptions (Steve Jobs among them) but they are the exception rather than the rule.

    4. Re:Those who don't learn from history... by Opportunist · · Score: 4, Insightful

      It's restructuring. It's what company managers do when they notice that their revenues plummet and they somehow try to hold on to their comfy chairs, which they could not if it seems like they do nothing to deal with the plummeting revenue.

      Once they notice that they can't do anything sensible (usually after spending a million or two on consulting, which usually makes me wonder what the fuck these goofballs are doing if they need someone telling them what to do any time a serious decision that goes beyond choosing the correct iron on the golf course is due), they need to do SOMETHING to appease shareholders.

      Restructuring is perfect for this. One, it looks like you're doing something, two, it makes you look like you know what you're doing and three, it may cost whatever it costs because, hey, restructuring takes time and costs money, everyone knows that. But afterwards it's going to be SO much better that the new revenue boost will easily recover this in a year. Two, tops.

      And two years later, you have a new CEO.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    5. Re:Those who don't learn from history... by Opportunist · · Score: 4, Funny

      On a lighter note, a topical joke:

      A new CEO is examining his new office. In a drawer, he finds a note and three sealed envelopes. The note says "Hello, dear successor. You find here three numbered envelopes. Every time your numbers look bad and the board wants your head, open them, in order, and do what you find inside."

      Well, not even a month after he took the helm, he creates his first huge blunder. Desperately he opens the first envelope and reads

      "Blame your predecessor"

      He does at the meeting and the board is appeased. Everything keeps going ok for a while until his numbers start to plummet and the board wants answers. He opens the second envelope and reads

      "Restructure"

      He does, everyone's busy restructuring and nobody can identify who is to blame for the increased costs. But after a while, restructuring is pretty much done but the increase in revenue is not coming in. Desperately he opens the third envelope and reads

      "Prepare three envelopes"

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    6. Re:Those who don't learn from history... by Anonymous Coward · · Score: 0

      I'm old enough to know that these guys "strategic vision" are essentially a fad which changes every few years.

      I'm not exactly a spring chick, either. In any case, I suspect you're being misled by the word strategic. These people conduct market analyses for the current market, and maybe do some predictions < 5yrs ahead, because that's what the investors want from a mature business, i.e. divis now and not 10 years down the road, and ultimately they're very unlikely to still be in charge of the business a decade after making any such "strategic" decisions. Finally, comparing Apple under Jobs to HPE? Really? The former was very much B2C company, while the latter is purely B2B (it's even in the company name!), so yeah, apples and oranges.

    7. Re:Those who don't learn from history... by Anonymous Coward · · Score: 0

      Your definition of "work" is wrong.

      The primary industry in the USA is Mergers and Acquisitions. It's what keeps those high-level execs in multi-billion dollar bonuses and guarantees them a humongous income, success or fail. First you buy, then you spin off, then you buy again. Repeat.

      Actually producing products or services is basically immaterial.

      It "works" just fine and gives you all the benefits of Capitalism without actually using your capital for anything productive.

    8. Re:Those who don't learn from history... by bluefoxlucid · · Score: 1

      What worked in 1790 doesn't work in 2016. Companies need to restructure as markets change; and markets change as technology changes.

      Millions of people working to produce and manage servers... and then we moved to cloud technology and virtualization, and now one person provides that server management for 20 companies who are all dangling off 1 VM host with 5 times the hardware as a single of the (20) servers it replaces. It suddenly takes 8% as many employees to do the same job, and people start leaving old-hat in-house service and paying 10% as much for outsourced "cloud data centers". Your company is standing around, overfed and fat as hell with 12 times as many employees as it needs to provide the same services as ever. what do you do?

      Answer: You restructure. You change your business model. You change your internal processes to match modern technology, eliminating the need for thousands of your employees, whom you lay off. You cut prices on those services they provided to match competitors who are providing the same for half the price--after all, you're not paying nearly as many employees to make that thing now, so it doesn't cost you all that much anymore. You transition off high-labor services onto cheaper, low-labor services that give your customers the same outcome at lower costs, pricing those even lower than your legacy services in a bid to get out of the clunky, old, unprofitable market and into the new, efficient one.

      Before you know it, $250/month ISDN 128k internet service becomes $70/month 2,000,000k cable-delivered internet service.

    9. Re:Those who don't learn from history... by Tablizer · · Score: 1

      Indeed. BS is America's comparative advantage.

    10. Re:Those who don't learn from history... by Opportunist · · Score: 1

      Nobody said that you should work as you did 200 years ago. But many companies are locked in permanent restructuring. And we're not talking about introducing a new technology, this is about shuffling personnel and, more important, departments from one management position to the other in what I liked to call "corporate gerrymandering" when I was still in consulting. The goal is basically to ensure he controls all the profitable areas of the company and manages to push all the unprofitable (but necessary) ones on a rival. To accomplish this, "restructuring" is usually the key.

      And since everyone does it, and hence all management really does in such companies is perpetual restructuring, this does not end. And it leads nowhere, since the goal isn't to get more productive but to make some manager look good.

      Sometimes I really wonder how these companies survive. I have a hunch it's by squeezing out even more for even less from the few further down the corporate ladder who actually do work there.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    11. Re:Those who don't learn from history... by bluefoxlucid · · Score: 1

      Sometimes I really wonder how these companies survive.

      The answer is simple: they're run by executives who actually know what they're doing, and who aren't actually playing out the fanciful narrative you've described. Some businesses are projectized, and so don't have firm functional divisions; others operate in less-rigid ways, and so are able to restructure on-the-fly without the mass expense an old-style 1920s office would face when trying to reorganize. We've done a lot of research since 1970 on how to get things done and how to minimize the risk of change, both by avoiding it and by expending ~1% of the cost of potential change so that such changes end up costing ~5% as much if they do happen.

      I get shuffled about, but it's a zero-cost operation. Somebody clicks a button and the manager responsible for my time is some other department head. When budget time comes, that guy's department pays the cost of my salary, and the balance sheets show different expenses from different areas. There is so much slack in the day that this operation doesn't even impede the normal work of whomever is assigned to it--we've come a long way from factory work, although not so far if you're a programmer (programmers spend nearly 100% of their time thinking about how to accomplish a task or accomplishing that task, and have much less slack time than other office workers).

  4. Is a asset stripper in charge? by Viol8 · · Score: 2

    This has a rotten smell to it. Seems to me HP is being slowly dismantled for money. A great company slowly being flushed down the toilet by short termist used car salesman types.

    1. Re:Is a asset stripper in charge? by SeaFox · · Score: 4, Insightful

      Not so sure HP has been a "great company" for some time.

      I wonder what sort of debts they will try and push onto whatever this remainder-of-HPE company is going to be. Gotta find a way to get that "clean slate" by scuttling the old ship with undesirably consequences of past leadership's transgressions, not to mention least favorite people. Those brave souls who remain will steer the old wreckage to the bottom of Bankruptcy Bay. A few will plan golden life rafts to escape the undertow that pulls hapless stockholders down with it.

    2. Re:Is a asset stripper in charge? by Anonymous Coward · · Score: 0

      Nice analogy, but the idea that sinking ships create an undertow is a myth. eg https://en.wikipedia.org/wiki/Charles_Joughin - "he was on the outside the ship as it went down by the head. As the ship finally sank, Joughin rode it down as if it were an elevator, not getting his head under the water".

    3. Re:Is a asset stripper in charge? by drinkypoo · · Score: 1

      Survivors of sinking ships report having been sucked down with their ship. Perhaps not all ships are created equal.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    4. Re:Is a asset stripper in charge? by ShanghaiBill · · Score: 2

      A great company slowly being flushed down the toilet by short termist used car salesman types.

      The decline of HP had little to do with short-termism, and much more to do with long-term technological change. HP did well when computers cost $5k, and printers cost $3k, and people were willing to pay a few thousand extra for top quality. Now, computers cost $500, printers cost $50, and there is little difference is quality between brands. HP's old business strategy just doesn't work anymore. You can't charge a premium when you are selling commodity goods, and you can't compete on price against Foxconn.

    5. Re:Is a asset stripper in charge? by psmoot · · Score: 1

      This has a rotten smell to it. Seems to me HP is being slowly dismantled for money. A great company slowly being flushed down the toilet by short termist used car salesman types.

      The rotten smell could be coming from the services division. Sounds like Meg noticed the EDS acquisition wasn't panning out so toss the mess to someone else and cut your losses.

      I'm really not sure what HPE has left. x86 servers, storage systems, some network stuff. The servers and blades are pretty well respected. I work at a storage competitor and we kind of laugh at HPE storage. The network gear they had when I worked at HP was pretty good but not nearly well respected as Cisco and other giants. There's nothing which is a real standout that I know of. You've got to be the best at something and I'm not sure what that something is for HPE.

      This also seems eerily like Agilent. HP's test and measurement got spun out and kept shrinking and shrinking. It's still around but a shadow of its former self.

    6. Re:Is a asset stripper in charge? by Enigma2175 · · Score: 1
      --

      Enigma

    7. Re:Is a asset stripper in charge? by bluefoxlucid · · Score: 1

      What's funny is HP slowly dying while people scream "OMG LAYOFFS!", complaining HP is an unprofitable behemoth and then freaking out when they fire people who aren't useful for anything because HP has employees to provide 1 billion hours of service but has customers to buy 200 million hours of service.

    8. Re:Is a asset stripper in charge? by drinkypoo · · Score: 1

      Yes, but their test was fairly meaningless, because it was a pretty small ship. The people who have survived to report being sucked down were on larger ones. As usual, myth not busted.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    9. Re:Is a asset stripper in charge? by plopez · · Score: 1

      Dismantling Carl's and the two clowns legacy. HP Inc. was mostly Compaq and ES was the purchase of EDS. Which isn't too bad of an idea.

      --
      putting the 'B' in LGBTQ+
    10. Re:Is a asset stripper in charge? by plopez · · Score: 1

      oops. I meant Carly

      --
      putting the 'B' in LGBTQ+
    11. Re:Is a asset stripper in charge? by Anonymous Coward · · Score: 0

      Got an example ?

  5. Anti-trust? by Carewolf · · Score: 2

    I wonder if that will be allowed.. Won't the new company have a near monopoly on incompentent consultancy, generally being bloody useless?

    1. Re:Anti-trust? by Anonymous Coward · · Score: 0

      Incompetent consultancy is generally seen as a pleonasm here. In this case they will fail, good riddance I'd say. The only sad thing is that the few competent people will lose their job while managers with so called "long term strategic vision" will earn a lot if undeserved money. Their "strategic vision" only targets their bank accounts.

    2. Re:Anti-trust? by Anonymous Coward · · Score: 0

      Lots of fierce competition in the incompetent consultancy business...

    3. Re:Anti-trust? by Anonymous Coward · · Score: 0

      There is positively no shortage of incompetent consultants.

      Booze Allen
      Accenture
      IBM
      Grant Thornton
      Bain
      Deloitte
      McKinsey
      the list goes on...

      No anti-trust to worry about here.

    4. Re:Anti-trust? by ShanghaiBill · · Score: 4, Funny

      Won't the new company have a near monopoly on incompentent consultancy?

      Not at all. There is IBM, Andersen, McKinsey, etc. Incompetent consulting is a big and competitive business.

    5. Re:Anti-trust? by psmoot · · Score: 1

      I hear there's a mutant space goat about to eat the planet so we need to build three space arks...

  6. Writing meet Wall - Probably by Anonymous Coward · · Score: 1

    I used to work for a little company called Nortel Networks, they outsourced their entire IT group to CSC. 18 months later CSC announced massive layoffs in 6 months meaning people were given "adequate notice" and their history of severance payments wasn't anywhere as good as Nortel's. This meant that severance packages could be minimal. The rest is history. The rumor mill said that a big part of CSC's business was helping large companies downsize and avoid some of the costs of layoff, I never researched it but it was what happened to me.

  7. I wonder if EDS is part of this spin-off? by Anonymous Coward · · Score: 0

    Poor EDS has been manhandled a fair amount!

  8. Doctor's salaries aren't the big problem by sjbe · · Score: 3, Interesting

    I come from one of those hippie countries with socialized healthcare, and doctors' income is usually not really a concern here.

    Doctor's income has very little to do with the skyrocketing cost of health care here in the US. In fact a huge portion of doctors don't actually have take home pay much different than a well paid software engineer. An internal medicine doctor in solo practice can work 70-100 hours per week and maybe take home $80-150K/year when all is said and done. Other doctors do better financially (particularly specialists) but the big drivers for health care costs are demonstrably not doctor's salaries. Those doctors who do make bigger salaries tend to be economically far more valuable than their take home pay.

    The big drivers of cost (in no particular order) are perverse treatment incentives relating to insurance, high drug costs, uncontrolled hospital billing, ridiculous administrative burden, lack of modern and interconnected computer systems, fraud, lack of a single payer entity, torts and actions to protect from torts, overuse of expensive medical equipment, and a few other things. Salaries of staff is a consideration too but it's not even in the top 10 problems driving health care costs. In fact there is a shortage of adequately trained staff in many parts of the country.

    What we did was kicking frivolous lawsuits out of the window where you could sue a hospital for a few billions based on "mental anguish" or similar bullshit, lowering their insurance bills and enabling them to provide FAR cheaper rates.

    And what do you do when you really do get screwed by an incompetent hospital? I'm quite sure that happens just as often as it does here in the US. What is your recourse when something goes horribly wrong?

    We also made a distinction between necessary and elective treatment. Reattaching a severed finger is necessary. Moving your nose a few inches up because you think it's not pretty enough is not. The former is paid by your insurance, the latter not.

    That is no different in the US. Elective cosmetic surgery is rarely covered by insurance except for cases related to reconstruction following an accident or serious illness. Your botox injection will not be covered by any insurance that I am aware of. My wife is a physician in a dermatology practice and they make a ton of money from elective cosmetic procedures not covered by insurance. (Vanity literally has a price)

    And finally we got free routine check ups, the older you get the more frequent they get.

    They're not free. You just pay for them with tax dollars instead of insurance premiums. I agree that they are a good idea and I think the US does it in a retarded way but let's not pretend it's free just because you didn't get presented with a bill when you left the office.

    1. Re:Doctor's salaries aren't the big problem by parkinglot777 · · Score: 2

      Doctor's income has very little to do with the skyrocketing cost of health care here in the US. In fact a huge portion of doctors don't actually have take home pay much different than a well paid software engineer. An internal medicine doctor in solo practice can work 70-100 hours per week and maybe take home $80-150K/year when all is said and done. Other doctors do better financially (particularly specialists) but the big drivers for health care costs are demonstrably not doctor's salaries. Those doctors who do make bigger salaries tend to be economically far more valuable than their take home pay.

      Actually, I think it is a part of the cost as well. Doctors are supposed to pay for malpractice insurance which takes a big chunk out of the doctor's paid. In order to keep $80k~$150k/year, the real gross income for doctors is much higher than that (could be about double). As a results, a doctor visit (seeing a doctor) becomes higher charges. The cost of higher charges is kicking down to health insurance. Who is paying that? Of course, you. Reducing and/or getting rid of malpractice insurance would in turn reduce the cost of health insurance for people.

      Prescription is another type of insurance which is different even though insurance company lump it up into "health insurance" type. The cost is high per what you said.

      So all in all, insurance companies are making money off you all. They charge doctors for high malpractice insurance cost. Then they charge you more to match up with the malpractice insurance and blame on the doctor cost (which is actually coming from their own charges). It is a double dipping.

    2. Re:Doctor's salaries aren't the big problem by Enigma2175 · · Score: 1

      Actually, I think it is a part of the cost as well. Doctors are supposed to pay for malpractice insurance which takes a big chunk out of the doctor's paid. In order to keep $80k~$150k/year, the real gross income for doctors is much higher than that (could be about double). As a results, a doctor visit (seeing a doctor) becomes higher charges.

      What? Malpractice insurance isn't nearly as expensive as you think it is. From http://truecostofhealthcare.net/malpractice/:

      That’s right, $4,926.63 for the whole year!

      if the cost of medical malpractice is breaking the back of healthcare in this Country, why is my bill so low? Is it because I’m such an outstanding doctor that my insurance provider long ago recognized that I would never be sued? Well, I’d like to think that were true but, no. Here’s how much other doctors in my community pay for medical malpractice insurance2015:

      The nephrologist who has an office one floor below me pays about $4,980 this year; $54 a year more than I pay and she runs a dialysis unit.

      A pulmonologist I work with pays $6,342 this year, an ophthalmologists less than $7,000, emergency room physicians: $11,000-$12,000 this year, anesthesiologists: $12,000-$14,000 this year, surgeons (including orthopedics) $20,000-$22,000 this year and Ob/Gyn about $34,000 (obstetrics always has the highest malpractice premiums).

      Yes, the insurance is expensive but well within the means of a decently-paid doctor

      --

      Enigma

    3. Re:Doctor's salaries aren't the big problem by Carewolf · · Score: 1

      And finally we got free routine check ups, the older you get the more frequent they get.

      They're not free. You just pay for them with tax dollars instead of insurance premiums. I agree that they are a good idea and I think the US does it in a retarded way but let's not pretend it's free just because you didn't get presented with a bill when you left the office.

      No, the tax burden IS LESS than if they didn't provide them, due to the saving they enable, so yes they are entirely free, they are in fact better than free since they pay for themselves and more.

    4. Re:Doctor's salaries aren't the big problem by Opportunist · · Score: 1

      Our drug costs took a pretty quick dive once pharma corporations noticed that there is ONE BIG insurance company in the country (along with a few private ones that make up about 1% of the market). If you have 99% of the market share and everyone pretty much HAS to be a member with you, your bargaining leverage is slightly improved. Mostly with medication that is available from different sources because the patent is gone. In other words, "we get it cheaper, Pfizer, because Roche over there is already begging us to sign with them".

      The only meds that still cost a pretty penny are those that are still within their patent time. And it's VERY difficult getting them prescribed because our government-insurance isn't too keen on paying for them. Of course, if you pay, pretty much anything goes that isn't on the red list (like, say, opiates and other Schedule-1 crap).

      If you get screwed by incompetent staff, there is of course recourse for this. It's pretty rare, but it happens. We're not really a sue-happy country to start with, and you simply don't sue people who're there to help you. It's probably a cultural thing. But yes, malpractice does happen. Usually something like this makes it into national news, though. And the outcome is usually that they have to fix what they broke. If all that "broke" is that your convalescence took longer, you basically get free hospital time. Which amounts to ... well, basically zero since it's part of your insurance anyway, so... The idea is that you get compensated for what went wrong. It's not an easy way to cash in big time.

      As for the check ups. yes, essentially I pay for them with my tax dollar. Or rather, the portion of my paycheck that goes off to the health insurance. But then again, a check up for 50 bucks that finds a cancer early that can be eliminated with a simple operation can "save me" paying for the same guy's chemo treatment that costs a few 1000 bucks a few years down the road. So no, it ain't free. Neither is the "free" flu shot that I may choose to get if I so wish. I pay for it, whether I get it or whether I don't (because someone else will). But it keeps the flu at bay, which in turn benefits me. Whether I get the shot or whether I don't.

      It's well invested money. That's not just me talking, that's the general consent around here. You can take away a lot from us, but touch our "free" health care and you got a civil war on your hands. That's why we shook our heads in disbelief when we heard about "Obamacare" and how people are actually opposed to it.

      I know the details now, and no, I would not want THAT kind of health care either. That's, sorry to say it, bullshit. Good idea, but the implementation is a catastrophe.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    5. Re:Doctor's salaries aren't the big problem by erp_consultant · · Score: 1

      "Doctor's income has very little to do with the skyrocketing cost of health care here in the US." - Spot on and you have outlined the real reasons quite nicely. In my view, Doctors should make more money not less. There are very few professions that require the amount of formal education and rigor that it requires to become a physician. Don't even get me started on how much athletes and entertainers make. It is obscene.

      I think the problem with the healthcare system is that nobody has any real skin in the game. All patients care about is how much their co-pay is for a given service. Doctors don't really care how much the lab charges or how much a given procedure costs as long as the insurance company will reimburse them for it. Insurance companies don't really care how much the doctor charges or the lab, as long as they can collect enough in premiums to cover it or pass it along to the patient in the form of a co-payment.

      Obamacare, despite addressing a few issues, does nothing to contain costs. It does nothing to address unnecessary or repetitive procedures. It does nothing to address frivolous malpractice lawsuits. It does nothing to address spiraling drug costs. Until those things are tackled costs will continue to rise.

  9. Undoing the EDS merger...interesting. by ErichTheRed · · Score: 3, Interesting

    This seems like a pure financial engineering transaction, but I wonder about the long term health of "IT Services" firms like CSC. I have worked both on the services and the "serviced" side doing various tasks over the years. The services firms cut every single corner they can to provide just enough service to avoid losing their contract; it's frustrating not being allowed to do something for a customer because it might make us less money but be more efficient. The companies hiring them use them as an excuse to wash their hands of anything IT related, dump staff, etc. without having to pay severance or take massive charges against earnings. And in the end, neither side ends up doing anything useful. I just wonder if companies have finally woken up to that fact and aren't just buying whatever the IT services sales guys tell them to anymore. I have seriously never heard of or experienced any good results of an IT outsourcing...it always puts the two companies at odds with each other.

    The only long term future I see for these kinds of companies is with government agencies. Agencies in most countries basically aren't allowed to spend agency money on in-house resources. It's always assumed that services companies provide more value for taxpayers' funds, but we know that's not the case. I think that now that companies can offload lots of their day to day IT to cloud providers like Amazon or Microsoft, there will be fewer places for the CSCs of the world to ply their "best practices" trade. It'll be the totally lazy companies that want nothing to do with IT, or agencies that have no choice but to outsource.

    I'm amused that HP is unwinding basically all of the mergers that they did to get so big. So many executive decisions like this are basically made by some 26 year old MBA from McKinsey or Booz Allen Hamilton, rather than the executives themselves. Granted, someone may have seen the writing on the wall for CSC/EDS/IBM/Accenture and others, but I doubt that. Like I said originally, it's probably financial engineering to squeeze out as much money as they can from HP before destroying it completely. IBM of late is famous for this.

    1. Re:Undoing the EDS merger...interesting. by jfdavis668 · · Score: 2

      Great, now another new group in charge of running the Navy/Marine Corp Internet (NMCI).

    2. Re:Undoing the EDS merger...interesting. by Anonymous Coward · · Score: 0

      Mergers, Acquisitions, and Divestitures are often just financial engineering moves, and they are almost always structured as a declining, indebted company conducting a leveraged purchase of a healthier one to transfer (aka steal) wealth from the shareholders of the healthy company to the preferred shareholders of the failing one. See also Kmart's acquisition of Sears.

      Then, the combined company will carve out the successful parts and spin off a new company (and new preferred stock) that has none of the original company's debts but all of the profitable capital, leaving behind a sinking ship for the common stockholders to deal with.

    3. Re:Undoing the EDS merger...interesting. by Temkin · · Score: 3, Informative


      The only long term future I see for these kinds of companies is with government agencies. Agencies in most countries basically aren't allowed to spend agency money on in-house resources. It's always assumed that services companies provide more value for taxpayers' funds, but we know that's not the case. I think that now that companies can offload lots of their day to day IT to cloud providers like Amazon or Microsoft, there will be fewer places for the CSCs of the world to ply their "best practices" trade. It'll be the totally lazy companies that want nothing to do with IT, or agencies that have no choice but to outsource.

      Don't be so quick to dismiss CSC. CSC bought Servicemesh, which provides them with one hell of a cross-cloud management platform. Agility Platform ties together AWS, Azure, Rackspace, etc... and a company's in-house vSphere clusters. It's kind of a DevOps monster... Setup the blueprint templates, and policy engine... You can literally have a team of three or four people managing 20+k instances... Add / Drop capacity as needed, and float to which cloud provider is cheapest at the moment.

    4. Re:Undoing the EDS merger...interesting. by BlackSupra · · Score: 2

      In November 2015, CSC split in two; CSC "private sector" (who is merging with HPE); and CSC "public sector" who merged with SRA to form CSRA.

      CSRA kept the FedRAMP approved 'Cloud' in the divorce.

    5. Re:Undoing the EDS merger...interesting. by Anonymous Coward · · Score: 0

      So in the long term, would we see a return of first Compaq, and then DEC?

    6. Re:Undoing the EDS merger...interesting. by Guy+Harris · · Score: 1

      So in the long term, would we see a return of first Compaq,

      There's now a PC and printer company named "HP"; I'm not sure what form of spinoff would restore Compaq.

      and then DEC?

      Alpha's dead, so they'd either have to bring that back to life, or spin off the OpenVMS-on-Itanium part to bring DEC back.

  10. IT Admin & HP Shop here - by nanodec · · Score: 1

    Since the spinoff, the desktops have gone to complete shit. New boxes with failing power supplies, bad mainboards, you name it. Their QC blows now, and their outsourced onsite techs are terrible. The server side has still been ok, but I'm worried they are going down the crapper too...

    1. Re:IT Admin & HP Shop here - by Anonymous Coward · · Score: 0

      I work for an MSP that tried switching from Dell to HP about 5 years ago. We went back to Dell within 3 months because HP was crap. But if they're bad enough that the HP-faithful are complaining, it must be even worse now.

    2. Re:IT Admin & HP Shop here - by Anonymous Coward · · Score: 0

      We're seeing the same thing here. We did a mass replacement using HP about 2.5 years ago, and now we're seeing multiple power supply failures cropping up. About 10% of our desktops thus far have been affected. Fortunately we have a 3 year warranty, but that's about to run out. We are sorely disappointed in the quality of hardware now.

  11. But of course, the company... by Anonymous Coward · · Score: 0

    will be "unable" to locate any qualified American workers to hire. (All the while the hallways, cube farms, and kitchen within the buildings reek of curry).

  12. over the last 9 years... by Anonymous Coward · · Score: 0

    EDS -> HP -> HPE -> ????

    Same account, same job, four different companies so far.
    That's some damn fine management!

  13. CSC? by The-Ixian · · Score: 4, Informative

    I used to work for a fortune 500 company who farmed out all server operations to CSC... I was on a core applications support team and would often need to work with CSC to spin up new servers or do restores or refreshes. I would say that 1 in 3 times the results of a request were actually what was expected. Most of the time something would go wrong and we would have to go into damage control mode.

    There was one time where we requested some new servers be brought up.... which they did... by reformatting production servers... I was always amazed at the novel ways in which CSC would screw things up.

    I got the impression that CSC probably had some competent people, they would have to in order to architect and maintain that level of server infrastructure, but we (the customer) never got to talk to those people. We dealt with the drones.... who were less than impressive.

    --
    My eyes reflect the stars and a smile lights up my face.
    1. Re:CSC? by Anonymous Coward · · Score: 0

      I was always amazed at the novel ways in which CSC would screw things up.

      That's called cutting-edge innovation...

  14. Consulting life cycle by tomhath · · Score: 4, Interesting

    So many companies go through the same sequence of events:

    1) Build a successful business selling hardware
    2) Customers ask for help with infrastructure and applications
    3) Build a successful consulting business supporting hardware sales
    4) Brilliant MBA notices consulting has a much higher profit margin than hardware
    5) Company outsources hardware business and focuses on consulting
    6) Pipeline of customers needing consulting dries up because they no longer buy hardware from company
    7) CEO panics, has massive layoffs
    8) New CEO looks around and sees that company no longer has a product to sell

  15. Less cost does not equal free by sjbe · · Score: 1

    No, the tax burden IS LESS than if they didn't provide them, due to the saving they enable, so yes they are entirely free, they are in fact better than free since they pay for themselves and more.

    Less does not equal free. By taking advantage of preventative medicine the average cost to a patient is less. Health care is NEVER free. The fact that you pay with tax dollars instead of private insurance doesn't change the fact that you still are paying some amount for the visit.

    1. Re:Less cost does not equal free by Carewolf · · Score: 1

      No, the tax burden IS LESS than if they didn't provide them, due to the saving they enable, so yes they are entirely free, they are in fact better than free since they pay for themselves and more.

      Less does not equal free. By taking advantage of preventative medicine the average cost to a patient is less. Health care is NEVER free. The fact that you pay with tax dollars instead of private insurance doesn't change the fact that you still are paying some amount for the visit.

      No, but we are talking about a specific part they provide that results in you having to pay less. The part they provide that causes you to pay less, doesn't cost you anything extra, it in fact cost you less.

  16. Sounds like HP is in trouble by fustakrakich · · Score: 1

    Where's Carly when you need her?

    --
    “He’s not deformed, he’s just drunk!”
    1. Re:Sounds like HP is in trouble by sconeu · · Score: 1

      Where's Carly? She's busy laying off Ted Cruz's campaign staff.

      --
      General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
  17. Insurance myths by sjbe · · Score: 2

    Doctors are supposed to pay for malpractice insurance which takes a big chunk out of the doctor's paid. In order to keep $80k~$150k/year, the real gross income for doctors is much higher than that (could be about double).

    Not as a general proposition. The amount you pay for malpractice insurance varies by specialty and by location but it very rarely doubles the cost of a doctor. Something between $10K-30K/year is fairly typical. Larger practices and hospitals can typically get better rates than smaller ones. Some specialties like OBGYN in certain locations can get socked with outrageous malpractice insurance fees due to the tort laws in that area. Most of the doctors I personally know about pay somewhere between $10K-15K per year. Substantial but not back breaking.

    Specialty doctors can easily earn $300-600K/year. Good money and it sounds like a lot but as a percentage of health care costs is actually quite minor. Lst time I looked at the statistics, doctors salaries accounted for single digit percentages of the overall cost.

    As a results, a doctor visit (seeing a doctor) becomes higher charges.

    Not necessarily. In many cases doctors cannot charge whatever they want. If the patient is a medicare patient, is indigent, etc the doctor or hospital may be limited in their ability to pass on increased costs. The notion that doctors can just pass on every increase isn't really true. Typically the profit a doctor's office makes depends heavily on their ability to negotiate with and work around insurance companies. Most insurance companies use medicare to determine rates they will pay for specific services.

    So all in all, insurance companies are making money off you all.

    Of course they are. There would be no reason for a private insurance company to exist if they weren't making a profit. The only way to avoid that is to have a government run health care system because the government is the only entity that entirely lacks a profit motive. (yes this even includes not-for-profit hospitals and the like) But since the idea a government run health care system gives republicans hives (despite the fact that we already de-facto have one with medicare) we have this Frankenstein monster of a system instead that only insurance companies could love. Idiotic but it's not going to change any time soon.

  18. Itanic by Anonymous Coward · · Score: 0

    At the time in question, everybody thought that CISC was passe, that RISC was the future, and HP wanted to do a one-upsmanship game vs DEC and IBM. Alpha and Power were already ahead of everything else, so HP wanted to see if a VLIW CPU would give them a quantum leap over the competition. The reason they picked Intel as their partner was both Intel's IP in x86 that would enable it to run x86 binaries, as well as Intel's fab process, since HP was already using it to manufacture PA-RISC

    Problem with VLIW was that each new CPU was guaranteed to break backwards compatibility, therefore forcing ISVs to recompile every time. Great for performance, maybe, but horrendous as a market acceptance strategy. Also, getting rid of a lot of the circuitry that was gonna be replaced by the compiler just saved 10% in real estate, while blowing up the complexity of the compiler. Making it untenable.

    What finally killed both RISC and EPIC was not x86 itself, but the multi core architecture that Intel packed into its way advanced processes. Once Microsoft united the Windows code bases in XP, making SMP support standard on all Windows, Intel could toss in more cores to boost performance, and totally negate the performance advantages of the PA-RISC, Alpha and everyone else. What's more - native Wintel software ran as well as ever - all that needed to be done was more multi-threading. Once RISC lost the one advantage it had over the x86 - performance, it was game over

    1. Re:Itanic by Guy+Harris · · Score: 1

      Problem with VLIW was that each new CPU was guaranteed to break backwards compatibility,

      Only if you do it in a way that either 1) changes the instruction encoding from CPU to CPU or 2) doesn't have rules for code that's guaranteed to work on all future processors. The IA-64 documentation gives the instruction encoding for all processors, and does have rules of that sort (see, for example, section 3.4 "Instruction Sequencing Considerations"), so they didn't do it in one of those ways, so each CPU is guaranteed not to break backwards compatibility for valid code (which means that the code doesn't, for example, have any of the dependencies that are "not allowed" by section 3.4).

      therefore forcing ISVs to recompile every time. Great for performance, maybe, but horrendous as a market acceptance strategy.

      Except that you don't have to recompile code to have it run on a future Itanium processor, as long as the compiler wasn't "too clever", generating code with "not allowed" dependencies because it "knew" that the processor would execute that code in the way it intended.

      You might get performance improvements by recompiling for a new processor, but that's hardly unique to Itanium.

      What finally killed both RISC and EPIC was not x86 itself, but the multi core architecture that Intel packed into its way advanced processes. Once Microsoft united the Windows code bases in XP, making SMP support standard on all Windows, Intel could toss in more cores to boost performance, and totally negate the performance advantages of the PA-RISC, Alpha and everyone else.

      I had the impression that, at least for the desktop and small server market, they lost a lot of that performance advantage well before Intel went multi-core.

    2. Re:Itanic by Anonymous Coward · · Score: 0

      Problem with VLIW was that each new CPU was guaranteed to break backwards compatibility,

      Only if you do it in a way that either 1) changes the instruction encoding from CPU to CPU or 2) doesn't have rules for code that's guaranteed to work on all future processors. The IA-64 documentation gives the instruction encoding for all processors, and does have rules of that sort (see, for example, section 3.4 "Instruction Sequencing Considerations"), so they didn't do it in one of those ways, so each CPU is guaranteed not to break backwards compatibility for valid code (which means that the code doesn't, for example, have any of the dependencies that are "not allowed" by section 3.4).

      That actually assumes that Intel can't add new instructions to future versions of the Itanium that may not have been anticipated during the work on Merced. I wasn't assuming that opcodes would change, just that new ones would be introduced that might improve, say, loop unrolling, and that to make use of that, the VLIW compiler would have to kick in. Like if the number of registers in a subsequent generation CPUs is increased, and register renaming is in the hands of the compiler, recompilation would automatically be required to get any performance enhancement, or worse, prevent a performance degradation.

      Of course, today's Itanium - the Itanium II or III, I've lost track - is more a RISC CPU than even an EPIC - things like register renaming, once the job of the VLIW compiler, is now there on silicon itself, just as it was with the RISC CPUs

      therefore forcing ISVs to recompile every time. Great for performance, maybe, but horrendous as a market acceptance strategy.

      Except that you don't have to recompile code to have it run on a future Itanium processor, as long as the compiler wasn't "too clever", generating code with "not allowed" dependencies because it "knew" that the processor would execute that code in the way it intended.

      You might get performance improvements by recompiling for a new processor, but that's hardly unique to Itanium.

      Yeah, I wasn't thinking so much about performance improvements, as much as recompiling to make use of more pipelines, or so on. Of course, one could squeeze all the parallelism out of the code right at the get-go by making it independent of the number of functional units of the CPU, and make that question moot.

      What finally killed both RISC and EPIC was not x86 itself, but the multi core architecture that Intel packed into its way advanced processes. Once Microsoft united the Windows code bases in XP, making SMP support standard on all Windows, Intel could toss in more cores to boost performance, and totally negate the performance advantages of the PA-RISC, Alpha and everyone else.

      I had the impression that, at least for the desktop and small server market, they lost a lot of that performance advantage well before Intel went multi-core.

      That might have been the case with the Pentium 4, but then it had some serious issues, such as power consumption, that hampered its market acceptance.

    3. Re:Itanic by Guy+Harris · · Score: 1

      Problem with VLIW was that each new CPU was guaranteed to break backwards compatibility,

      Only if you do it in a way that either 1) changes the instruction encoding from CPU to CPU or 2) doesn't have rules for code that's guaranteed to work on all future processors. The IA-64 documentation gives the instruction encoding for all processors, and does have rules of that sort (see, for example, section 3.4 "Instruction Sequencing Considerations"), so they didn't do it in one of those ways, so each CPU is guaranteed not to break backwards compatibility for valid code (which means that the code doesn't, for example, have any of the dependencies that are "not allowed" by section 3.4).

      That actually assumes that Intel can't add new instructions to future versions of the Itanium that may not have been anticipated during the work on Merced. I wasn't assuming that opcodes would change, just that new ones would be introduced that might improve, say, loop unrolling, and that to make use of that, the VLIW compiler would have to kick in. Like if the number of registers in a subsequent generation CPUs is increased, and register renaming is in the hands of the compiler, recompilation would automatically be required to get any performance enhancement, or worse, prevent a performance degradation.

      That's a bit more than what happens with every other type of CPU, but not all that much more - new instructions are added, and some instruction sets even acquired more registers (z/Architecture added some instructions to manipulate the lower half and upper half of registers, so that a single 64-bit GPR can act as 2 32-bit GPRs, for example).

      But that doesn't break binary compatibility, it just requires recompilation for more performance. If not recompiling causes a significant performance hit, that's a severe problem, though.

      (And the recompilation would happen transparently, other than some first-time performance hit, on a {System/38,AS/400,IBM i}-style system, where compilers generate a higher-level code that gets translated to executable machine code when the code is first executed, allowing a re-translation the first time the code is executed on a new machine. That's also kinda sorta what Transmeta did. But most systems aren't like that, for better or worse.)

      What finally killed both RISC and EPIC was not x86 itself, but the multi core architecture that Intel packed into its way advanced processes. Once Microsoft united the Windows code bases in XP, making SMP support standard on all Windows, Intel could toss in more cores to boost performance, and totally negate the performance advantages of the PA-RISC, Alpha and everyone else.

      I had the impression that, at least for the desktop and small server market, they lost a lot of that performance advantage well before Intel went multi-core.

      That might have been the case with the Pentium 4, but then it had some serious issues, such as power consumption, that hampered its market acceptance.

      I seem to remember seeing claims (in Microprocessor Report?) that x86 was giving the faster RISCs a run for their money in the P6 days, even if it wasn't quite doing completely as well or better.

  19. And the Meg meltdown continues.... by erp_consultant · · Score: 2

    Meg Wittman has to go down as one of the worst CEO's in history. HP, the once proud company, is being reduced to a steaming pile. So now EDS is being spun off, which HP massively overpaid for in the first place. This is after Meg triumphantly declared that HP was going to be a huge player in the "services" market.

    Same mistake that IBM and DELL made. Another hardware vendor tries to become a services player and falls flat on its face.

    Pretty soon HP will be reduced to a company with some patents and selling printers. Meanwhile Meg feathers her nest in anticipation of the golden parachute jump. But before that happens thousands more will lose their jobs and the company continues to be gutted.

    Bill and David must be rolling in their graves.

    1. Re:And the Meg meltdown continues.... by Guy+Harris · · Score: 1

      Pretty soon HP will be reduced to a company with some patents and selling printers.

      So what will happen to HPE (which sells no printers)?

    2. Re:And the Meg meltdown continues.... by erp_consultant · · Score: 1

      HPE becomes the steaming pile I referred to above :-)