"send a patch via mail" process.
I don't see a problem with it. I don't know what tools you use, but the current process certainly isn't ancient. Even if I use GitHub or something else, I still highly depend on my e-mail to actually know somebody published a patch and if I am supposed to review it. I don't have to use a GUI coupled with shitty UI decisions. E-mails are very simple in their own way and I don't find it ancient or bad.
Yes, I like text more than visual icons. More proof is given by the fact that I used words like cpu, mem, net over the thousands of icons I could've used instead, considering that the font I am using is a Nerd Font patched one.
I use JetBrains Mono font. I am not sure what you meant by font rendering, so if you're interested, you can check my dotfiles.
I experienced this too. That's why I stopped asking them anything after my first query (why my keybindings were not working when defined in another file) and relied on guess work. I also found the community kind of dead, so you don't actually get the answers quicker than the guess work will get you there.
I had to look through the source code of their widgets (like wibox.widget.textclock, awful.titlebar.widget.maximizedbutton) they use in their default config file to have a grasp of what's happening. Looking through others' dotfiles was more pain because it's not supposed to be looked upon by the beginners, so they cram all they know in a few lines and leave you guessing.
You are correct.
The program itself isn't really bigger, what makes the difference is that it won't use the dependencies installed by your native package manager, it will download them, it also will download various runtimes if needed for the program, these runtimes are not really supposed to be ran if you compile the package yourself for your distribution, but if you use Flatpak, it is going to run all these runtimes for the program to work, these runtimes will use more RAM than the native build, if the runtime is not optimised, then it will also contribute to higher use of CPU and everything else in general.
It will differ from program to program, but I'll let you know that I have natively compiled EasyEffects (real-time audio manipulation) and also have tried the Flatpak build. The native version hardly uses more than 5% CPU, and is also lightweight in terms of RAM. But the Flatpak build took significantly more RAM usage and my CPU went 80% whenever I played music with the same preset that I tested on the native build. Flatpak also had to download 700-900 MB worth of internet (no idea how much space it took after installation) for the program to run.
They did the silent treatment on me for a long time.
Hi from feddit.nl 🙌!
her username?
I pretty much only use Bard. Bing Chat is just too fucking slow. I have used Bard for my SQL stuff and other small coding stuff, and it works well & really fast. Bing Chat was rushed, and I doubt Microsoft is ever going to fix the shitty code that their employees wrote to meet the deadline.
I love it too. It's pretty much Gruvbox.