From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Paul Michael Reilly Newsgroups: gmane.emacs.devel Subject: Re: Emacs on OS X development Date: Sun, 15 Jul 2012 09:12:49 -0400 Message-ID: References: <33545A47-0907-4059-92A6-0343CEDD2750@swipnet.se> <869E965F-CD75-46D6-92BB-B3C08C8D846B@swipnet.se> <87fw8t7siv.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b10cb0ff5660404c4de1143 X-Trace: dough.gmane.org 1342357982 20732 80.91.229.3 (15 Jul 2012 13:13:02 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 15 Jul 2012 13:13:02 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jul 15 15:13:01 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SqOd6-000561-QF for ged-emacs-devel@m.gmane.org; Sun, 15 Jul 2012 15:12:57 +0200 Original-Received: from localhost ([::1]:58969 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SqOd6-0008Lp-21 for ged-emacs-devel@m.gmane.org; Sun, 15 Jul 2012 09:12:56 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:60011) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SqOd3-0008LU-6E for emacs-devel@gnu.org; Sun, 15 Jul 2012 09:12:54 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SqOd1-0005Sd-Of for emacs-devel@gnu.org; Sun, 15 Jul 2012 09:12:53 -0400 Original-Received: from mail-pb0-f41.google.com ([209.85.160.41]:54038) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SqOd1-0005SZ-Em for emacs-devel@gnu.org; Sun, 15 Jul 2012 09:12:51 -0400 Original-Received: by pbbrp2 with SMTP id rp2so9661369pbb.0 for ; Sun, 15 Jul 2012 06:12:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=6oe8QaAFXgqwRNBZj5+s7eILdwvYJtOgw3Weu5aflTU=; b=HCs/FQ9uGfc4TCMCi/pO03UXvf3eYNwhpf7T8+wE0Y4gWMgBEPICPytf6KLusGT2QX CglWPsijCpGXsmUPIOBxQhiAbaOqaQ/1I73R5iePdqDCx/51LNzeICXhH3WTl+z46RON 0yBg1pjM0FpqdZDK1Z/+x8h0a2Pk/1xkp/PTSnFz51wFDcwmEqa7/ftlxNWyqhOsCHaI iQKlyfJiHye5W3cOWc/RyhGfWuyUo1R7BNNJkOv3bqeZdXPf8vIEyqs7HCocgVBn42Lv E1lpCSmzn0eI5jxSqNkSc5MCFoOB6zHEFjJZ+O2RLdvC6Bgw6EvJW7eB7K0vkkZAv0Gx O52w== Original-Received: by 10.68.194.201 with SMTP id hy9mr18935229pbc.69.1342357969921; Sun, 15 Jul 2012 06:12:49 -0700 (PDT) Original-Received: by 10.142.163.4 with HTTP; Sun, 15 Jul 2012 06:12:49 -0700 (PDT) In-Reply-To: X-Gm-Message-State: ALoCoQnSyutfbroNPMXq5aJJzDOyVaf7dqv9ZRd8JSctW1v7YmHPYx+49yOj5KY++87O6HxPXisd X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.85.160.41 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:151622 Archived-At: --047d7b10cb0ff5660404c4de1143 Content-Type: text/plain; charset=ISO-8859-1 On Sat, Jul 14, 2012 at 11:40 PM, John Wiegley wrote: > >>>>> Chong Yidong writes: > > > Look, no one is saying that you're not allowed to improve the Mac OS > part of > > the Nextstep port, or that the GNUstep part must must work exactly as > well > > as the Mac OS part. On the contrary; if you want to help improve it, go > > right ahead. > > And I am doing so right now, by suggesting we adopt Yamamoto's work. :) > And I concur. Perhaps someone can explain to me the downside of having Yamamoto place his tree as a sibling to the ns tree. I do not understand why this would be a bad thing. On the other hand, having both side by side will undoubtedly allow me to figure out much more about (and more easily) what is going on and why one version is better than the other, etc. It just seems intuitively obvious that having both sit side by side will increase interest that will likely improve both. At least for a while. Over the long haul I suspect most development will favor one over the other. My preference is to give them both a chance to thrive together. That said, I use the ns tree daily and love it. The fonts look pretty good to me. I click on the green maximize button (twice) and get a full screen experience that works for me. Speed has never been an issue. So I'm scratching my head over where the pain point is in the ns code. Maybe I should just fix a bug or two, if only to start feeling Yamamoto's pain wrt the quality of the coding experience inside the ns tree. Someday, when it is trivially easy to build the Yamamoto code, I will try that instance too just to see the differences and compare the approaches. -pmr --047d7b10cb0ff5660404c4de1143 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Sat, Jul 14, 2012 at 11:40 PM, John Wiegley <= span dir=3D"ltr"><johnw@newartisans.com> wrote:
>>>>> Chong Yidong <cyd@gnu.org> writes:

> Look, no one is saying that you're not allowed to improve the Mac = OS part of
> the Nextstep port, or that the GNUstep part must must work exactly as = well
> as the Mac OS part. =A0On the contrary; if you want to help improve it= , go
> right ahead.

And I am doing so right now, by suggesting we adopt Yamamoto's wo= rk. :)

And I concur. =A0Perhaps someone= can explain to me the downside of having Yamamoto place his tree as a sibl= ing to the ns tree. =A0I do not understand why this would be a bad thing. = =A0On the other hand, having both side by side will undoubtedly allow me to= figure out much more about (and more easily) what is going on and why one = version is better than the other, etc. It just seems intuitively obvious th= at having both sit side by side will increase interest that will likely imp= rove both. =A0At least for a while. =A0Over the long haul I suspect most de= velopment will favor one over the other. =A0My preference is to give them b= oth a chance to thrive together.

That said, I use the ns tree daily and love it. =A0The = fonts look pretty good to me. =A0I click on the green maximize button (twic= e) and get a full screen experience that works for me. =A0Speed has never b= een an issue. =A0So I'm scratching my head over where the pain point is= in the ns code. =A0Maybe I should just fix a bug or two, if only to start = feeling Yamamoto's pain wrt the quality of the coding experience inside= the ns tree.

Someday, when it is trivially easy to build the Yamamot= o code, I will try that instance too just to see the differences and compar= e the approaches.

-pmr
--047d7b10cb0ff5660404c4de1143--