Update stage1 with basic review #7
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
unode
reviewed
Feb 7, 2023
| > Any programming language (and its ecosystem) has its own strong points and weaknesses. Most of the time any programming language can be used. You should choose the one you are comfortable with. | ||
| > But sometimes you do not have choice, because either you only know a single programming language, or you are aiming to use specialised hardware, and / or the existing libraries which will cut down the needed development time are tied to one or another language. | ||
| > In some cases, it is the target ecosystem the determining point. Software communities like bioconductor, machine learning, bioconda or text mining, for instance, only provides feedback on their favoured programming languages. | ||
| > First of all, if you only have experience with a single programming language, then the decision regarding the software code language to be used in the project is almost taken. |
There was a problem hiding this comment.
I'm not fully on board with this statement. It implies that the reader's knowledge is static and learning another programming language isn't a valid option. Some projects start with the intent of exploring the advantages of a new language or ecosystem. I would emphasize the ecosystem and community advantages of each language along with performance and time-to-code considerations.
unode
reviewed
Feb 7, 2023
| > In some cases, it is the target ecosystem the determining point. Software communities like bioconductor, machine learning, bioconda or text mining, for instance, only provides feedback on their favoured programming languages. | ||
| > First of all, if you only have experience with a single programming language, then the decision regarding the software code language to be used in the project is almost taken. | ||
| > Any programming language (and its ecosystem) has its own strong points and weaknesses. In most cases, any programming language can be used. You should choose the one you are comfortable with. | ||
| > However, sometimes you do not have choice, because either you only know a single programming language, or you are aiming to use specialised hardware, and / or the existing libraries which will reduce the required development time are tied to one or another language. |
There was a problem hiding this comment.
Tempted to propose that we leave "reader's knowledge" out. If I only knew COBOL or ASSEMBLY more weight should be given to other factors. Code portability, code maintenance, readability, ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contains suggested changes for
stage1_inception.md. The changes are mostly recommendations, so feel free to accept or remove any of them :)