From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: =?utf-8?B?7KGw7ISx67mI?= Newsgroups: gmane.emacs.devel Subject: Re: "Why is emacs so square?" Date: Sun, 19 Apr 2020 16:04:01 +0900 Message-ID: <149F5B4D-F219-409C-A994-096C777259EC@icloud.com> References: <863691n4xl.wl-me@enzu.ru> <86blno9yle.wl-me@enzu.ru> <87d0845msg.fsf@yahoo.com> <87h7xgjasw.fsf@yahoo.com> <0B01B576-3DC7-4FAE-8010-C9B5CB6BA024@icloud.com> <87d084htcf.fsf@yahoo.com> Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Content-Type: text/plain; charset=utf-8; delsp=yes; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="117730"; mail-complaints-to="usenet@ciao.gmane.io" Cc: ndame , Ahmed Khanzada , Stefan Kangas , Joseph Garvin , Richard Stallman , Emacs developers , Eli Zaretskii , Drew Adams To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Apr 19 09:05:16 2020 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 1jQ40x-000UXH-Om for ged-emacs-devel@m.gmane-mx.org; Sun, 19 Apr 2020 09:05:15 +0200 Original-Received: from localhost ([::1]:38462 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jQ40w-00087z-Qz for ged-emacs-devel@m.gmane-mx.org; Sun, 19 Apr 2020 03:05:14 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52162) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jQ3zv-0007eK-3b for emacs-devel@gnu.org; Sun, 19 Apr 2020 03:04:11 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.90_1) (envelope-from ) id 1jQ3zu-0007yH-F3 for emacs-devel@gnu.org; Sun, 19 Apr 2020 03:04:10 -0400 Original-Received: from pv50p00im-ztdg10022001.me.com ([17.58.6.58]:37581) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jQ3zt-0007xk-W1 for emacs-devel@gnu.org; Sun, 19 Apr 2020 03:04:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=1a1hai; t=1587279848; bh=mx9s7wiV4J7UDFg/y0eZLBotAUCmzGIuU9PgV2oSbRU=; h=Content-Type:Subject:From:Date:Message-Id:To; b=ZU+1Bd/1Z3vDKi/D8rW3aZjv0YUrGm9B4q54Kys6heDZKwq/fZxV7T+9cgHqzdlve dMTfHh8OqlTyxvG+B4inNsKlxnrigUjAnokvDrTtTDhYD/ukszMY6jYnPW7u9vrXvw 1oQsEDHNE2cQIlOsJJTAecKn05uoIkZWD+YGf1vL2GguDAngB2vGd+WUc6O9+GVyii 69RpOmSuiVVtrYfCiYcUrtmgGSe53JzlZdTL4pZJuFNbdoKzbWeeB+4nzGXxY+fnu3 F/ajwqQZq8Xdmi330val0vaHjbo27Iw99lomcLgs+oZo69t4AepPhnne//R91HPNlG 47qA4YkpH6EJQ== Original-Received: from [192.168.0.3] (unknown [1.230.108.64]) by pv50p00im-ztdg10022001.me.com (Postfix) with ESMTPSA id 703BEA04B4; Sun, 19 Apr 2020 07:04:05 +0000 (UTC) In-Reply-To: <87d084htcf.fsf@yahoo.com> X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.676 definitions=2020-04-18_10:2020-04-17, 2020-04-18 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=18 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2002250000 definitions=main-2004190064 Received-SPF: pass client-ip=17.58.6.58; envelope-from=pcr910303@icloud.com; helo=pv50p00im-ztdg10022001.me.com X-detected-operating-system: by eggs.gnu.org: Linux 3.11 and newer X-Received-From: 17.58.6.58 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:247283 Archived-At: Po Lu 작성: > 조성빈 writes: > >> Skimming the Emacs Lisp intro doesn’t make one reasonably proficient in >> programming Emacs packages though. For one to understand how Emacs works >> (with it’s obscure naming scheme like windows), one has to jump a lot of >> hoops, and I can guarantee that one who is familiar with Algol-family >> languages can pick up the VSCode API much faster than picking up Lisp, >> Emacs, and the Emacs API. > > This is what gets interesting: Emacs Lisp is a language in it's own > right, and the "Emacs API" is the Emacs Lisp language. Emacs Lisp is > also a rather small and simple language. Emacs Lisp as a language and the standard library (the Emacs API) is different. For example, the fact that functions and variables have their own namespaces is a part of the language, and the functions self-insert-command or bury-buffer are parts of the API. You can call them as a whole Emacs Lisp, but that doesn’t mean that it’s more easier/simple than VSCode. Yes, Emacs Lisp isn’t a complex language like C++, but for outsiders that have never used Lisp, it’s hard to approach. Regardless, Emacs can’t stop using Emacs Lisp, so Emacs needs to be the reason for users to use Emacs Lisp, not backwards. And that means that Emacs should have a great onboarding experience (which is currently not true) with various packages for so many languages and productivity tools (which is IMHO true considering all of the packages in GitHub). > You don't have to pick up "Lisp", or the Emacs "API", you only > pick up Emacs Lisp. > >> But the default Emacs doesn’t have that, and that’s the problem. >> Which means that, for one to have nice OOTB experiences, one has to have >> a really good reason to use Emacs (like learning Common Lisp), then google >> how to configure Emacs, then encounter Spacemacs without knowing anything >> about evil or helm or ivy. And proficient Emacs users usually recommend >> not using a starter kit in the internet. (That’s my experience on trying >> to use Emacs.) > > We could put a link to them somewhere, but that's probably something for > RMS to decide. Yes, it would be very useful if we can include some links to the starter kits. Also, it would be great if Emacs can have a default init.el that gets generated when there is no one, so that first time users don’t get a bad impression. >> I don’t think OP was saying that we should use Electron for Emacs, but >> more >> that due to using Electron, it gives the stability that Emacs doesn’t >> give. >> Maybe you’ve only used Emacs on Linux, but at least on macOS, Emacs >> glitches, >> locks, and crashes very frequently, and that’s a non-starter for a lot >> of people. > > If it "glitches, crashes, locks", that's a bug, and instead of treating > it as a fact, report it. I know, I should report it, but I find that macOS/Windows is considered a second-platform here, and I didn't want to take my time writing reports just to get no feedback. I’ll try to report some today. (TBF, I remember trying to report them, searching for duplicates, and I saw some bug report on the exact same issue I was experiencing. I didn’t know how to subscribe, so I just thought that it might get fixed.) > Plus, I know a lot of people who use Emacs on > macOS, and I even had to use Emacs on Windows a long time back, and > Emacs has always been rather solid. The starter packs are also supposed > to work well, and it might also be a problem with your own config. > > OTOH, Lisp code shouldn't be able to make Emacs crash (unless you're > doing stuff like running invalid bytecode, or overflowing the GC stack), > and if it does, it's also a bug that should be fixed.