x74sys

joined 1 week ago
[–] x74sys@programming.dev 3 points 4 hours ago* (last edited 4 hours ago) (1 children)

Try to optimize this away, sucker:

echo "level full-speed" | sudo tee /proc/acpi/ibm/fan
[–] x74sys@programming.dev 15 points 17 hours ago (4 children)

Luckily I have a ThinkPad, I just run the following program and hold the fan vents against my face:

int main(void) {
  while (1);
}
[–] x74sys@programming.dev 23 points 1 day ago (1 children)

GNU is a trusted quality stamp. Me see GNU, me go GET.

[–] x74sys@programming.dev 5 points 2 days ago* (last edited 2 days 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.

[–] x74sys@programming.dev 7 points 2 days ago* (last edited 2 days ago) (1 children)

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).

[–] x74sys@programming.dev 1 points 2 days ago

Also using something like that takes all the fun out of configuring it yourself.

[–] x74sys@programming.dev 1 points 2 days ago

That’s some really good music. Apart from the theme.

[–] x74sys@programming.dev 3 points 4 days ago* (last edited 4 days ago)

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.

[–] x74sys@programming.dev 1 points 5 days ago* (last edited 5 days ago)

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.

 

Hey guys, I have a project which I want to cross-compile to windows (because I don't want to install windows on my machine, nor do I plan on developing on windows) and eventually MacOS.

All I really need is to know that it will compile for & run on windows.

This is what I tried, but I'm not sure what the best approach is here. Searching online didn't yield any conclusive results either.

{
  description = "cross-compile dev env";

  inputs = {
    nixpkgs.url = "github:NixOS/nixpkgs/nixpkgs-unstable";
  };

  outputs = { nixpkgs, ... }:
    let
      supportedSystems = ["x86_64-linux"];
      eachSystem = fn: nixpkgs.lib.genAttrs supportedSystems (system:
        fn nixpkgs.legacyPackages.${system}
      );
    in
    {
      #1 this is what I tried at first,
      # but it created conflicts in the environment (obviously)
      devShells = eachSystem (pkgs: {
        default = pkgs.mkShell.override { stdenv = pkgs.gcc15.stdenv; } {
          packages = with pkgs; [
            ...
            pkgsCross.mingwW64.buildPackages.gcc15
          ];
        };
      });

      #2 this is probably a better solution?
      devShells = eachSystem (pkgs: let packages = with pkgs; [
        ...
      ]; in {
        default = pkgs.mkShell.override { stdenv = pkgs.gcc15.stdenv; } {
          inherit packages;
        };

        windows = pkgs.pkgsCross.mingwW64.mkShell { 
          inherit packages;
        };
      });
    };
}

The project is just a C program which compiles using a Makefile. I stripped out dependencies etc. from the flake.

[–] x74sys@programming.dev 4 points 6 days ago* (last edited 6 days ago)

Yeah, apart from the fact that I imagine that people who need alt text don’t appreciate LLM output. It‘s very boring. It’s either extremely technical and ice-cold or so cringe that you have to stop reading. Just what I think.

At least for me, if I realize that I’m reading an AI blog article or AI generated text in some other form, I don’t read it.

[–] x74sys@programming.dev 10 points 6 days ago* (last edited 6 days ago)

In my opinion, no. It has to be heavily curated. You’re not saving yourself a lot of work if you have to read it word by word (and probably correct stuff) anyway.

I think just one very short sentence describing what’s on there (it doesn’t have to be detailed) is a lot better than whatever an LLM will give you.

view more: next ›