I'm tired of this anti-Wayland horseshit

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • emacs

    Mirror of GNU Emacs (by masm11)

    A pgtk build of emacs is what I have been using for quite some time without any significant problems

    https://github.com/masm11/emacs

    Pretty sure there are builds for the browsers you mentioned that run natively on wayland

  • wlroots

    Discontinued A modular Wayland compositor library

    This was a sway thing more than a Wayland thing and a PR for it was merged back in March https://github.com/swaywm/wlroots/pull/2064

    Also it's (ironically) an X11 related issue which shows up do to XWayland backwards compatibility, not something new with Wayland.

    Chrome also since supports Wayland natively so the workaround in that PR isn't even needed for it anymore. Electron is still a bit behind but it's looking like Electron 12 should have native Wayland support as well, until then the workaround is there.

    There are still a few things I'd like to see land (which are closing in) before saying Wayland is a better fit for most users but better DPI scaling certainly isn't one, it was one of the first wins to land to be honest.

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  • sway

    i3-compatible Wayland compositor

  • obs-studio

    OBS Studio - Free and open source software for live streaming and screen recording

    How does this work? https://github.com/obsproject/obs-studio/pull/2484

    Is it just basically a backdoor going through the hardware?

    Is there some way that a compositor works with Linux security so that you need a special privilege or root or something in order to record the screen?

  • grim

    Discontinued Grab images from a Wayland compositor

  • > Individually, these things are small, but the small impedances these changes introduce does take a toll on people, especially when you're trying to just get stuff done.

    One of the problems is a parity disconnect. A developer/PM often has very different perspective from their users: They see the new changes as they're happening and so they're all small, incremental changes, plus they're closely following development.

    A lot of users only infrequently update and/or infrequently use certain features, and so for them, all these small incremental features add up to be massive change for the sake of change. This will often manifest as "Every time I go to do x, it's totally different and I have to re-learn everything!".

    I find a lot of software -- especially FOSS -- also communicates change poorly. Release notes are the primary way to get across changes, yet there are several bad things people do that make it basically impossible to read:

    * List every change or commit message, especially without categorizing or simplifying the wording

    * Don't properly highlight feature changes (eg with screenshots and/or reasoning)

    * Have dozens of betas/pre-releases, but don't consolidate the release notes into a final "here's what's changed since the last main release" document

    Some examples of exceptionally good release notes: Visual Studio Code [1], Jira [2], Gitlab [3] (though if they only provided their changelog [4] it would be a good example of being overly verbose to the point of unusable).

    [1] https://code.visualstudio.com/updates/v1_52

    [2] https://confluence.atlassian.com/jirasoftware/jira-software-...

    [3] https://about.gitlab.com/releases/categories/releases/

    [4] https://gitlab.com/gitlab-org/gitlab-foss/-/blob/master/CHAN...

  • wayvnc

    A VNC server for wlroots based Wayland compositors

    TeamViewer/AnyDesk/VNC is not "remote windowing", it's "remote access" to a whole desktop. And that's easily available https://github.com/any1/wayvnc

    But actually "remote windowing/apps" is even better supported, it's a universal proxy: https://gitlab.freedesktop.org/mstoeckl/waypipe Absolutely does not require any support from the core protocol.

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  • wl-clipboard

    Command-line copy/paste utilities for Wayland

  • kanshi

    Discontinued Dynamic display configuration (mirror)

    * It's not exactly the same, but I use Kanshi for dynamic output configuration. https://github.com/emersion/kanshi

  • clipman

    Discontinued A simple clipboard manager for Wayland

  • xdg-desktop-portal-wlr

    xdg-desktop-portal backend for wlroots

    For your reference, these are the issues to subscribe to if you're interested in following the discussion as it's taking place:

    https://github.com/emersion/xdg-desktop-portal-wlr/issues/12

    https://github.com/swaywm/wlr-protocols/issues/93

  • ffmpeg-templates

    a video editor without a gui

    This is super off topic, but I also find working with video UIs frustrating for this reason. For my own needs, I have been working on a video editing tool that has a workflow more similar to web dev. E.g. describe changes in text files and render the final video on the command line. https://github.com/andykais/ffmpeg-templates

  • jetson-inference

    Hello AI World guide to deploying deep-learning inference networks and deep vision primitives with TensorRT and NVIDIA Jetson.

    Well, don't get me wrong. I do like my Jetson Nano. For a hobbyist who likes to tinker with machine learning in their spare time it's definitely a product cool and there are quite a few repositories on Github[0, 1] with sample code.

    Unfortunately… that's about it. There is little documentation about

    - how to build a custom OS image (necessary if you're thinking about using Jetson as part of your own product, i.e. a large-scale deployment). What proprietary drivers and libraries do I need to install? Nvidia basically says, here's a Ubuntu image with the usual GUI, complete driver stack and everything – take it or leave it. Unfortunately, the GUI alone is eating up a lot of the precious CPU and GPU resources, so using that OS image is no option.

    - how deployment works on production modules (as opposed to the non-production module in the Developer Kit)

    - what production modules are available in the first place ("Please refer to our partners")

    - what wifi dongles are compatible (the most recent Jetson Nano comes w/o wifi)

    - how to convert your custom models to TensorRT, what you need to pay attention to etc. (The official docs basically say: Have a look at the following nondescript sample code. Good luck.)

    - … (I'm sure I'm forgetting many other things that I've struggled with over the past months)

    Anyway. It's not that this information isn't out there somewhere in some blog post, some Github repo or some thread on the Nvidia forums[2]. (Though I have yet to find a reliably working wifi dongle…) But it usually takes you days orweeks to find it. From a product which is supposed to be industry-grade I would have expected more.

    [0]: https://github.com/dusty-nv/jetson-inference

  • tensorrt_demos

    TensorRT MODNet, YOLOv4, YOLOv3, SSD, MTCNN, and GoogLeNet

  • SaaSHub

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts