• 5 Posts
  • 176 Comments
Joined 2 years ago
cake
Cake day: July 6th, 2023

help-circle










  • BB_C@programming.devtoRust@programming.devTypst 0.13 released
    link
    fedilink
    arrow-up
    4
    arrow-down
    2
    ·
    28 days ago

    While you missed the mark here since typst has all the important stuff open (I wouldn’t use the web interface even if it was free/open source), I appreciate that you’re keeping an eye open.

    If you were in r*ddit’s rust community a few years ago, you probably would have been banned, just like me😄

    A blog post from M$ mentioning Rust with zero code

    => straight to the top

    A news article regurgitating the same thing a week later

    => straight to the top

    Another news article two weeks later regurgitating the same thing, possibly with the addition of a random tweet from some M$ dev

    => straight to the top

    Anyone not sucking nu-M$'s ****

    => banished to the bottom, or worse.

    Things got so silly to the point where I made this jerk post (archive link) about one of these silly posts.


  • I wouldn’t correct you if this was a general community where the internet gantry hangs in numbers like the multiple !linux communities, but let’s keep things more factual here in !rust.

    After Wedson quit months ago, no one from the Rust-For-Linux effort has quit/resigned/whatever. No one quit who is relevant to current mainline kernel development in general, either.

    There is a difference between the actual Rust-For-Linux team, and Rust proponents who may write kernel code out-of-tree, or may happen to still be listed as maintainers in a dead poor GPU driver. Confusing the two is good for drama, but let’s not do that here.

    And the bad boy maintainer is entitled to his opinion (which I disagree with of course). An opinion which will always be more informed and relevant than 99.999% of whatever the internet gantry has been contributing.






  • Is there a tiling Wayland compositor out there that supports applying custom shaders to windows (similar to picom)? This has been a known limitation for many years. And I brought it up myself with a couple of compositors’ developers, and they told me that it would break direct scan-out, and I told them that I would be fine with that, and then discussions fizzled out.

    I also tried an x11vnc alternative I don’t remember the name of, and besides the generally buggy experience, it completely broke when power management kicked on the sever side (turning off the monitor IIRC). So that’s another show stopper, although maybe not as relevant as custom shader support which I need for applying my custom color inversion shaders to specific windows, otherwise, my vision would go bad quickly.

    So yeah, I will be sticking with my Awesome WM (+picom +x11vnc) setup for a while too.