From: tfb@tfeb.org (Tim Bradshaw)
Subject: [TUHS] Oracle euthanizes Solaris 12, expunging it from roadmap
Date: Thu, 19 Jan 2017 16:39:45 +0000 [thread overview]
Message-ID: <B894AC3E-B97D-46F3-BBDC-EA72F39F6E49@tfeb.org> (raw)
In-Reply-To: <a7d2dca4-3fbe-839d-1a00-4772943ab6e8@kilonet.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3020 bytes --]
Well, they are probably reacting to what their customers want which, in my experience working at a fairly typical customer up to a couple of years ago, is indeed Linux. That's kind of sad, but Linux, much though I'd like to hate it, is unfortunately both a significantly more pleasant experience as a user & administrator, and a lot easier to hire people for. It's 20 years too late for Solaris to have a future.
> On 19 Jan 2017, at 14:40, Arthur Krewat <krewat at kilonet.net> wrote:
>
> Let's hope they do the right thing and release Solaris into the wild again. ZFS in particular.
>
> Personally, I think they are making a huge mistake. What are they going to do, move to Linux? Oh, right... the "cloud" will be Linux.
>
> Blech.
>
>> On 1/19/2017 3:49 AM, Wesley Parish wrote:
>> I suppose that set of rumours will lead to people shifting to the FOSS versions
>> of Solaris and SPARC.
>>
>> Wesley Parish
>>
>> Quoting Kay Parker <kayparker at mailite.com>:
>>
>>> guess it is the beginning of the end of Solaris and the Sparc CPU:
>>> 'Rumors have been circulating since late last year that Oracle was
>>> planning to kill development of the Solaris operating system, with
>>> major
>>> layoffs coming to the operating system's development team. Others
>>> speculated that future versions of the Unix platform Oracle acquired
>>> with Sun Microsystems would be designed for the cloud and built for the
>>> Intel platform only and that the SPARC processor line would meet its
>>> demise. The good news, based on a recently released Oracle roadmap for
>>> the SPARC platform, is that both Solaris and SPARC appear to have a
>>> future.
>>>
>>> The bad news is that the next major version of Solaris—Solaris 12—
>>> has
>>> apparently been canceled, as it has disappeared from the roadmap.
>>> Instead, it's been replaced with "Solaris 11.next"—and that version
>>> is
>>> apparently the only update planned for the operating system through
>>> 2021.
>>>
>>> With its on-premises software and hardware sales in decline, Oracle has
>>> been undergoing a major reorganization over the past two years as it
>>> attempts to pivot toward the cloud. Those changes led to a major speed
>>> bump in the development cycle for Java Enterprise Edition, a slowdown
>>> significant enough that it spurred something of a Java community
>>> revolt.
>>> Oracle later announced a new roadmap for Java EE that recalibrated
>>> expectations, focusing on cloud services features for the next version
>>> of the software platform. '
>>>
>> http://arstechnica.com/information-technology/2017/01/oracle-sort-of-confirms-demise-of-solaris-12-effort/
>>> --
>>> Kay Parker
>>> kayparker at mailite.com
>>>
>>> --
>>> http://www.fastmail.com - The way an email service should be
>>>
>>>
>>
>>
>> "I have supposed that he who buys a Method means to learn it." - Ferdinand Sor,
>> Method for Guitar
>>
>> "A verbal contract isn't worth the paper it's written on." -- Samuel Goldwyn
>>
>>
>
next prev parent reply other threads:[~2017-01-19 16:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 7:53 Kay Parker
2017-01-19 8:49 ` Wesley Parish
2017-01-19 14:40 ` Arthur Krewat
2017-01-19 16:39 ` Tim Bradshaw [this message]
2017-01-19 17:02 ` Arthur Krewat
2017-01-20 2:00 ` Nick Downing
2017-01-20 11:24 ` Joerg Schilling
2017-01-20 13:26 ` Random832
2017-01-20 14:23 ` Joerg Schilling
2017-01-20 14:29 ` Steve Nickolas
2017-01-20 15:20 ` Arthur Krewat
2017-01-20 15:45 ` Andy Kosela
2017-01-20 16:30 ` tfb
2017-01-20 19:38 ` Nemo
2017-01-21 0:25 ` Tim Bradshaw
2017-01-21 1:58 ` Rico Pajarola
2017-01-21 17:32 ` Arthur Krewat
2017-01-24 3:51 ` Rico Pajarola
2017-01-21 15:43 ` Nemo
2017-01-20 20:30 ` Steffen Nurpmeso
2017-01-20 22:30 ` Kay Parker
2017-01-20 23:50 ` Steffen Nurpmeso
2017-01-21 0:09 ` Steve Nickolas
2017-01-21 1:03 ` Kurt H Maier
2017-01-20 11:54 ` Tim Bradshaw
2017-01-19 18:17 ` Joerg Schilling
2017-01-20 14:58 Rudi Blom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B894AC3E-B97D-46F3-BBDC-EA72F39F6E49@tfeb.org \
--to=tfb@tfeb.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).