From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "Alfred M. Szmidt" Newsgroups: gmane.emacs.devel Subject: Re: Android port of Emacs Date: Sat, 17 Jun 2023 12:47:44 -0400 Message-ID: References: <83v8fnslfz.fsf@gnu.org> <83edmask4z.fsf@gnu.org> <874jn6fue3.fsf@yahoo.com> <83zg4yr1tf.fsf@gnu.org> <87r0qaee6b.fsf@yahoo.com> <83jzw2qy0l.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30182"; mail-complaints-to="usenet@ciao.gmane.io" Cc: luangruo@yahoo.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jun 17 18:48:36 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qAZ6J-0007aM-7s for ged-emacs-devel@m.gmane-mx.org; Sat, 17 Jun 2023 18:48:35 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qAZ5Y-0005Co-EQ; Sat, 17 Jun 2023 12:47:48 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qAZ5V-0005C3-E6 for emacs-devel@gnu.org; Sat, 17 Jun 2023 12:47:45 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qAZ5V-0006Xt-5b; Sat, 17 Jun 2023 12:47:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=Date:References:Subject:In-Reply-To:To:From: mime-version; bh=LXYJyCv28BKSeU1XoxiYPEyuifdF/s86ZMAMhiTnzN0=; b=Qx8AGGsgkS9D dhhZUBEFnBeW0DwnbfWCQ2PWziCpjy8PQF8UkbqR3f7wd61Xr6Wdgrub3kygpqGvslGw+O47NbDo4 SCRQ57mz/qysv50uS1xSZYOLO0pWseUSWd7LxAIWRnUNzMLmlo0F6dFr6eEXSM+xiJX/t4TypO3Rl TeUDv34SMYnbAMNnFLdAGOKJJtJTKnMb4zuYbm7R8c2Ta/aR1ns3rW0bZ9YkmrQO0HVnkGcPPrXKl d72Q+8R6sz9aIjgQOFqhZME0yZs1I6j4Wv7S0Osoc+0g4aTyecAbDT8bk52miIhNCgZxkwvdzAhNb yvSZTNIhkYY5cGiqBEvOgA==; Original-Received: from ams by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1qAZ5U-0001e2-Us; Sat, 17 Jun 2023 12:47:44 -0400 In-Reply-To: <83jzw2qy0l.fsf@gnu.org> (message from Eli Zaretskii on Sat, 17 Jun 2023 11:43:54 +0300) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:306882 Archived-At: > > Your work is appreciated, but I'm unconvinced that it can make the > > impact of this port easy enough to not break our backs. Rather than > > relying on beliefs, I'd like to rely on experience with other ports, > > and on general experience with Emacs development. > > I designed the Android port _with_ said experience in mind. Including > design mistakes in the Haiku and PGTK ports that I have since fixed. I was talking about long-term experience of developing and maintaining various ports in Emacs. You cannot possibly have such an experience. One can view it as someone getting that long term experience, I tink Po Lu has shown to be quite the long term hacker when it comes to GNU Emacs. Giving them the responsibility of said port is a good way to nourish, and grown such experience. But yeah, as in a previous message of Eli, there are jobs that have to be done. E.g., what happens if this port delays a release in some manner (Po Lu not having the time to address the issue, or it is complicated, whatever)? Does that delay the whole release of Emacs, is it addressed in a bug fix release ... Maybe there could be made some rules about what happens if the port (or any port) starts lagging behind.