I see comments in flake.nix file that this file, and the related flake.lock I assume, are there just to be used by Skyler Ross skyler@launchbadge.com`; this can be confusing and misleading. As a dev, I prefer not having useless files on my repo, or assuming I can use Nix because I see the .nix file, and than I discover it's not there for me.
todo-list.txt seems outdated (last update Dec 2022). It's confusing if I should still look at it or not to understand the current SDK features.
Solution
If those files are there for Skyler only, we should remove them. Skyler can keep those files for itself ;)
If those files are needed in some custom dev env, we can add those files to .gitignore, the same we do with .idea or .task
If, on the contrary, those files can be helpful as an optional tool, because they want to use NixOS, I suggest to update them, keep them updated, and remove the comment.
About the todo-list, keep it up to date or remove it to avoid confusion.
Problem
I see comments in flake.nix file that this file, and the related flake.lock I assume, are there just to be used by Skyler Ross skyler@launchbadge.com`; this can be confusing and misleading. As a dev, I prefer not having useless files on my repo, or assuming I can use Nix because I see the .nix file, and than I discover it's not there for me.
todo-list.txt seems outdated (last update Dec 2022). It's confusing if I should still look at it or not to understand the current SDK features.
Solution
If those files are there for Skyler only, we should remove them. Skyler can keep those files for itself ;) If those files are needed in some custom dev env, we can add those files to .gitignore, the same we do with .idea or .task
If, on the contrary, those files can be helpful as an optional tool, because they want to use NixOS, I suggest to update them, keep them updated, and remove the comment.
About the todo-list, keep it up to date or remove it to avoid confusion.
Alternatives
No response