From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: Next browser finally on master! Date: Wed, 19 Dec 2018 22:32:22 +0100 Message-ID: <87zht1i4nt.fsf@ambrevar.xyz> References: <87in085kk2.fsf@ambrevar.xyz> <87woo5y6yq.fsf@gnu.org> <87woo5mjzt.fsf@posteo.net> <877eg5jq3s.fsf@ambrevar.xyz> <8736qttg3h.fsf@elephly.net> <87tvj9mf12.fsf@posteo.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50031) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gZjSQ-00036F-12 for help-guix@gnu.org; Wed, 19 Dec 2018 16:32:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gZjSL-0005Ne-4E for help-guix@gnu.org; Wed, 19 Dec 2018 16:32:45 -0500 Received: from relay8-d.mail.gandi.net ([217.70.183.201]:43847) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gZjSK-0005NM-TE for help-guix@gnu.org; Wed, 19 Dec 2018 16:32:41 -0500 In-reply-to: <87tvj9mf12.fsf@posteo.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Brett Gilio Cc: help-guix --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Brett Gilio writes: > Excuse me for not being fully aware, are you involved in the development > of the Next browser? I am! John Mercouris is the original author, and I've implemented the WebK= itGTK platform for Next. Ricardo Wurmus writes: > I=E2=80=99ve read that discussion, but I don=E2=80=99t see how it is rele= vant. > The *name* of the package surely does not have any effect on the > features, does it? > > For applications like StumpWM and Next we could change the package names > to =E2=80=9Cstumpwm=E2=80=9D and =E2=80=9Cnext=E2=80=9D, respectively. Don't get me wrong, I don't have a strong opinion against this change. But Lisp is special, and common sense for other packages / programming languages don't necessarily apply here. A few points to consider: =2D While StumpWM has dropped support for anything but SBCL, Next browser plans to support CCL (it already works but for one thing). So we could have a ccl-next package. =2D As far as I understand, the compiler *does* change the resulting binary, thus the resulting REPL experience will be different, because all Lisps are different beyond the ANSI standard and other undefined behaviour. In other words, connecting via SLIME to ccl-next or sbcl-next would result in a different environment. > That these packages can *also* be used as libraries does not mean that the > packages should have names with the =E2=80=9Csbcl-=E2=80=9D or =E2=80=9Cc= l-=E2=80=9D or =E2=80=9Cother-lisp-=E2=80=9D prefix. That would not be consistent with the Lisp library naming scheme then. And it raises the question as to why we have bothered with the sbcl- and ecl- prefixes so far. Andy, any opinion on this? =2D- Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAlwauOYACgkQm9z0l6S7 zH8pFQf/bvfEAd3F5taINbr2VYeft/SCqtOOQbApmDqaO4qhvaVReMzizedpnCm7 gSLW8W+2DRKffBaUpLkJwSd/8wNt99aYQM3vsj6Z4w3acS5itIeKb34DpFW2lj8s llAaEKzKhLpVB8k18hKa0XboBVsQd8OGkbmeGuaoxb2GyryyiipVBJpZpwWRRY69 NIHtP1cTGMhDT0ZDOf0h1zK8lJu27yYKm5vT+sy1rdxXCBq+1aVTcKHiwb9wGpNx stPhy+HdURLgG2HNlMPVBKGkL1c6ULRqTsnSBBjjJb/Hrty0m6sd9aWsPb+e0aKc VM5sB+xpMjVgn/Nqm3f02QkzmhsWNg== =Y7sN -----END PGP SIGNATURE----- --=-=-=--