-
-
Notifications
You must be signed in to change notification settings - Fork 89
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
Decision: Plain Bash or POSIX compliance? #88
Comments
I agree for all the same reasons |
Same decision to make for bats: bats-core/bats-core#28 |
When creating example exercises, should we allow use of extra commands that are not necessarily a part of bash? Of course, the student should ultimately be able to solve an exercise however they want, but some exercises become a lot more difficult without extra commands. i.e. |
I think we don't necessarily need to enforce POSIX compliance, as exercism is a learning tool and this might seem to be too complex (or just a bit excessive) for new users. Please correct me if I am mistaken, but just because we don't enforce POSIX compliance doesn't mean that users cannot submit this kind of solution? In this case, we could add a small blurb about POSIX at the end of READMEs as a stretch goal or reminder? |
I like the POSIX stretch goal idea. |
Looks like we have a decision and we can act on it :D.
For the stretch goal that could be a good start for a discussion when users submit their solutions. |
It might be a good idea to have the discussion about this in this separate issue.
As @kenden stated here: #4 (comment), we need to decide what are the requirements for this track.
I agree to that, we should just teach plain Bash with no extra requirements or POSIX compliance in the code or in the tests.
Learning bash is difficult and for most of the users (especially the targeted users for exercism v2), and the majority of the use cases for bash is to create scripts to aid in development, which means the environment is similar or at least known.
What do you think?
The text was updated successfully, but these errors were encountered: