Texture VS dissent

Historically, Reddit has used both UIKit and Texture as layout engines to build out the Reddit app. At the time of its adoption, Texture was used as a way to build screens and have the UI update asynchronously, which mitigated frame rate hitches and optimized scroll performance. However, Texture represented a significantly different paradigm for building UI than UIKit, and prior to RPL, we had components built on both layout engines. Reusing components across these frameworks was difficult, and having to juggle two different mental models for these systems made it difficult from a developer’s perspective. As a result, we opted to deprecate and migrate off of Texture.

On iOS it’s written using a fork of Texture, formerly AsyncDisplayKit. In my experience, Texture outperforms UIKit’s auto layout and rich text widgets significantly.

https://github.com/TextureGroup/Texture

In order to make our engineers' lives easier and gain consistency in our user experience, we needed a declarative abstraction on top of UIKit. We chose UIKit because after experimenting with SwiftUI, Texture, ComponentKit, and other alternatives, UIKit offers us the right combination of features, including:

Ok thanks. I've included a link for everyone else. Texture

Not sure if it still works (or will continue to work) but this might be what you're looking for: https://cancel.fm/ripcord/

I've also had fairly good results using gtkcord4, though it takes it little finagling to get up-and-running: https://github.com/diamondburned/gtkcord4

gtkcord4 is a (very experimental) Discord client for GNOME.

Sadly no, but its more privacy respecting than the regular client for sure. FOSS options include: https://github.com/diamondburned/gtkcord4 https://github.com/uowuo/abaddon https://github.com/terminal-discord/weechat-discord (weechat plugin to use Discord within weechat) https://github.com/evelyneee/accord (seems to be for M1 macs) https://github.com/ArmCord/ArmCord (seems to support AMD64, not just Arm64) https://github.com/khlam/discord-sandboxed (sandboxing for standard discord client) There are others I'm sure. One easier option is to run the Discord code in a newer version of Electron. This still isn't open source, but it provides better security and performance. Arch users can use the AUR package discord_arch_electron, other users can just follow the commands in the PKGBUILD for said package and figure it out. Hope that helps. Keep in mind even if your client is open source, Discord's servers aren't, and while there will be some mitigation of data collected, it'll still be quite a bit.