From: "Ludovic Courtès" <ludo@gnu.org>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: zimoun <zimon.toutoune@gmail.com>,
Guix Devel <guix-devel@gnu.org>,
GNU Guix maintainers <guix-maintainers@gnu.org>
Subject: Re: Release v1.4?
Date: Fri, 17 Jun 2022 17:31:33 +0200 [thread overview]
Message-ID: <87bkurfgru.fsf@gnu.org> (raw)
In-Reply-To: <87mted7zm4.fsf@jpoiret.xyz> (Josselin Poiret's message of "Thu, 16 Jun 2022 10:59:31 +0200")
Hi,
Josselin Poiret <dev@jpoiret.xyz> skribis:
> I'm not sure, it does seem like a fraction of people use it on IRC but
> then again it's more likely that Wayland users would talk about it, X
> being the default. If there are no outstanding bugs with Wayland Gnome
> though, I think it'd be a better choice: no tearing in the default
> configuration, and better designed. GUI Toolkits seem to have adapted
> pretty well, and we still have XWayland for the rest. The most glaring
> non-Wayland app would be Emacs, but emacs-next-pgtk is fully
> Wayland-native.
So plain ‘emacs’ package doesn’t work on Wayland? That sounds like a
recipe for a poor user experience, no?
(FWIW folks like me who use exwm, ratpoison, or one of these geeky
tiling window managers probably can’t switch.)
> For me the #1 reason though is onboarding experience: take a user of
> another distro that uses their favorite Wayland compositor, and wants to
> try out Guix. They install it through the Guix installer, and don't
> understand (yet) how to read the whole documentation and write their own
> config file fully. They add sway to their system packages, reconfigure,
> but next reboot GDM doesn't show Sway in the available sessions; they then
> decide it's not worth their time and go back to their old distro. This
> default change would make sure that it Just Works Out of The Box™ on
> first install.
Yeah, understood. (I think we should have a section in the manual
documenting, with actual examples, how to set up Wayland!)
Surely there’s a geek audience who expects Wayland, and another geek
audience who needs X for their tools; in between, there’s probably a lot
of people who’s fine either way.
I have no objection to defaulting to Wayland, but my gut feeling is that
we have enough on our plate for 1.4 already, so I’d rather delay that
post-release.
WDYT?
Ludo’.
next prev parent reply other threads:[~2022-06-17 15:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 8:35 Release v1.4? zimoun
2022-06-03 16:41 ` Ludovic Courtès
2022-06-05 17:57 ` zimoun
2022-06-05 22:31 ` vidak
2022-06-06 15:39 ` Maxim Cournoyer
2022-06-06 21:17 ` Merging ‘staging’? Ludovic Courtès
2022-06-08 11:50 ` Efraim Flashner
2022-06-08 21:24 ` Ludovic Courtès
2022-06-10 7:57 ` Efraim Flashner
2022-06-11 9:53 ` Ludovic Courtès
2022-06-11 10:49 ` Tom Fitzhenry
2022-06-12 3:58 ` Efraim Flashner
2022-06-12 21:08 ` Ludovic Courtès
2022-06-13 7:03 ` Ludovic Courtès
2022-06-14 4:01 ` Thiago Jung Bauermann
2022-06-14 10:32 ` Release ? (was: Merging ‘staging’?) zimoun
2022-06-14 13:08 ` Efraim Flashner
2022-06-15 9:21 ` Release ? Ludovic Courtès
2022-06-09 17:19 ` Merging ‘staging’? pelzflorian (Florian Pelz)
2022-06-09 17:41 ` Efraim Flashner
2022-06-09 19:02 ` pelzflorian (Florian Pelz)
2022-06-10 6:07 ` pelzflorian (Florian Pelz)
2022-06-11 7:35 ` pelzflorian (Florian Pelz)
2022-07-15 10:52 ` Rock64 segfaults (was: Merging ‘staging’?) Timotej Lazar
2022-06-12 4:54 ` Merging ‘staging’? Thiago Jung Bauermann
2022-06-12 21:06 ` Ludovic Courtès
2022-06-10 15:47 ` Release v1.4? Josselin Poiret
2022-06-15 8:54 ` Ludovic Courtès
2022-06-15 16:51 ` Gábor Boskovits
2022-06-16 8:59 ` Josselin Poiret
2022-06-17 15:31 ` Ludovic Courtès [this message]
2022-06-17 15:37 ` Brian Cully via Development of GNU Guix and the GNU System distribution.
2022-06-19 3:33 ` Further thoughts on Xorg "vs" Wayland etc -- was: " bokr
2022-06-19 18:16 ` Philip McGrath
2022-06-22 13:31 ` Ludovic Courtès
2022-06-28 9:02 ` Efraim Flashner
2022-06-17 15:45 ` Josselin Poiret
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=87bkurfgru.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dev@jpoiret.xyz \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).