You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Choosenim should be able to provide the same functionality as it's equivalents in other programming languages, and that would include the ability to download nim from source and build it if necessary. In the least, it should be able to do this for Linux based OSs.
Currently, there is no means by which users can easily manage different versions of Nim that are built from source. This would include keeping up-to-date with the newest version of Nim and patching security vulnerabilities. This inability represents a stumbling block in the way of Nim's acceptance as a mature language for programming, as unless developers are actively involved in the Nim development community, they can easily become unaware of important releases and security fixes. Which means there is the potential for work invested in creating a new program written in Nim to be lost due to it being based off a version of Nim that is deprecated or vulnerable to a security vulnerability.
As long as Nim still possesses difficulties with OpenSSL versions, users will have to compile their own installation of Nim, and as long as they are required to do this, they will lack the ability to easily maintain their version with the newest release.
The text was updated successfully, but these errors were encountered:
Feature Request: Build Nim from Source
Choosenim should be able to provide the same functionality as it's equivalents in other programming languages, and that would include the ability to download nim from source and build it if necessary. In the least, it should be able to do this for Linux based OSs.
Currently, there is no means by which users can easily manage different versions of Nim that are built from source. This would include keeping up-to-date with the newest version of Nim and patching security vulnerabilities. This inability represents a stumbling block in the way of Nim's acceptance as a mature language for programming, as unless developers are actively involved in the Nim development community, they can easily become unaware of important releases and security fixes. Which means there is the potential for work invested in creating a new program written in Nim to be lost due to it being based off a version of Nim that is deprecated or vulnerable to a security vulnerability.
As long as Nim still possesses difficulties with OpenSSL versions, users will have to compile their own installation of Nim, and as long as they are required to do this, they will lack the ability to easily maintain their version with the newest release.
The text was updated successfully, but these errors were encountered: