[-] x74sys@programming.dev 3 points 3 hours ago* (last edited 2 hours 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 1 day ago* (last edited 1 day 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.

3

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 5 points 1 day ago* (last edited 1 day 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 11 points 1 day ago* (last edited 1 day 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.

[-] x74sys@programming.dev 8 points 2 days ago

I don't really have any problem with the thing by itself, I honestly don't even know that much about it. I just hate everything that gains publicity just because there is a certain name behind it. Which is what happened with omarchy.

Didn't know that it was AI slop as well. That's kinda sad...

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

Yeah, NixOS is definitely a journey. For me personally, a very fun one. You’re kinda experiencing what is was like experiencing linux for the first time. Took me like half a year to get proficient with nix in a way I was productive with it.

That configuring some programs is completely different from how it should be is a weird quirk of home-manager. I personally don’t use it, it adds a lot of complexity for not much benefit.

But for me, nix saved me in terms of linux. I‘m someone who frequently switches around devices or just completely wipes their existing ones (I‘m very messy with file management, and I just need a clean install after a year or two). It was incredibly annoying to use other distros, especially if you are tinkering a lot it can occasionally happen that you brick your install. You kinda had to document all the fixes for certain issues so that you didn‘t forget them. I could think of more things. That’s just specific to me, but Nix solves all those problems. Not sure I‘d be using linux if it wasn’t for NixOS.

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

Yeah, it will definitely not turn out well. But for now I‘m pleased with their products & services, especially Denon DJ stuff is miles ahead of what Pioneer does. Can’t say much about the rest, but haven’t heard anything bad.

[-] x74sys@programming.dev 3 points 2 days ago

Yeah, honestly if I notice something has AI in it, I don’t use it anymore. Open source projects with a CLAUDE.md or whatever in them? No, thanks.

The amount of assumptions they make are really one big issue what makes them suck so bad. In the end you just have more work. Instead of getting done 80% of the work in 20% of the time, now you get 30% of the work done in 1% of the time, but good luck getting the remaining stuff done at all.

[-] x74sys@programming.dev 3 points 2 days ago

Yeah, at most you can let them manage a 1k loc python script (the free tiers or Gemini Pro at least), but more than that and it starts to really eat your tokens without achieving what you asked or breaking functional behavior.

I extremely doubt that Coding Agents will see a future like promised. LLMs are still so expensive to run, and the useful larger models will probably never be affordable (if they charged for them what they cost). Apart from the fact that even their output can be utter garbage (and mediocre at best). You can already see it everywhere. Websites break in weird ways, ways in which it’s clear that either a complete beginner wrote that or an LLM did. Look at Shazam a few weeks ago. UI design? Horrific. Extremely inconsistent. Ugly. There are many other examples. It just shows that it doesn’t work. And no, the next model will not solve those issues. LLMs are flawed for this task from the ground up, the approach is outright wrong, we can make up so many bandaids and they will still suck, forever.

x74sys

0 post score
0 comment score
joined 4 days ago