![]() Setxkbmap shouldn't be used, still that's one example I am getting off the top of my head.Īlso, I didn't find any noticeable performance difference, so not felt like a compelling advancement. Firefox also misbehaved like showing the address bar drop down on second display. Eg, setxkbmap/something similar in terminal doesn't work in Firefox or Chrome because they run on XWayland and not Wayland. I had some issues using X11 applications. If you want to just work, have sensible defaults, no useless tinkering, and good UI, GNOME. TLDR: If you want to learn, customize, try i3. I had been frustrated by the PDF viewer on KDE which had weird way of text selection. Just one (or sometimes two) sensible default applications, which work, are mature, and have decent features. One sensible way to do things: There isn't multiple file managers, no multiple music players.FreeDesktop has good standards, but they need to be implemented with user in mind, not developer. Same with image viewer, which is not EOG, or Gwenview, it's Image Viewer. It won't show you Nautilus right in the application menu, but rather Files. Application names: One great thing I like about GNOME is sensible application names.However, they are doing great work to make one of the best OS of all time. For me, Dropbox system tray didn't work well on Pantheon. The apps there need to stabilize and move to Vala/Granite. Elementary/Pantheon looks even better, but has to pass the test of time and gain stability. UI: GNOME looks good enough to use without random customizations.Other appear to have geek first approach (although I am one). GNOME for me strikes the balance between good user experience and good developer experience. UX: Due to the maturity of GTK ecosystem and backing by corporate (RedHat and recently Canonical), the resulting product has a good user experience compared to KDE/XFCE/i3.Although I am a terminal guy, spending all time inside Terminal (except web browser), I don't like to hunt for plugins for extracting certain archive types, or use Evince on KDE. The experience was more or less the same on most distros I used - Debian, Ubuntu, Fedora, Arch. It just works, with sensible defaults and no botheration. I want to focus on my work, rather than tweaking and customizing every tiny bell and whistle. Sensible defaults: I have almost given up on customizing my OS for a while.By cohesiveness, I mean the array of applications - file manager, image viewer, PDF viewer, music player, system monitor, settings available and how well they work with each other without appearing as independent units plugged. ![]() KDE is working in that direction and have stabilized a lot in their ecosystem, still I feel they have a long way to go. Cohesiveness: GNOME appears to me like a one-cohesive system, while KDE appears like a loosely-coupled system struggling to work together.Maturity : GNOME is mature, stable and just works without bothering.Here are my reasons to prefer GNOME above alternatives: This one hasn't changed for about more than a year, unlike other experiences which changed in a few months. In my perspective after using almost all distros and DEs, I finally stabilized on Arch + GNOME (Manjaro GNOME - it's greenish theme + Arc dark - wayland + X11). ![]() How you can say development has "pretty much ceased" is beyond me. Lastly, I see developers of KWin and other well known compositors actively talking to sway/wlroots developers, sharing details about how they've implemented specific protocols. Proposals are actively submitted by developers in the sway/wlroots/etc ecosystem. There are about half a dozen other compositors actively porting to wlroots.įrom what I understand, the Wayland project itself just creates and reviews protocol proposals (for things like screenshots and video capture), and updates Weston which is their reference implementation. The people at Purism are building a Linux phone which uses Wayland and wlroots. sway was then ported to it and is still being developed at a breakneck pace. Earlier this year the core developers on sway (a Wayland compositor) crowdsourced funds, used it to hold a two week hackathon and built a library called wlroots which helps developers create Wayland compositors. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |