[HN Gopher] Wayflan: a from-scratch Wayland client for Common Lisp
       ___________________________________________________________________
        
       Wayflan: a from-scratch Wayland client for Common Lisp
        
       Author : susam
       Score  : 82 points
       Date   : 2022-10-21 15:31 UTC (7 hours ago)
        
 (HTM) web link (sr.ht)
 (TXT) w3m dump (sr.ht)
        
       | v3ss0n wrote:
        
         | Jtsummers wrote:
         | > Seriously, lisp?
         | 
         | Sure, why not? This is a Wayland _client_ , not the server
         | (aka, compositor). But there's little technical reason not to
         | make the compositor in Lisp either, other than the time
         | commitment. If you want Rust clients and compositors, they do
         | exist. If you don't know how to find them, here's one that
         | turned up on Google: http://way-cooler.org/
         | 
         | Some more Rust/Wayland stuff:
         | 
         | https://github.com/Smithay/wayland-rs
        
           | Arnavion wrote:
           | Note that Way Cooler switched from Rust to C in 2018, because
           | the developer felt Rust didn't work for them. It's also been
           | archived since 2019.
           | 
           | (Also even the Rust version was built on top of wlroots, not
           | a Rust implementation of the protocol like wayland-rs is.)
           | 
           | https://way-cooler.org/blog/2020/01/09/way-cooler-post-
           | morte...
        
         | SanderSantema wrote:
         | Are you suggesting this person should've spent their time
         | working on reimplementing wayland in rust instead? If so I
         | suggest you drop all the projects you're currently working on
         | and do the same.
        
         | encryptluks2 wrote:
         | Rust doesn't make programs bug free or safe.
        
       | MattHood0 wrote:
       | Very cool! I like that the author chose socket-based
       | communication over a C FFI, which I assume might lead to better
       | reliability and a cleaner API on the Lisp side. Are there any
       | disadvantages to sockets vs. FFI? Any additional, perceivable
       | latency?
        
         | Jtsummers wrote:
         | https://wayland.freedesktop.org/docs/html/ch04.html#sect-Pro...
         | 
         | Wayland clients already communicate with the compositor via
         | sockets. This is no different, the main thing will be being
         | able to produce a Lisp-centric API rather than directly using
         | the existing libwayland-client or another library's API.
        
       | the_jesus_villa wrote:
       | Honestly, I've always preferred other Lisps (specifically Racket
       | and Clojure). But among desserts, flan has a special place in my
       | heart. I don't let myself indulge these days but thanks to the
       | delectable drawing in this article, I might go get some this
       | evening!
        
       | ssivark wrote:
       | Does this mean we can now have a StumpWM port (or equivalent) for
       | Wayland? Is this already in the works?
        
         | timidger wrote:
         | This is a client library only (at least according to the
         | title). There would need to be an equivalent server library
         | implementation, not to mention all of the necessary non Wayland
         | protocol code (libinput, drm, etc). Still the easiest means to
         | port StumpWM would be to use c bindings for wlroots
        
         | medo-bear wrote:
         | you might find this interesting
         | 
         | https://github.com/stumpwm/mahogany
        
           | podiki wrote:
           | Yes, let's get some work on this and then I can finally move
           | to Wayland!
        
             | headhasthoughts wrote:
             | It's open source. Have you contributed?
        
       ___________________________________________________________________
       (page generated 2022-10-21 23:00 UTC)