1. 26
  1. 6

    I’m glad to see this option because I’m interested in declarative UIs in general.

    On the other hand, a top problem with UIs (in Rust and elsewhere) is lack of accessibility. Getting a11y right is a difficult and time-consuming task, so it is understandable that new / experimental UIs are not able to prioritize a11y, but it makes actually using any of these UI frameworks for production software ethically questionable.

    I suspect the Rust community in the near future would be better served by pouring effort into making one or two UI libraries accessible (perhaps druid, which is also declarative ui?) rather than making more and more UI libraries that exclude people. That said, if a shared accessibility approach like accesskit is able to make many different UI libraries accessible, that would be a very pleasant outcome, allowing more diversity in UIs while including people who rely on a11y.

    1. 2

      Hi! Author here. I would suggest you contribute to access kit (or similar) so I’d have something mature to use. cheers!

      1. 5

        Forgive me if I misinterpret your brief and casual comment, but this seems like an example of a toxic habit in the open source community: responding to criticism with “well, why don’t you fix it?”

        I understand the impulse, and it’s not inherently bad. If framed well, invitations to contribute and improve software can be empowering. Among the strengths of FOSS are:

        • the ability to study how a program works. This includes seeing where a11y concerns arise, and where they could be addressed.
        • the ability to add fixes yourself. In a friendly community-oriented project, those fixes can easily be contributed upstream. Even given a hostile, uncooperative upstream, the community can exercise the right to fork and maintain their own fixes elsewhere.

        This means that people who are interested in an issue like a11y can learn to program in a practical fashion, even if in a limited way just to “scratch their itch”, and make the software work for them. This sort of agency is impossible in the world of proprietary software, where you have no choice but to lobby the software company and hope they think helping you is profitable.

        Unfortunately, such recommendations to write code yourself are often framed poorly, in an off-putting fashion that sounds more like “I do not care about your concerns and I am uninterested in welcoming you to the community.” Rather than reading like an invitation to make the world better for all, it reads like gatekeeping (if you can’t code, your opinion doesn’t matter) and dismissal.

        This is especially damning in the context of accessibility, where sometimes participating in something like software development is physically impossible, because the tools necessary for collaboration do not take accessibility needs into account.

        Right now, tools developed using your UI library would contribute to that problem.

        1. 3

          Hey, I’d love to do accessibility. The is just a really early version of this library. There’s also no internationalization yet. It’s totally an experimental proof-of-concept, and got more attention than I expected.

          1. 2

            Wait - you hijacked OPs post to talk about your agenda for accessibility, and they are the toxic one? Accessibility is a good thing. But your comment had absolutely nothing to do with their post. You were talking about accessibility in general, and guilt tripped a person trying something out in a new project.

            They are right. If this is something that you are so passionate about, go ahead and fix the problem. Don’t put down other people’s work.

            1. 1

              If this project had been posted without a software license, someone might have commented about repos lacking licenses being a general problem on GitHub. Would this have nothing to do with the project?

              1. 1

                Strawman argument, because that’s not what you did here. You didn’t reference the posted project in any way.

                Remember, it’s easy to criticize. Your comments are low-effort. If you want to improve accessibility, it’s not a very good strategy to criticize tiny proof of concept libraries. A better strategy would be to devote time, and most importantly code, towards your goal.

      2. 2

        Discord server is here: https://discord.gg/JCVVBU3sCN

        1. 2

          Apologies if this isn’t a good fit, this is my first post (not comment) on lobste.rs, and I simply thought this was a very interesting project.

          1. 3

            Hey Absolucy, I think it fits :) You might want update your post that you are the author of the project. You can do that when submitting the post by checking the corresponding box. I‘m not exactly sure but I think you can also do it when editing the post :)

            1. 2

              I’m not the author, just a big fan of SwiftUI-style UI libraries.

              1. 2

                Haha my bad… I somehow misread the Github name on your Lobsters profile…