-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Categories #3
Comments
Yes, I agree.... The category list is important as it will drive future development in this repo. It will enable the developer to better understand what types of scripts need to be written as well as "show off" the power of nu from a higher level architectural and design patterns point of view. It may take a few weeks to get a handle on the types of categories we actually want to have as well as come up with a list that makes sense from the current scripts we currently have. This may help us decide as well over time what the standard library should like like. As nu matures maybe eventually some of the current internal commands will actually become scripts... This will probably happen in parallel over the next year as nu matures as a language. But having this repo in place now is a great starting point from which to move forward in this cool endeavor. Thanks to @kubouch and @fdncred for their initial contributions. |
Agreed. Let's start listing some categories. This is what my initial thoughts are, just from my scripts since they are easily categorized.
Add more categories in this thread below and I'll update my bullets above with them. |
we can start with a few and group the ones we have, and then see what other kinds of scripts come |
I added categories with a readme in each. We can change them if we need to. |
I was thinking, it would be a good idea to split the scripts into directories / categories / topics.
The text was updated successfully, but these errors were encountered: