public inbox for
 help / color / mirror / Atom feed
From: Corinna Vinschen <>
Subject: Re: Manifest Density [Was: Re: cygcheck -svc segfaults on Windows 8.1 with cygwin64]
Date: Thu, 21 Nov 2013 11:06:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]

On Nov 20 18:53, Warren Young wrote:
> On 11/20/2013 05:53, Charles Wilson wrote:
> >So it's a play on words: Manifest Density vs. Manifest Destiny.
> Yes.
> The policy of manifest destiny is a form of pure arrogance: This is
> the way it will happen and everyone will either like it or get
> steamrolled by the inevitable.
> ...Much like Microsoft "encouraging" apps to use manifest files.
> And I agree, the Microsoft policy implemented by this API *is*
> dense. The denser an object is, the less affected it is by incoming
> matter. Density is a function of arrogance, so when reason speaks to
> arrogance, little happens.

What bugs me most is that this manifest enforcement runs completely over
the head of community-driven projects.

But even so.  If some company wants to make sure their applications run
on the new OS, it's *not* enough anymore to test.  "Yeah, our product
still works, nothing to do".  Rather, Microsoft practically forces 
software companies to create new versions, which is a big deal and costs
money for nothing.  And in a case of a community project like Cygwin,
we just can't rebuild all of our packages just to follow up with new

Fortunately there is the chance to use side-by-side manifests, but that's
really ugly, isn't it?  Twice as many entries in /bin, urgh.


[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2013-11-21 11:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
     [not found]   ` <>
     [not found]     ` <>
     [not found]       ` <>
     [not found]         ` <>
2013-11-20 12:53           ` Charles Wilson
2013-11-20 13:29             ` Corinna Vinschen
2013-11-20 16:47               ` JonY
2013-11-21  7:59                 ` Gary Johnson
2013-11-21  1:53             ` Warren Young
2013-11-21 11:06               ` Corinna Vinschen [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).