Decision: Plain Bash or POSIX compliance? about bash HOT 6 CLOSED

I agree for all the same reasons

from bash.

Looks like we have a decision and we can act on it :D.

• Don't enforce POSIX compliance for our internal code, or code submitted as the solution and we allow users to use any utilities as long as the test passes on their system.
• Have POSIX compliance as a stretch goal

For the stretch goal that could be a good start for a discussion when users submit their solutions.

from bash.

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?

from bash.

I like the POSIX stretch goal idea.

from bash.

Same decision to make for bats: bats-core/bats-core#28

from bash.

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. gigaseconds usage of the date command

from bash.