The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jon@fourwinds.com (Jon Steinhart)
Subject: [TUHS] What UNIX Artifacts Are Still Missing?
Date: Wed, 06 Dec 2017 22:14:15 -0800	[thread overview]
Message-ID: <201712070614.vB76EFiQ014953@darkstar.fourwinds.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1712071552450.28409@sirius.opentrend.net>

Robert Brockway writes:
> On Thu, 7 Dec 2017, Dave Horsfall wrote:
> 
> > Call me a cynical old bastard (which I am), but I can't see M$ raising a flag 
> > for Unix...  Wasn't it Billy Gates who reportedly said that any PC running 
> > Linux is one not running Windoze, and did his best to discredit it?
> 
> Microsoft today is not the company of old.  In recent years Microsoft has 
> participated in standards bodies and worked on interoperability with other 
> browser vendors.  They even joined the Linux Foundation last year.
> 
> https://techcrunch.com/2016/11/16/microsoft-joins-the-linux-foundation/
> 
> Cheers,
> 
> Rob

Don't know how much time you've spent on standards committees; I've done my
time.  Standards committees are not filled with altruistic folks working to
make something great.  Much of the time people are there to prevent a standard
from interfering with their market, or to prevent a good standard from being
adopted.  The examples of the NSA participating on crypto committees to weaken
the standards got a lot of press and is emblematic of what happens.  Microsoft
has a well documented record of using standards to screw the competition so I
didn't read any goodness into their joining up.  I would agree that they're not
the company of old in that they got themselves trounced by Apple and are no
longer top dog and able to tell others what they're allowed to do.

Jon


  parent reply	other threads:[~2017-12-07  6:14 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.400.1512518427.9955.tuhs@minnie.tuhs.org>
2017-12-06 11:25 ` Paul Ruizendaal
2017-12-06 12:58   ` Mutiny 
2017-12-06 14:33     ` Paul Ruizendaal
2017-12-06 17:13       ` Clem Cole
2017-12-06 19:27         ` Paul Ruizendaal
2017-12-07  6:14         ` Jason Stevens
2017-12-06 22:32       ` Dave Horsfall
2017-12-07  5:05         ` Jason Stevens
2017-12-07  5:46           ` Dave Horsfall
2017-12-07  5:40         ` Andy Kosela
2017-12-07  5:56         ` Robert Brockway
2017-12-07  6:07           ` Warner Losh
2017-12-07 17:47             ` Grant Taylor
2017-12-09  6:03               ` Nigel Williams
2017-12-07  6:14           ` Jon Steinhart [this message]
2017-12-07  7:02             ` Robert Brockway
2017-12-07 16:22               ` Jon Steinhart
2017-12-07 14:59             ` Larry McVoy
2017-12-07 15:40               ` Steve Simon
2017-12-07 15:42               ` Chet Ramey
2017-12-07 16:28             ` Clem Cole
2017-12-07 16:30               ` Clem Cole
2017-12-06 17:55   ` Warner Losh
2017-12-07 15:14 Noel Chiappa
2017-12-07 15:36 ` Nevin Liber
  -- strict thread matches above, loose matches on Subject: below --
2017-12-06 17:59 Rudi Blom
     [not found] <mailman.398.1512513526.9955.tuhs@minnie.tuhs.org>
2017-12-06 11:22 ` Paul Ruizendaal
2017-12-05 22:45 Nelson H. F. Beebe
2017-12-05 22:21 Warren Toomey
2017-12-05 22:38 ` Robert Swierczek
2017-12-05 22:55 ` Angelo Papenhoff
2017-12-05 23:06   ` Warner Losh
2017-12-05 23:03 ` Dave Horsfall
2017-12-06  0:00 ` Robert Swierczek
2017-12-06  0:08   ` Grant Taylor
2017-12-06 15:23   ` Clem Cole
2017-12-06  5:54 ` arnold

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=201712070614.vB76EFiQ014953@darkstar.fourwinds.com \
    --to=jon@fourwinds.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).