GNU is a trusted quality stamp. Me see GNU, me go GET.
x74sys
joined 2 months ago
And I want to add: even though LLMs can identify cybersecurity risks, it doesn’t mean they are good at cybersecurity. They’re probably just as bad as in any other area. Also questionable if the actual positives outweigh the labor required to flag all the false-positives.
Just because they‘re used everywhere doesn’t mean that we just have to accept them. Also doesn’t mean that LLMs are a good thing.
I think LLMs can be used as an (additional!) cyber security analysis tool, that’s honestly the only area in which it seems to be actually useful (right now). And most projects don’t reach the size in which spotting security risks spanning across many different modules is a relevant skill to have. So it should be used sparingly, on things like the linux kernel. Then the cost of it might even be worth it (but I also don’t want to know about the amount of hallucinated bugs it finds).
Honestly I don’t really understand what’s wrong about calling them that, I do prefer calling them compositors as well, but to the untrained eye window manager is much more clear, and it’s the existential goal of a compositor anyway (in most cases at least). Just because a spec sheet doesn’t call a game engine a 3D renderer doesn’t mean a game engine is not a 3D renderer, because unless it only renders 2D, it is also a 3D renderer, if you get what I mean.
Though you could argue that a compositor without a window manager is useless, thus a compositor implies the presence of a window manager.
Sway and River both use wm as part of their URL: swaywm (see https://swaywm.org/) and riverwm (see https://github.com/riverwm). Calling them only one or the other is wrong, they’re both compositors & window managers.
Also using something like that takes all the fun out of configuring it yourself.
That’s some really good music. Apart from the theme.
No, I don’t configure using nix, but partially because I don’t use home-manager. So I just write in the native config language.
The other reason is that I don’t believe configuring everything in nix is sustainable. You’re adding another layer that needs to be maintained by someone, and there isn’t much benefit. The native config is as much part of my configuration as a pure nix configuration would be.
And it doesn’t really matter whether it’s dedicated files or just inline in a nix module. I decide based on complexity. My neovim config is spread out over many files, but all other configs are inline.
Adwaita
My goal is to cross-compile from nix to windows. I need to have this program running on windows (or at least provide binaries for it haha), but I really don't want to dual-boot again (I just got rid of windows a couple of months ago, and I'm not too keen on looking at it again in the near future). Maybe I phrased my question the wrong way.
So I don't need the environment to run on windows, it just needs to be able to compile for windows.
Rust made the same mistake that C++ made, otherwise it might've been a viable option. Now instead debugging a memory issue for 3 days, I think a month on how to architect my software, just to scrap that 5 months later and rewrite it from scratch.