From: akosela@andykosela.com (Andy Kosela)
Subject: [TUHS] Oracle euthanizes Solaris 12, expunging it from roadmap
Date: Fri, 20 Jan 2017 09:45:35 -0600 [thread overview]
Message-ID: <CALMnNGiWy2k7SxHmmVYQTageXVgb9DHJ8aXoMuq+wP-QFE=91A@mail.gmail.com> (raw)
In-Reply-To: <d294e3ab-e19c-7a7c-3674-5088382d9ff3@kilonet.net>
On Friday, January 20, 2017, Tim Bradshaw <tfb at tfeb.org
<javascript:_e(%7B%7D,'cvml','tfb at tfeb.org');>> wrote:
>
> And it's also why they slowly die: their market ends up being people who
> have huge critical legacy systems which they need to maintain, not people
> who are building new systems. Indeed even the people with the great legacy
> chunks of software, when they build new systems, start using the shiny new
> platforms, because the shiny young people they hire to do this like the new
> platforms.
>
>
>
I understand that Linux can still be called a new kid on the block, but it
is actually not "a new platform" anymore. It has been deployed (along with
FreeBSD) in large corporations for around 20 years now. It really
became the Standard OS from embedded world to supercomputers.
Personally I do not find this to be a bad thing, because with OS
standardization comes uniformity, and I would rather have one true
Unix standard than hundreds of incompatible ones.
I believe that the future of proprietary UNIX is doomed and the only
remaining choices for server operating systems will be Linux and Windows in
the near future. If you think about it, the future is already here...
--Andy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170120/f6083763/attachment.html>
next prev parent reply other threads:[~2017-01-20 15:45 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
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 [this message]
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='CALMnNGiWy2k7SxHmmVYQTageXVgb9DHJ8aXoMuq+wP-QFE=91A@mail.gmail.com' \
--to=akosela@andykosela.com \
/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).