Date: Wed, 25 Aug 1999 12:04:02 +0300 (IDT) From: Eli Zaretskii X-Sender: eliz AT is To: Mumit Khan cc: djgpp AT delorie DOT com Subject: Re: fall of rsxntdj?? In-Reply-To: <7pv8on$hcs$1@news.doit.wisc.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On 24 Aug 1999, Mumit Khan wrote: > Sure Cygwin is buggy -- it's nowhere near as mature as DJGPP. However, > lots of people are using it and many may not care about the 10% cases. The point is that those 10% can e.g. prevent you from building a package, and the problems are so subtle that the average John Doe the Programmer can spend days on end without finding a solution. > But that's just a side issue here. I know of Mingw users using UWIN as > the platform, and there are others using Interix as the platform. Been there, done that. This was what a typical PC user needed to do circa 1986: to look on the net for various ports and clones of good development tools. The problem is they are all subtly incompatible, and a lot of effort went into making all that hodgepodge of programs work together in concert. A coherent package such as DJGPP or Cygwin solves these problems. > If DJGPP folks want an alternative to RSXNTDJ and find Mingw acceptable, > then someone will have to do the work of getting things to work together. > I however don't have time for it, nor do I have the incentive. I can only > offer some guidance, and a helping hand if time permits. No argument here. My message wasn't meant to suggest that you alone should do the work. It was meant to suggest a way to make Mingw a better development environment by tracking the path charted by DJGPP, and encourage interested people to start moving Mingw in that direction.