first attempt

Nix: configuration.nix
{ config, pkgs, ... }:

{
services.xserver.enable = false; # Wayland only
services.display-manager.enable = false; # optional if using sway-like session launch
users.users.youruser.extraSessionCommands = ''
${pkgs.hyprland}/bin/hyprland --config ${config.home.file."hyprland.conf".source}
'';

environment.systemPackages = with pkgs; [
hyprland
];

# Hyprland config file (example path)
home.file."hyprland.conf".text = ''
# disable Xwayland
xwayland = false
# other hyprland settings...
'';
}

second, with access to the web. better but still, why use uwsm? and i asked for both methods with compilation and without

>!
{ config, pkgs, ... }:

{
programs.hyprland = {
enable = true;
xwayland.enable = false;
# if you use the Hyprland flake package, set package and portalPackage consistently:
# package = inputs.hyprland.packages.${pkgs.stdenv.hostPlatform.system}.hyprland;
# portalPackage = inputs.hyprland.packages.${pkgs.stdenv.hostPlatform.system}.xdg-desktop-portal-hyprland;
withUWSM = true; # recommended
};

# Don't enable X server:
services.xserver.enable = false;
}
!<

both ways to post code in a post was "proposed" by GPT5, and both of them are wrong. Blame him, not my retardation

Currently if you want good code you have to give the model lots of guidance. Imo it's still somewhat helpful but since you have to be in the loop you won't get 10x faster results as some promise. 10x or more you only get if you get lucky and accept slop.

>>108204359
I observed the ability to write better code if i give it access to the documentation by sending the file or link to it. But still, I'm forced to guide it. It's literally same thing as writing by yourself by looking at docs, but for people unable to use keyboard normally.

But it's good at shortening documentation and as fast search, but i find ctrl+f by keywords still better, just because AI can sometime ruin the meaning of the original text.

>>108204236
>I'm doing something wrong
no. Just noticing things. This whole "vibe coding" thing reminds me of the early 90's when Microsoft was pushing Visual Basic and Access. Everybody and their cousin was whipping out simple little apps to do shit, Microsoft was aggressively pushing the line that companies could replace their expensive and slow C/C++ developers and just let ordinary employees write whatever business apps they needed.
And it worked. Kind of. For a while. But importantly, it worked well enough for people to demonstrate that their pain points could be fixed with the right application, and could demonstrate real financial benefits to the company. The problem is that those applications hit their limits very very early, ordinary employees had no idea how to manage complexity (admittedly both Access and VB in their goal for "simplicity" made this especially difficult). Access was a single-user database so you couldn't deploy the application out to all the guys in the company that needed it, Visual Basic hit its complexity limit shortly after the "calculator" phase.
The result was that there was an absolutely huge need for real developers for the next three decades as companies rewrote all those Access and VB applications from scratch in a way that was scalable, supportable, and capable of handling the level of complexity that real Line of Business applications can accrete.

>>108204421
I use it to write small stuff in languages I don't know or haven't used in a while. I wanted a certain IDE plugin for a long time but they are written in Java or Kotlin, so I had Claude do it.

>>108204236
>IT DOES work, but the code is an amazing mix of boilerplate and non canonical practices of doing "things". Again, it is doing it's work, so some retarded manager and hobbyist can make things work with it, but still.
I saw a video talking about this perspective. If you know how code, the Claude is a hand on wheel. Because it will help you so much.

File: vibe-check.jpg (299 KB, 1242x1317)

299 KB JPG

>>108204435
>>108204438
fair enough. I suppose AI will be used the same way Figma is used to convert graphic design to html/css, but for back-end.

>>108204236
For me prompt engineering works fine when I have an absolute clear idea of what I'm trying to accomplish. I also use NixOS for servers and when I want to quickly create a configuration I need to clearly state every single details of the configuration. Compared to coding, where you can explore the idea before writing the actual specifications, a Nix/Ansible/whatever configuration needs to be extremely specific from the very first moment.

If you want to try vibecoding, try to come up with a project idea, plan it carefully on a Markdown file by explaining all the features you would like to have, then list the dependencies (very important, don't let the AI choose them for you) and provide a skills.md file (which will reduce the hallucinations).

>>108204435
Oh and DBase/Foxpro, and on the Mac there was Hypercard, those were also big ones that non-developers used to write applications that were going to put "real" developers out of a job. Lots of developers made bank over the next decade or so rewriting those proof-of-concepts.