Okay wow. I looked into your repo and its a really interesting implementation of a DSL. I think I get what the code is trying to do? You run shimky through bash and it turns into python code? meta programming stuff! I think its a regular language? its hard to tell.

So I’ve actually been studying DSLs for a few months and I can recommend some ways for you to improve this code if you want.

Feel like this should be included here. I’m pretty sure I found the original pr. I couldn’t find an associate issue so I’m not sure where the miscommunication about waiting happened.

https://codeberg.org/libreboot/lbmk/pulls/181

I understand the frustration get how annoying it is but I also can see it from leah perspective. Honestly I think this is a misunderstanding and I don’t think anyone is trying to be toxic (at least not initially. The your work was shit comment is rude af)

This may not be what you want to hear but I think you should consider whether all this argument and feeling bad is worth the potential upside. What happened was shitty but you shouldn’t let this ruin your day.

You are running fedora which is using the dnf package manager. The commands you mentioned (apt/ppa) are part of the apt (aptitude) package manager which is comes with Ubuntu.

Apt is the command to install/manage packages on Ubuntu (and other distros that use apt). A ppa is a special way to tell apt where it can download packages from. It lets you a install 3rd party packages not provided by your distros default selection. It is specific to apt and will not work for dnf.

This isn’t the end of the world and you can still install the package. Because these packages are open source, you can build the package from source. The instructions for which can be found on the github readme. Hopefully this cleared some things up!

[Edit] done some poking around, and I managed to get it running on fedora. I had weird issues building it from scratch, so I did it in a janky way by downloading and extracting the deb (it had precompiled bin inside). Looks to be working tho I couldn’t test it because no qemu

This isn’t really guide. More a tool for finding what makes your system look like a VM. pafish is a good tool for detecting vms. It also tells you what gave it away. You can use pafish to find out what is giving you away and fix it.

Bottom is also good.

What’s up with the ux design of nix? I get it’s made for advanced users but still. I’m reading through this guide and man it’s convoluted.

The different ways of installing packages. Either through editing the configuration.nix or running a command. The weird inconsistency of nix commands. nix-env -iA to install and nix-env --uninstall to uninstall. Then updating uses nix-channel --update but upgrade uses nixos-rebuild switch --upgrade. All this to use the package manager. Also haven’t even mentioned flakes or home manager.

It’s a cool OS, but the UX really needs work imo.

[Edit] I do wanna add something else too because I feel like my point isn’t getting across.

It’s okay to have a complicated ui. Especially if your target audience are tech-savvy. But even tech-savvy people have to start as new users. A tech-savvy new user isn’t going to know what the best practices are. Being able to anticipate the steps for installing a package is important for ux. If the commands for installing packages isn’t cohesive/intuitive, then the user has to spend more time looking for guides and learning how to use the software.

People also mentioned a new command in the works. This is great! However, these current commands are being recommended through blogs and nix. New users won’t know about this new command.