From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Android port of Emacs Date: Fri, 23 Jun 2023 15:08:34 +0300 Message-ID: <83lega1iv1.fsf@gnu.org> References: <83v8fnslfz.fsf@gnu.org> <83edmask4z.fsf@gnu.org> <5c02371a-3c42-de66-70b7-4ed0d88cc3fa@gutov.dev> <834jn159vs.fsf@gnu.org> <831qi23bif.fsf@gnu.org> <87jzvuy2e7.fsf@yahoo.com> <83sfai1nq6.fsf@gnu.org> <87cz1mxvc2.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9765"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rms@gnu.org, emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jun 23 14:09:25 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 1qCfbR-0002ID-Ca for ged-emacs-devel@m.gmane-mx.org; Fri, 23 Jun 2023 14:09:25 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qCfaZ-0004RD-DM; Fri, 23 Jun 2023 08:08:31 -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 1qCfaW-0004HV-R0 for emacs-devel@gnu.org; Fri, 23 Jun 2023 08:08:28 -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 1qCfaW-0004w8-DX; Fri, 23 Jun 2023 08:08:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=cRzfdllnGVSLCnrw/u0/g1ih/iU7DzUJi/zRmcT0XAs=; b=gJHihkOXzX02 VIKNe5H+Wn2S+5TGHuiNI2jR3ON3I7hHTwuAyTaJGcMQmKPlqy7TLz+2frFh55afbl+7Ru5OpHvfK 5gW3/IFC5cRmeaxzrlbRqZhw6fDI/K7mbwceeZTO7gMSiojW7Az+Icq4xjGCG1QoZSiSM04WMfId+ RV7+8RTt7YjK1o+qrRZghPNYAiZwGbIO/cSEFtJD4ZI0QKg2Iv7L1PxoKr2r9US6LSJBeQezaMJlC P19HGU5XKsTMt29SZ83XAO6M41yxsY4soPNh/zVP+fAQTJc+gwWh1CQvsex1zos119PW7lTgFhkJg U6DT14yG9aHfnrIxUcSUjw==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qCfaO-0003Ir-Nn; Fri, 23 Jun 2023 08:08:21 -0400 In-Reply-To: <87cz1mxvc2.fsf@yahoo.com> (message from Po Lu on Fri, 23 Jun 2023 19:38:05 +0800) 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:307158 Archived-At: > From: Po Lu > Cc: rms@gnu.org, emacs-devel@gnu.org > Date: Fri, 23 Jun 2023 19:38:05 +0800 > > Eli Zaretskii writes: > > > You are not answering any of the questions I raised. > > Well, I've been reiterating the same stuff over and over, because you've > been doing the same thing. I'm pointing, time and again, to the main issues that caused me to start this, in the hope that someone will finally relate to those issues and starts discussing them, instead of dancing around them. > I think that in the eyes of most people (me included), the downsides of > releasing Emacs with a port that is broken is negligible, if the port > itself is so unimportant that nobody steps up to fix it before the > release is made. So, in fact, this is very much an imaginary issue: > either it will get fixed, or it will be broken -- and I've been trying > hard to make sure it won't be broken. This is how most free software > treats ports to systems that aren't considered important, and is the > only proven way to remain portable while development is being undertaken > by volunteers. This description doesn't fit the reality. People who use the NS port are quite disappointed by the problems that don't get solved, and I as the maintainer cannot remain indifferent to their plight. It breaks my heart that I can do almost nothing to facilitate the solution of those problems. And mind you, no one thinks the NS problems are "unimportant", we are just unable to fix them, even though we all agree they are grave and should be fixed ASAP. So you might be indifferent to such problems, or consider them "unimportant", but IMO any responsible maintainer will not; I certainly am not. And if we envision such problems to happen sooner rather than later to the Android port, we may wish to decide whether we want this now, before the danger becomes real -- as it became with other similar features.