unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Ryan Prior <ryanprior@hey.com>,
	Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl>
Cc: Development of GNU Guix and the GNU System distribution
	<guix-devel@gnu.org>
Subject: Re: Latest Nyxt features a GUI for Guix :)
Date: Thu, 12 Nov 2020 10:20:10 +0100	[thread overview]
Message-ID: <871rgzgcdx.fsf@ambrevar.xyz> (raw)
In-Reply-To: <0dfacdc4d261507fc25735e5e4bde388dff2982c@hey.com>

[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]

Ryan Prior <ryanprior@hey.com> writes:

> On November 11, 2020, Jan Wielkiewicz
> <tona_kosmicznego_smiecia@interia.pl> wrote:
>> [web browsers are] a really poorly designed copy of
>> operating systems and its utilities.
>>
>> [...]
>>
>> I just don't understand why in the web browser.
>> I'll try it.
>
> The web browser is the primary operating environment for a lot of
> people. Just as Emacs users built web browsers, terminal emulators, and
> mail clients on the Emacs platform, the web platform also has all those
> things (including various elaborate in-browser code editors.) So I
> understand this as having the exact same genesis as the Guix interface
> in Emacs: people would like to manage their operating system using the
> interface they spend most of their time in, and for Nyxt power users
> that would be their browser. I'm not at all interested in managing my
> Guix packages using Nyxt, which is highly correlated to my not being a
> Nyxt power user.

Exactly :)

To add to what Ryan said, Nyxt has a interesting design feature: it does
not need to depend on a web browser!  Nyxt is rather a 
"Common Lisp interactive framework" and it would be perfectly possible
to implement a textual interface à-la Emacs.  Of course, web page
rendering would be much more limited though.

I'd like to work on a pure GTK (or <insert-your-fav-toolkit-here>)
version of Nyxt at some point.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]

  reply	other threads:[~2020-11-12  9:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-11 14:41 Latest Nyxt features a GUI for Guix :) Pierre Neidhardt
2020-11-11 14:42 ` Pierre Neidhardt
2020-11-11 18:50   ` Bengt Richter
2020-11-12  9:21     ` Pierre Neidhardt
2020-11-11 17:21 ` Jan Wielkiewicz
2020-11-11 18:35   ` Pierre Neidhardt
2020-11-11 21:56     ` Jan Wielkiewicz
2020-11-11 22:08       ` Ryan Prior
2020-11-12  9:20         ` Pierre Neidhardt [this message]
2020-11-12 16:06           ` Jan Wielkiewicz
2020-11-12 16:10             ` Pierre Neidhardt
2020-11-12 20:46           ` Ricardo Wurmus
2020-11-13  8:53             ` Pierre Neidhardt
2020-11-12  8:51       ` Ricardo Wurmus
2020-11-12 16:00         ` Jan Wielkiewicz
2020-11-12 17:21           ` Ricardo Wurmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871rgzgcdx.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=guix-devel@gnu.org \
    --cc=ryanprior@hey.com \
    --cc=tona_kosmicznego_smiecia@interia.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).