I just fought them off in my apartment. Everything they said is correct. I just want to add that I bought some kind of spray to kill them and it was very effective. Got rid of them in two applications.
I just fought them off in my apartment. Everything they said is correct. I just want to add that I bought some kind of spray to kill them and it was very effective. Got rid of them in two applications.
Yes. No to the Reddit’s size though.
Right, I forgot that autistic people are not allowed to post about things that annoy them in a community about annoying things. Noted.
Commenting mostly to make this post more active because I have very high hopes for COSMIC and really want it to succeed!
I have very bad memories with this dish. I hated it as a kid and was sometimes forced to eat it. 🤮
Do you mean that it’s worse on GrapheneOS in comparison to stock?
While it’s not nearly as customizable as an Ubuntu kernel, it’s still easy to make your GrapheneOS look and feel exactly how you want it to, within reason.
WTF is it supposed to mean?
Well, I actually enjoy code review, and I enjoy it on both ends. I learned A LOT thanks to insightful review by my teammates. And I like to pass that knowledge on to juniors when reviewing their code.
I want a good tiling DE solution so much. I really hope COSMIC will fill in that gap.
I guess the fact that it can kill you easily is not enough to call it a suicide cable lmao
I recommend checking out satty as well.
I really liked it but unfortunately I was not able to get it to work on Wayland (with Hyprland) at all.
Haha, no worries! There’s definitely some truth in this.
I got recently diagnosed with autism and r/autism is the reason I started using Reddit again after more than a year. I would prefer using Lemmy for this but there’s barely any activity in autism community on Lemmy. Yeah, I know, I should be the change I want to see. I promise I will try to post something there!
Exactly this! Powerful tiling without the need to build your own DE from scratch sounds incredible!
Right, in the simplest case it’s a single option declaration and a single lib.mkIf
. I was probably overthinking the complexity. I will probably go with this approach.
Thanks for the answer and happy nixing!
I’m currently learning NixOS myself and was wondering about the same thing. I’m definitely leaning towards namespacing but I would like to hear an expert’s opinion.
Also, just a question. Are you planning to expose all your configuration modules via custom options? When I’m looking at other people’s configs I feel like the most popular approach is to enable modules just by importing them. I really like the idea of having custom options for everything but it’s additional work and complexity and I can’t decide if it’s worth the effort.
True. This is one of the reasons why I only help people with their computers using remote desktop now. I’m so done with doing this verbally over the phone.
I think vast majority of my friends wouldn’t be able to tell the difference between “browser”, “search engine” and just “Google”. Yes, it seems weird but TBH does it really matter? They can use internet just fine.
Declarative configuration fixes this problem. You don’t really have to write down how to setup something because the configuration is the description.
I use NixOS so in my case all the stuff you described would be defined in a Nix code in a separate Calibre module. I can enable and disable such module at will with a single option in my main config file.
I really recommend looking into immutable, declarative systems. I think NixOS is the most complete solution but there are some other too. I have no experience with them though.