From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: ndame Newsgroups: gmane.emacs.devel Subject: Re: "Why is emacs so square?" Date: Sun, 19 Apr 2020 06:52:03 +0000 Message-ID: References: <863691n4xl.wl-me@enzu.ru> <86blno9yle.wl-me@enzu.ru> <87d0845msg.fsf@yahoo.com> <87h7xgjasw.fsf@yahoo.com> Reply-To: ndame Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="69020"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 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 08:53:41 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 1jQ3pU-000H7X-P5 for ged-emacs-devel@m.gmane-mx.org; Sun, 19 Apr 2020 08:53:24 +0200 Original-Received: from localhost ([::1]:38366 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jQ3pO-0003pl-QJ for ged-emacs-devel@m.gmane-mx.org; Sun, 19 Apr 2020 02:53:18 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46926) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jQ3oR-0002j4-V0 for emacs-devel@gnu.org; Sun, 19 Apr 2020 02:52:20 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.90_1) (envelope-from ) id 1jQ3oQ-0002Ze-MB for emacs-devel@gnu.org; Sun, 19 Apr 2020 02:52:19 -0400 Original-Received: from mail-40132.protonmail.ch ([185.70.40.132]:25040) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jQ3oP-0002V4-Ra for emacs-devel@gnu.org; Sun, 19 Apr 2020 02:52:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1587279135; bh=MJTJH4K5ykaSc4bbafEI/TqVi5kR6daqtLPD6wK8W2g=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=LZ1kMeMwEC33td+niYUegazlBY/fLlgC2b8Z/uGPUih1QiXXw6E7wUaJZ5rt33tdw mpTVkCOe4eRT+Ca/0KVpwBc2gtpgmQ2Spa8Tlat9iXVNhWN7uNarqZmGCL7DJEujHr iZCU4IiE+jCzHG+zNmQb4tqYE6Yuq1zqDXq3sX8A= In-Reply-To: <87h7xgjasw.fsf@yahoo.com> Received-SPF: pass client-ip=185.70.40.132; envelope-from=ndame@protonmail.com; helo=mail-40132.protonmail.ch X-detected-operating-system: by eggs.gnu.org: Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 185.70.40.132 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:247280 Archived-At: > > Here's the problem: You have to learn the VS Code API. I'd say learning > that, and becoming reasonably proficient at it takes longer than > skimming through the Emacs Lisp intro. Learning lisp needs a new mindset while the VS Code API is just a bunch of method calls. And you don't need to learn the whole API. When I wrote an extension for a test, to see how hard it is then I just googled things and used those parts which I needed. I certanly didn't learn the whole vscode API, because it wasn't necessary. > > VScode has a very nice out of the box experience. If you want support > > for a language then it's one click to install it and it installs the > > necessary scaffolding too, like a language server for the language. > > We have several starter packs, with similarly nice OOTB experiences. But they are not advertised on the emacs homepage, so a new user who just googles emacs doesn't necessarily know about them. > > Electron is not free software (https://labs.parabola.nu/issues/1167), > and is definitely not as well suited to providing an integrated > experience like Emacs. I know it's not free software. I just meant it provided many features out of the box which has to be implemented separately for emacs. > For instance, even if you render raw HTML inside VS Code, you would not > be able to grab the region using VSC APIs. I'm not sure if the VSC API > allows interacting with the DOM, but from what I can tell, it can't. Certainly, it's more limited some ways, you don't have the freedom to access everything like in Emacs. > > We have Cua mode. No, you don't need to have it enabled by default, > since it would result in unnecessary breakage for old users. Well, I think old users could adapt for the sake of new users. New users shouldn't encounter lots of strange concepts from the start. For example, the current tutorial may not be the best approach. Explaining about cursor movement with C-f and C-b? Windows and frames? Why a new user who casually wants to try emacs has to start with this? A new user can use the cursor keys and the mouse to operate the menus. Rather than focusing on strange keys for cursor movement a better approach could be explaining what emacs does better than other tools and how to use those features. And users could be informed on the startup screen that they can learn traditional emacs keys in a separate tutorial if they are interested. > > I personally think that the Emacs bindings are better, and in the end > work better with Emacs itself, but I do agree that newcomers should be > allowed to familiarize themselves with Emacs before moving their > workflow (and habits) to it entirely. Exactly. Users should encounter a familiar environment first, using the keys they are used to. They can always move on if they decide to stay with emacs.