true

also the fact that I can now share my project and the other person just has to run "nix develop .#", wait for everything to download and afterwards start programming is really nice

* upadte process....

the first setup was the worst experience I had in a while lol

i have not tried this myself, but I think it should work perfactly fine.
i mean even home-manager often exposes a "package" option, to specify the package to use

yeah I think the storage problem with NixOS is quite real...
it is a trade-of and I think I am willing to take it, because:
a) I like writing & tinkering with my config
b) I like the feeling when you setup a machine and all the software is "just there"

i see it somewhat "as a feature" to update everything at once, so I don't forget to update specific things...

and if I really need a specific version for a package, I can just pull in a second nixpkgs and use that can't I?

it is http: right? without the // but with the : and I dont know why

I hope it is both "" or "/" (would go with "/" based on vibes)

Once a changed a DB column in my Backend. Typescript showed me all the places where I now had to use a different key to access said value and the migration went seemless, afterwards everything worked as expected...
So for me, typescript is a win

Concerning the "bothersomenes" of type checking when it works, I think we both are writing different typescript.

In my code bases, most of the time types are inferred everywhere, so I don't actually write any typescript and get the safety for free.

The type conversion is often a problem, I would agree on that point, even dough I think with triple equal signs and typescript in your codebase it becomes less of a problem (typescript will tell you if you try to check equality of variables of different types and so on).

no problem,
i wanted to take I look but had trouble finding it on github xD

could it be, that the clone link is wrong?
(because it points at github but the project is hosted on codeberg)

thats super cool!

tbh i like both...
I feel like my typescript checks are strong enough so i don't get runtime type errors

and literal string types are so nice to work with in some cases...
e.g. I am using a typesafe router (Tanstack Router) in React, and this is only possible due to string literals

I think you could also. good to feeds > discover > unpin and it would be gone

(but rubix cube is also a nice idea /lh)

restarting the Dev server often helps in such cases

additionally I love the update process... because you execute two commands (update flake input and rebuild system) and all your packages are updated at once...

it does not happen, that you accidentally stay on an old version of one package... nor do you have 10 places to update apps