public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "KARL BOTTS" <kdbotts@usa.net>
To: <cygwin@cygwin.com>
Subject: RE: native Linux userland in Windows 10
Date: Wed, 13 Apr 2016 12:56:00 -0000	[thread overview]
Message-ID: <416uDmm4T7200S05.1460552179@web05.cms.usa.net> (raw)


What baffles me is, why didn't MS just arrange to support Cygwin more
directly, e.g., make a "blessed" distribution mechanism for Cygwin available
to their users?  Surely this could have been worked out: they have some sort
of "partnership" with RedHat, they claim.

I put a lengthy comment to that effect in the forum associated with that
video, after a colleague who was at the "Build Conference" in SF emailed it to
me last week.  (There may be more than one video.)

I do not think they have really considered the integration issues that Cygwin
has mostly solved.  Not just permissions, but small things like cygpath and
such utilities.  No doubt they can, but will they stick to it long enough to
make everything work?  I have my doubts.

Remember, they have tried basically the same thing at least twice before: the
"POSIX Subsystem" of WinNT, and the "Unix Tools for Windows".  Both failed and
have been abandoned.  And PowerShell is sort of another try: do you all know
that they started from the old ksh sources, somehow?  But they totally screwed
up PS, from my point of view, by making it deal primarily with binary streams
of proprietary data instead of text.  That may make it better for a former
CMD.EXE user, but it does not integrate at all with anything else.  For
instance, trying to pipe PS output into a bash script, or vice versa, is a
nightmare.  I have given up.

At the end of the day, mass Windows users just don't get the whole idea of a
shell as an integrator of software tools.  They think it is supposed to make
pretty pictures in a console emulator, as a poor substitute for a GUI.  I
suspect that will lead MS to screw up their Unix environment, to make it more
friendly to their primary user base.  Which will make it useless to me.

I could be wrong.  I'll give it a year or two to settle, and then give it a
try.  I just hope it does not interfere too much with my Cygwin setup, which I
expect to keep for the foreseeable future.


---
Karl Botts, kdbotts@usa.net


--
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

             reply	other threads:[~2016-04-13 12:56 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13 12:56 KARL BOTTS [this message]
2016-04-13 13:21 ` John Cowan
2016-04-14 15:58 ` Warren Young
2016-04-14 17:18   ` Andrew Schulman
2016-04-14 19:20   ` Andrey Repin
2016-04-14 19:26     ` Eliot Moss
2016-04-14 20:40     ` John Cowan
2016-04-14 22:50       ` Andrey Repin
2016-04-14 23:34         ` John Cowan
2016-04-15 10:05           ` Andrey Repin
2016-04-15 16:27             ` John Cowan
2016-04-17 21:35               ` Andrey Repin
2016-04-18  5:45                 ` Don't descend into a flame war. was: " Herbert Stocker
2016-04-18 13:51                   ` cyg Simple
2016-04-14 23:09     ` Warren Young
2016-04-14 23:53       ` John Cowan
2016-04-15 10:05       ` Andrey Repin
2016-04-20 22:23         ` Warren Young
2016-04-21 11:56           ` David Macek
2016-04-21 16:31             ` John Cowan
2016-04-22  8:04               ` David Macek
2016-04-22  8:40                 ` Steven Hartland
2016-04-22  4:37           ` Andrey Repin
2016-04-14 20:49   ` John Cowan
  -- strict thread matches above, loose matches on Subject: below --
2016-04-12 12:51 Andrew Schulman
2016-04-12 12:59 ` Marco Atzeri
2016-04-12 13:41   ` Corinna Vinschen
2016-04-12 14:41     ` Philip Daniels
2016-04-12 14:54     ` wilson
2016-04-12 17:01       ` Andrew Schulman
2016-04-12 19:22         ` Eliot Moss
2016-04-12 22:08           ` Warren Young
2016-04-13 15:35             ` Andrey Repin
2016-04-13 18:21               ` John Cowan
2016-04-14  0:14               ` John Cowan
2016-04-14  1:05                 ` Andrey Repin
2016-04-14  3:06                 ` Eliot Moss
2016-04-14 18:35                   ` Andrey Repin
2016-04-14 14:50               ` Warren Young
2016-04-14 15:08                 ` Alexey Sokolov
2016-04-14 17:35                   ` Eliot Moss
2016-04-14 18:35                     ` Andrey Repin
2016-04-14 18:37                       ` Eliot Moss
2016-04-14 18:35                 ` Andrey Repin
2016-04-12 17:37       ` Achim Gratz
2016-04-13  0:12   ` Andrew Schulman
2016-04-13  5:02     ` Herbert Stocker
2016-04-12 17:42 ` Achim Gratz
2016-04-13  5:20 ` Herbert Stocker
2016-04-13  9:41 ` Gerrit Haase
2016-04-13 10:17   ` Tony Kelman
2016-04-15 11:12 ` Tobias Zawada
2016-04-15 16:48   ` John Cowan

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=416uDmm4T7200S05.1460552179@web05.cms.usa.net \
    --to=kdbotts@usa.net \
    --cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).