DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:references
	:mime-version:content-type:content-transfer-encoding
	:in-reply-to; q=dns; s=default; b=iKIvDswOWBMuaJiESvGmZR+FP4un5+
	ZkeVjGcRW7Cw7mrPPMRSBFK/q63xoPaKUCdYlmE+7JTMf5r07SGcXkR4CBC6oJ1N
	UTL2faoMpfrX1vGHAc/gbyzY3DulWh2le8UBCqPNDI1Ko86JMjX4pRd+eupe/zy1
	+08yPnDfL/rzA=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 14 Apr 2016 16:49:19 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: cygwin@cygwin.com
Subject: Re: native Linux userland in Windows 10
Message-ID: <20160414204916.GB7622@mercury.ccil.org>
References: <416uDmm4T7200S05.1460552179@web05.cms.usa.net> <84CCF5B5-9F11-4541-A527-FD0BD3AE5545@etr-usa.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <84CCF5B5-9F11-4541-A527-FD0BD3AE5545@etr-usa.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

Warren Young scripsit:

> Third, given a choice between the Cygwin package repo and the Ubuntu
> package repo, well, no contest, yes?  That’s also why Ubuntu and
> not, say, Fedora or Arch; Microsoft chose the biggest single package
> repo available.

I'm not so sure of that.  Canonical is fairly friendly to non-FLOSS
software, although the great bulk of the distro is of course FLOSS.  
It may be a matter of who MS thought they could best work with.

> But to drag all of this back on topic, UfW is Microsoft saying,
> “Yes, we know we screwed up.  Please accept this full apology.”  A
> whole lot of people are going to accept that gratefully.

Ever since I had to switch to Win64, I've missed CoLinux (which apparently
is no longer being developed).  UoW, once the bugs are flushed, will
look a lot like that: the Windows filesystem is visible but the Win32
executables don't work.  (Wine on UoW?  Who knows?)

> Under PowerShell, you run a command line, get a given output, but then
> still have no obvious solution because the command’s representation
> may materially change in a pipeline, so now you have to go chasing
> through the MSDN docs or reflection APIs to work out how to crawl its
> list-of-objects representation.

There are of course a few Posix commands like that, notably ls.
It's just that we are used to them, and they usually do the Right Thing
when the output is not a tty.

> UfW will be completely independent of Cygwin.  More’s the pity,
> because it means you’ll be incentivized to choose one or the other,
> likely to Cygwin’s net detriment.

Based on my CoLinux experience, I expect I'll keep Cygwin but won't
use it as much as I do today.  It will still be indispensable for some
things.

-- 
John Cowan          http://www.ccil.org/~cowan        cowan@ccil.org
Not to perambulate the corridors during the hours of repose
in the boots of ascension.       --Sign in Austrian ski-resort hotel

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple