Slashdot Mirror


Oracle Staff Report Big Layoffs Across Solaris, SPARC Teams (theregister.co.uk)

Simon Sharwood, reporting for the Register: Soon-to-be-former Oracle staff report that the company made hundreds of layoffs last Friday, as predicted by El Reg, with workers on teams covering the Solaris operating system, SPARC silicon, tape libraries and storage products shown the door. Oracle's media relations agency told The Register: "We decline comment." However, Big Red's staffers are having their say online, in tweets such as the one below. "For real. Oracle RIF'd most of Solaris (and others) today," an employee said. A "RIF" is a "reduction in force", Oracle-speak for making people redundant (IBM's equivalent is an "RA", or "resource action"). Tech industry observer Simon Phipps claims "~all" Solaris staff were laid off. "For those unaware, Oracle laid off ~ all Solaris tech staff yesterday in a classic silent EOL of the product."

43 of 239 comments (clear)

  1. Rule #1 by UndyingShadow · · Score: 5, Funny

    "Don't make the mistake of anthropomorphizing Larry Ellison." -Bryan Cantrill

    1. Re:Rule #1 by ShanghaiBill · · Score: 4, Insightful

      "Don't make the mistake of anthropomorphizing Larry Ellison." -Bryan Cantrill

      Larry can be very cold hearted, but I can't fault him for this. Sparc/Solaris was a great choice in the 1980s, a reasonable choice in the 1990s, and a bad choice ever since. There can't be much more than a handful of legacy customers left. I am surprised that it took this long to finally die.

    2. Re:Rule #1 by Anonymous Coward · · Score: 3, Informative

      After Solaris was open sourced, there seemed to be a time when the use of Solaris could potentially expand greatly. Once Ellison closed the code again, there was no hope at all. Ellison should be blamed completely for this.

    3. Re:Rule #1 by Tailhook · · Score: 2

      This. Solaris could have gone far, but for the people that owned it.

      --
      Maw! Fire up the karma burner!
    4. Re:Rule #1 by UltraZelda64 · · Score: 2

      Then why the fuck did he buy it? Maybe his company could have done less of a dick move by just selling the Sun properties that they were not interested in, like Solaris, so they could be given an actual, proper chance. Fuck Oracle.

    5. Re:Rule #1 by ShanghaiBill · · Score: 5, Insightful

      Then why the fuck did he buy it?

      To kill MySql, which was a long term threat to Oracle's core business.

      Maybe his company could have done less of a dick move

      Without dick moves, Oracle wouldn't be Oracle, and Larry certainly wouldn't be Larry. Being a dick is his core competency.

    6. Re:Rule #1 by thesupraman · · Score: 5, Insightful

      MySQL? A Threat a real database? Umm. No.

      PostgreSQL perhaps, but not MySQL.

      Just because its popular with 'toy database' applications (where the db is really just slightly glorified read only storage) doesnt mean it is a threat or oracle - different horses for very different courses.

    7. Re:Rule #1 by Anonymous Coward · · Score: 5, Insightful

      MySQL? A Threat a real database? Umm. No.

      A threat to real database needs, no. But a threat to real database sales, yes, at least in the eyes of people who see any alternative as a lost sale. Sure, MySQL is mostly a replacement for a structured file, but that's still one replacement for a structured file that Oracle wasn't paid for.

      It's not much different than the kind of mind set that would claim that a 10 year old a yearly allowance of $1200 copying a bunch of MP3s is a loss to the music industry of $12 million.

    8. Re:Rule #1 by TheRaven64 · · Score: 5, Insightful

      PostgreSQL is less of a threat to Oracle than MySQL. If you start building a system with PostgreSQL, you have a reliable database with a decent query optimiser and you'll end up putting a lot of logic into the database. Once you grow to a big enough size that you might be able to afford Oracle, they send along salesmen and convince your least competent C?O that your data would be a lot safer if you migrate to a proper database and they provide migration tools to do this. They can probably demonstrate some speedups from their custom filesystem and query optimiser. On the other hand, if you start with MySQL, you end up using the database as little more than a key-value store and put most of the logic outside of the database. It's much harder to demo a place where Oracle is an improvement because your bottleneck is the application logic that's doing a load of redundant database queries, not the database itself.

      --
      I am TheRaven on Soylent News
    9. Re:Rule #1 by Anonymous Coward · · Score: 3, Interesting

      Not sure if you've noticed, but Oracle have spent the last 2 years pulling volume discounts from under some pretty big companies. My entire multinational has set a deadline to remove all use of Oracle, and I know we're not the only ones migrating from Oracle to Postgres

    10. Re:Rule #1 by TheRaven64 · · Score: 5, Interesting

      I didn't, but I'm not surprised. Last time I spoke to someone at Oracle, they said that the revenue from the DB was up, but they had very few new customers. Their real problem is Moore's law and friends. In the early '90s, payroll for a moderately large company took a serious database on high-end hardware to manage, with several hours of compute time to complete the payroll calculations each week. Now, that same company is maybe 10 times the size, but you can buy a computer more than 100 times better in terms of RAM, storage capacity, storage speed, and processor speed, for a few hundred dollars. On a modern machine, you don't need carefully optimised queries and carefully designed on-disk data structures - you can probably fit the whole thing in RAM and run the computations in Lua and still get the whole thing done in a second or two. At one end of the market, most customers can now run their systems with cheap commodity hardware and software. At the other end of the market, companies like Facebook and Google have more data than Oracle can easily handle and couldn't afford Oracle license fees even if there was a viable Oracle product for them to buy. The middle is gradually shrinking.

      --
      I am TheRaven on Soylent News
    11. Re:Rule #1 by azrael29a · · Score: 2

      Then why the fuck did he buy it? Maybe his company could have done less of a dick move by just selling the Sun properties that they were not interested in, like Solaris, so they could be given an actual, proper chance. Fuck Oracle.

      To sue Google for Java patent infringement in Android. But that plan has failed.

    12. Re: Rule #1 by hord · · Score: 2

      Lots of shared, hyper-threaded cores. The performance on them is abysmal. They started to bank on marketing the number of cores rather than making cores that perform so you get CPUs with 128 "cores" based on 4 CPU dies that take 10x as long to gzip/gunzip and other simple tasks.

    13. Re:Rule #1 by hord · · Score: 2

      You probably still have large SPARC sales due to legacy applications requiring it as part of the stack. This is changing, but I used an ERP that only gave requirements for Sun SPARC/Solaris with Oracle databases and this drives purchasing decisions. We tried for years to convince them to switch to Linux with all kinds of performance metrics. You lose your support contract when doing so, however.

      Now that stuff is moving into the cloud, SPARC has no real reason to exist. It was already pretty crippled compared to x86 for general purpose stuff.

    14. Re:Rule #1 by MouseR · · Score: 4, Informative

      He bought it mainly because of Java. Oracle has a huge investment in Java and there was no way in hell he could afford to let it die or, worse yet, let it go to IBM.

      Solaris was a nice bonus because Oracle also had lots of investment in that hardware/software platform for it's own servers. From where I sit, I saw a gradual move to Oracle Linux over the years but I can not say wether that is responsible for dropping Solaris/Spark.

      There was a time I had a Solaris virtual box. Mostly unused but was useful when I needed to install a particular server instance for the applications I was doing at the time. Nowadays, I have an Oracle Linux virtual machine on which runs one of our development tools, for our App development. Other members in the team have their own Oracle Linux virtual machine to host dev or qa instances of the server for our App development use.

      Haven't seen an OpenSolaris box in years, but I know one of our training center in MDC has (had?) a few boxes on there. Not sure they are still there. Been ages since I walked in that office.

    15. Re:Rule #1 by MouseR · · Score: 2

      Forgot to mention: those are my thoughts and impression. Not an official Oracle statement. I claim not to know the inner workings of management decisions.

    16. Re:Rule #1 by rholtzjr · · Score: 2

      PostgreSQL is less of a threat to Oracle than MySQL. If you start building a system with PostgreSQL, you have a reliable database with a decent query optimiser and you'll end up putting a lot of logic into the database. Once you grow to a big enough size that you might be able to afford Oracle, they send along salesmen and convince your least competent C?O that your data would be a lot safer if you migrate to a proper database and they provide migration tools to do this.

      Here is the big question. WHY would any SANE programmer put business logic into the model layer? That would tightly couple your database engine to the other layers of the application. Once a more viable solution is available, it may have already become too cost prohibitive to migrate to the next technology. We see this now with a lot of mainframe centered companies. Don't get me wrong, most mainframe based companies have a very highly tuned and efficient solution, but as technology changes, where does that leave them?

    17. Re:Rule #1 by Anonymous Coward · · Score: 5, Informative

      WHY would any SANE programmer put business logic into the model layer?

      To uniformly enforce rules when accommodating multiple applications accessing the same data.

      Another reason is that the database will usually be the longest living part of the software architecture.

      In terms of things being tightly coupled, defining a set of stored procedures for data access hardly makes the application tightly coupled. Using raw SQL tightly couples your application to the schema. If the schema needs to change for database reasons the stored procedure layer could prevent you from having to modify the applications.

      Yes, there are other ways to accomplish the same thing but it's not an insane decision.

    18. Re:Rule #1 by Penguinisto · · Score: 2

      Same story here, really. At a previous employer, I fed and cared for a metric ton of ldoms* running on Sparc T-3 iron, as well as other (slightly older) Sparc pizza boxes running a ton of zones. The big reason they existed was to test the product on the Solaris/Sparc platform under various incarnations (from Solaris 7 to latest/greatest, which was IIRC 11.x at the time)... and that was about it.

      Anything they actually cared about (business-wise) sat on Linux and/or Windows boxen.

      * for those who were unaware, apparently Oracle decided they wanted to compete with VMWare at one point in time, so they created something called Logical Domains (ldoms). Think of everything you ever thought to be frustrating about vSphere, make it 10x worse (especially virtual networking), then build it with a CLI-only interface. Let's just say that IBM's version of it ( lpars ) were 100x more enjoyable to build/maintain.

      --
      Quo usque tandem abutere, Nimbus, patientia nostra?
    19. Re: Rule #1 by hord · · Score: 2

      T-series SPARC architecture is only good for one thing: serving static web pages. You will get horrid performance for anything else. I know because we ran all kinds of stuff on them including web servers, databases (Oracle), and infrastructure. You are getting a slow, 4-CPU machine that "hyperthreads" to 128 cores with little to no cache. No, it is a horrible platform that needs to sink to the bottom of the digital ocean regardless of "high volume" and "server" labels. It was designed for transactional processing and fails. Don't take my word for it... ask the entire IT industry what they think.

    20. Re:Rule #1 by hey! · · Score: 2

      I suspect the one thing which Oracle wanted from Sun was control of Java. Not necessarily for nefarious purposes (although a more ruthless company I have seldom encountered); it was just intolerable given the commitment they'd made to Java to have it in anyone else's hands.

      MySQL was a great project, but there is no way it threatens Oracle's database customer base.

      Oracle has an aggressive lock-in strategy for its database customers; to that end not only does it offer myriad proprietary ways of doing things, it offers some genuinely impressive technical capabilities; it also works hard to co-opt DBAs by having them acquire a number of Oracle-specific skills. This makes it both difficult and unattractive to move away from Oracle.

      One thing Oracle got into early was copy-on-write technology. This gave them far better transaction isolation than their competitors. It's even possible to create long-running forks of a databases, and then later merge those forks -- just like forking and merging a source code tree.

      Sure, as a backing store for your web site, pretty much anything will do the job. Oracle is overkill -- in fact relational databases in general are overkill.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  2. Re:All Solaris Staff? by theweatherelectric · · Score: 5, Informative

    Can the codebase be recovered?

    Doesn't need to be. Illumos is the open fork of (not so) OpenSolaris.

  3. VirtualBox by that+this+is+not+und · · Score: 4, Interesting

    Has there been any word about VirtualBox? That is pretty much the only former-Sun softwarevI use on a regular basis. Since the Oracle purchase of Sun I have wondered why Oracle was keeping it alive.

    1. Re:VirtualBox by Tailhook · · Score: 5, Interesting

      VirtualBox is difficult to explain. Oracle has never seriously tried to monetize it. They've never inflicted a Java installer on VirtualBox users. Most of it is still Open Source and they haven't driven off the entire user base to some fork. They haven't done any of the damage this sociopath or a corporation does to everything else they acquire.

      I pointed this out to a moderately clever person once. He suggested that perhaps Oracle forgot about it. Maybe there is a small team of dedicated developers quietly enhancing their work, filling out their TPS reports and successfully avoiding notice.

      --
      Maw! Fire up the karma burner!
    2. Re:VirtualBox by Bing+Tsher+E · · Score: 2

      I used wget to grab the whole set of the current version installers. You can never be too safe.

    3. Re:VirtualBox by whoever57 · · Score: 2

      So you are saying that the VirtualBox team are the equivalent of Milton Waddams?

      Just hope that Oracle doesn't bring in "the Bobs".

      --
      The real "Libtards" are the Libertarians!
    4. Re:VirtualBox by TheRaven64 · · Score: 2

      Sun's goal for VirtualBox as to make it a gateway drug for their Xen + Solaris + proprietary management tools stack. The idea was that VirtualBox would make it easy to create small numbers of VMs for managing infrastructure, but when you got to a larger scale you'd want to buy the bigger system. Now that Oracle has started dabbling in the cloud provider space, they may start caring again for the same reason.

      --
      I am TheRaven on Soylent News
  4. Re:All Solaris Staff? by Anonymous Coward · · Score: 2, Informative

    There's still a lot of valuable code in the closed version of Solaris. ZFS enhancements come to mind.

  5. Re:All Solaris Staff? by theweatherelectric · · Score: 5, Informative

    ZFS enhancements come to mind.

    After the split with OpenSolaris, ZFS development moved to the Illumos project and OpenZFS grew out of it.

  6. More information the Layoff by plopez · · Score: 3, Informative

    In case anyone wants more insider info. https://www.thelayoff.com/orac...

    --
    putting the 'B' in LGBTQ+
  7. A problem of Sun's making. by upuv · · Score: 5, Insightful

    Lets face it Sun made mistakes. These mistakes made it ripe for take over and plundering by Oracle.

    The biggest mistake was Linux. When Red Hat launched no one took it seriously. Red Hat legitimised Linux in the eyes of industry. Companies faced with massive expansions of internet equipment simply could not afford the iron from SUN / HP / IBM. These small start ups went to Linux. One such startup was Google. All of a sudden massive new companies emerged on a platform that was not enterprise iron. Overnight Dell become a major player in the server room.

    What did Sun do about this? Nothing. Even when faced with new unit sales that were almost zero compared to just a few years before sun still did nothing. Sun released Solaris for x86/64. But completely forgot to get 3rdparty shops and it's on internal application development teams to port to it. They only thing that ran on the x86/64 Solaris was open source software. Stuff that was already running on much cheaper x86/64 gear. Sun limped on for a few years making the occasional uplift sale for existing gear in the field.

    Then Oracle pounced. Suns mistakes led to this point. They sold for far less than they were worth. Why? The market lost all faith in Sun's ability to generate a cash flow. Thus the negative impact on asset value.

    Oracle saw something it liked very much. Java. Oracle instantly went on a predatory path of trying to extract money out of Java. We all know how well that went. Oracle just recently announced that they are looking to open source the Java EE specification. This predatory cash grab caused some other interesting market changes. The explosion of new languages resulted and they got market share. Ruby on rails in my opinion would have never had as much success as it once did with out Oracles legal threats over java usage.

    Oracle also needed to save it's DB division. At that point Oracle DB pretty much was only ever deployed on pricey Sun gear. Also Sun owned the control of MySQL. Which was growing at an astonishing speed. This threat needed to be squashed at all costs. In my mind these were the real reasons for Oracles purchase of Sun.

    There were some other assets that Oracle was looking to sell off. But in the end Oracles taint reduced their value to zero. OpenOffice comes to mind.

    I still remember the day when Oracle purchased Sun. There was an audible groan in the office. Execs around the world were scrambling to find alternatives to many products. Sun certified engineers instantly saw there pricey certificates devalue in an instant.

    The only reasons Oracle has kept Solaris and SPARC alive for so long are:
    1. Uplift purchases still come in. But not many. These can be counted in 1000's world wide. Basically nothing.
    2. The platform became part of the Exadata/Exalogic platform. ( An an holy creation in my mind. )

    1. Re:A problem of Sun's making. by whoever57 · · Score: 5, Insightful

      The biggest mistake was Linux. When Red Hat launched no one took it seriously. Red Hat legitimised Linux in the eyes of industry.

      I disagree. The root problem was that single-thread performance of Sparc lagged Intel x86 around the time the PIII came out. Linux made adoption of x86 possible for many applications, but few of them would have moved to x86 without the big performance and cost benefits of adopting it.

      Sun tried to compensate with more cores, but that only made Sparc more expensive and many applications were not written to take advantage of multi-core hardware.

      --
      The real "Libtards" are the Libertarians!
    2. Re:A problem of Sun's making. by bungo · · Score: 5, Informative

      This is very true.

      This wasn't just Sun's problem, IBM had similar issues with the AIX Power servers. The price/performance of Java on x86 was far better than anything that Sun or IBM could offer. They were still stuck with the mindset of selling expensive mid-range type systems. They could offer better scaling, with more cores in a single box, but when you could have a distributed application, with many small servers, the old vendors couldn't compete.

      Once Redhat went public and management were able to convinced that Linux was a real alternative, instead of buying 4 AIX servers of $75k each, I was able to get 12 Linux x86 servers for $4k each (rack mounted, so a little bit expensive). The price for Sun SPARC servers were cheaper than the AIX servers, but still way more expensive than x86 servers.

      The Linux servers were multiple times faster for the Java applications that they had to run, for just over 1/2 the price of a single AIX box.

      --
      "The best part? I became an ordained minister while not wearing pants." -- CleverNickName
    3. Re:A problem of Sun's making. by _merlin · · Score: 4, Insightful

      I see it differently. MS killed desktop UNIX by being good enough. Desktop UNIX was better, but Windows NT 4 on commodity hardware was (perhaps just barely) good enough, and far cheaper. This impacted all the UNIX vendors, as it killed off a significant revenue stream.

      Sun was losing the performance battle badly with SPARC. This was painfully obvious with the Sun Blade 2500 tower. The CPUs were no faster than the Blade 2000, and it had a quarter of the RAM bandwidth as a cost-saving measure (they reduced memory from 256 bits wide to 64 bits wide so you could install RAM DIMMs individually rather than in groups of four). They were still trying to charge premium prices for SPARC, but x86 and POWER were walking all over it in performance. They managed to score some wins on highly-parallel workloads with the UltraSPARC T series (Niagara), but it was always specialised and Suns AMD64 boxes performed better on most workloads.

      Sun was spread far too thin on the ground and faced with falling revenues. They tried open source as a strategy, but open sourcing something provides no value on its own. They couldn't maintain/enhance their OS (Solaris), compilers (SunPro), Java, and everything else. They were floundering, occasionally coming out with an interesting product, but no consistency.

      Ruby on Rails was framework-of-the-month already by 2006, years before the Oracle purchase. The explosion of programming languages would've happened anyway, it's a result of all the people who studied computer science after the first dotcom bubble. J2EE had already been co-opted by Apache and Red Hat, and let's face it, hardly anyone even uses J2EE. Most of the time Spring is a lighter-weight substitute, you only really want J2EE if you need distributed transactional consistency.

      Sun were lucky to sell out when they did. They really didn't have a viable plan, and taking the money and running probably was the best thing for the shareholders. They'd already open-sourced most of the stuff that had any value, so it wasn't going to matter too much how Oracle mismanaged it. Oracle were stupid to buy Sun, as it was already pretty obvious there wasn't really much worth buying.

      Yeah, I miss Sun, but the Sun I miss had already faded long before the Oracle purchase. I just didn't want to believe it and willingly went into denial.

  8. Only real question is by oldgraybeard · · Score: 4, Insightful

    Why did they wait so long. We all knew this was going to happen. Oracle wanted the intellectual property not the actual projects or the people.

    1. Re:Only real question is by upuv · · Score: 3, Interesting

      The big reason they waited so long was they wanted/needed to migrate existing customers onto exa or cloud platforms. If they just killed it quickly they would effectively be loosing those customers, probably forever.

      Also OracleDB was one of the only reasons to buy SPARC anymore. Database shops hate platform change in general. No one ever got fired for buying SPARC for the DB environment.

  9. Re:sorry, not sorry by upuv · · Score: 3, Interesting

    In the early days SPARC was one of the only platforms that you could run x64 Java. Linux x64 was considered unstable and untested at the time.

    So we bought massive SPARC boxes to host java apps. A lot of java apps at once. And yes the performance was garbage. A dedicated engineer at least just constantly on the lookout for performance issues.

    I still remember one team going OK we built those new linux boxes for you. Only to find out they built them with 32bit linux. They simply would not build them x64. I had to remind them that the whole point of the project was to evaluate java on x64 intel. When they finally did rebuild them properly the initial performance tests were amazing. That company never looked back after that point.

  10. Re:All Solaris Staff? by Z00L00K · · Score: 2, Insightful

    As I see it Solaris is pretty stagnant since at least a decade. Most new development of *NIX environment has been under Linux and different BSD variants.

    There may be certain applications that are Solaris specific, and it's probably a few of those that could be of interest to port to other environments if they aren't ported already.

    But the days when Solaris was a leading significant factor in the *NIX world ended some 20 years ago.

    --
    If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
  11. Re:All Solaris Staff? by avgapon · · Score: 2, Informative

    Proprietary ZFS also grew a number of features and enhancements. For example, OpenZFS is just growing the encryption support while the proprietary ZFS has had it for several years.

  12. Re:sorry, not sorry by Anonymous Coward · · Score: 2, Interesting

    Having spent years struggling with Solaris instability for java (see madness linking required kernel patches to JVM upgrades) I honestly cant think of a single aspect of it that I miss.

    Regarding SPARC, I remember the JavaOne conference where Intel engineers sat side-by-side with Sun JVM engineers to describe their partnership to delivery the best Java performance ever. I also remember switching a specific Java application from SPARC to Intel with no other changes and seeing at 23x performance boost while lowering hardware costs. Not missing a single thing about SPARC either.

    Perhaps my experience was a fluke. Are there many people out there productive and stable using SPARC and Solaris? I had always assumed the entire market segment was maintaining legacy systems in situations where there was no money to move forward with modern choices.

    Solaris and instability in the same post?

    YOU SIMPLY DON'T KNOW WHAT YOU'RE TALKING ABOUT

    Period.

    You don't.

    Call me when Linux actually implements AUTH_SYS properly instead of randomly grabbing the first 16 groups it finds. Yeah, that asinine, random, now-you-can-access-your-files-now-you-can't works really well in a large enterprise environment with tens of thousands of users.

    Call me when Linux fixes pwrite() - read the Linux man page, that bug has been in there for years and prevents access to a file that allows both atomic appends or atomically writes to any location.

    Call me when GNU stops trying to get POSIX to remove fork() from the list of functions required to be async-signal-safe - the glibc fork() implementation is broken and not async-signal-safe because the glibc developers STUPIDLY used pthread_atfork() handlers in glibc, of all fucking places. So instead of fixing glibc, GNU is pushing for lower standards.

  13. Re: So who is Oracle going to buy now? by that+this+is+not+und · · Score: 2

    If Oracle buys RedHat so it can die, can we make sure to securely rope systemd to the body before it's sunk in the bay? Also the body of that festering millineal who champions it, of course. And Gnome3 wants to ride along.

  14. System V R4 is dying by Stonent1 · · Score: 2

    They should have stuck with BSD, it's dying but less quickly. :)

  15. Re: And the people? The REAL lesson here. by Uncle+Warthog · · Score: 2

    Anyone who interviews regularly knows that 75% of developers can't count to 11

    Huh? That's not hard:

      0
      1
    10
    11