3 ms·

The release is happening today, so I posted a bit early. Some parts, like the binaries, are not online yet. There are tutorials for newcomers: http://nim-lang.

by def- 12y ago

The release is happening today, so I posted a bit early. Some parts, like the binaries, are not online yet. There are tutorials for newcomers: http://nim-lang.org/tut1.html http://nim-lang.org/tut1.html https://nim-by-example.github.io/ https://nim-by-example.github.io/ Edit: Fixed tutorial link

gfasdgsfd 12y ago
I'd like to clarify that http://nimbuild.nim-lang.org/tut1.html http://nimbuild.nim-lang.org/tut1.html is for the devel branch. You probably want to use http://nim-lang.org/tut1.html http://nim-lang.org/tut1.html if you're going to use the newly released version.
commentzorro 12y ago
First, congratulations on the new version. Been playing since 0.9.2 and I hope to try this latest version too. But, please make a zipped portable version available for Windows. You don't have to include a binary version of Nim (although that would be nice) but do put the required MinGW pieces off a subdirectory under Nim as was done with earlier releases. This allows unzipping to a thumb drive, xcopy installs, and using Nim anywhere without having to permanently install on specific systems. Also, it makes things really easy for a quick demo when showing someone else Nim on their machine. (FWIW: The sad state of Windows is that almost every installer out there, MinGW included, means crapping in your system to some extent and never knowing what went on nor being able to removed all traces of what was installed. With each installed application you have to make a conscious decision whether it's worth the unpredictable OS pollution to install the application on a particular machine ... because you know with each install that your headed to that inevitable last one where you have to wipe the entire OS and start over.)
- gfasdgsfd 12y ago
  It looks like mingw provides a non-installer version of the binaries, although it is (unintentionally) well hidden in the web. http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.2/threads-posix/seh/x86_64-4.9.2-release-posix-seh-rt_v3-rev1.7z/download http://sourceforge.net/projects/mingw-w64/files/Toolchains%2...
  - commentzorro 12y ago
    I see that, thanks. It's a zipped dump of all pieces for all OSes. If you're a Nim dev, please don't let this dissuade you from eventually releasing a portable "ready to go" version of Nim for Windows. I know myself and my compatriots bail at any language that forces Cygwin or MinGW and has its own installer on top of that. I'll never get to try OCaml, Haskell, Kitten [which looks really interesting but relies on Haskell], and a number of other new languages just because of the install burden. IMO, if trial and adoption are your goals then as little friction as possible to get to "hello world" is a good route. (And an unzip to the directory of your choice then a double click on "Test_Hello_World.bat" are about as good as you could get.)
    - vosper 12y ago
      It's not the same thing at all, but could you use Virtualbox to run a Linux VM on Windows, and play around with languages in that?
- vram22 12y ago
  >(FWIW: The sad state of Windows is that almost every installer out there, MinGW included, means crapping in your system to some extent and never knowing what went on nor being able to removed all traces of what was installed. With each installed application you have to make a conscious decision whether it's worth the unpredictable OS pollution to install the application on a particular machine ... because you know with each install that your headed to that inevitable last one where you have to wipe the entire OS and start over.) This is a huge point, and a huge downside about Windows, even in recent versions. E.g. some time ago I installed some utility EXE and suddenly my Skype stopped working - in a really weird way - the UI itself changed, IIRC it did not show the login screen, though it did start the app. But could not use it since I had no way to log in. Had to roll back to a previous system save point or some such to undo the damage. The Windows registry (being a single point of failure [1], plus not getting cleaned out or updated completely (i.e. not all the registry keys getting updated) on installs/uninstalls due to buggy (un)installers), and DLL hell [2] are major causes for this. [1] http://en.wikipedia.org/wiki/Single_point_of_failure http://en.wikipedia.org/wiki/Single_point_of_failure [2] http://en.wikipedia.org/wiki/DLL_Hell http://en.wikipedia.org/wiki/DLL_Hell

by def- 12y ago

gfasdgsfd 12y ago

I'd like to clarify that http://nimbuild.nim-lang.org/tut1.html http://nimbuild.nim-lang.org/tut1.html is for the devel branch. You probably want to use http://nim-lang.org/tut1.html http://nim-lang.org/tut1.html if you're going to use the newly released version.

commentzorro 12y ago

First, congratulations on the new version. Been playing since 0.9.2 and I hope to try this latest version too. But, please make a zipped portable version available for Windows. You don't have to include a binary version of Nim (although that would be nice) but do put the required MinGW pieces off a subdirectory under Nim as was done with earlier releases. This allows unzipping to a thumb drive, xcopy installs, and using Nim anywhere without having to permanently install on specific systems. Also, it makes things really easy for a quick demo when showing someone else Nim on their machine. (FWIW: The sad state of Windows is that almost every installer out there, MinGW included, means crapping in your system to some extent and never knowing what went on nor being able to removed all traces of what was installed. With each installed application you have to make a conscious decision whether it's worth the unpredictable OS pollution to install the application on a particular machine ... because you know with each install that your headed to that inevitable last one where you have to wipe the entire OS and start over.)

gfasdgsfd 12y ago
It looks like mingw provides a non-installer version of the binaries, although it is (unintentionally) well hidden in the web. http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.2/threads-posix/seh/x86_64-4.9.2-release-posix-seh-rt_v3-rev1.7z/download http://sourceforge.net/projects/mingw-w64/files/Toolchains%2...
- commentzorro 12y ago
  I see that, thanks. It's a zipped dump of all pieces for all OSes. If you're a Nim dev, please don't let this dissuade you from eventually releasing a portable "ready to go" version of Nim for Windows. I know myself and my compatriots bail at any language that forces Cygwin or MinGW and has its own installer on top of that. I'll never get to try OCaml, Haskell, Kitten [which looks really interesting but relies on Haskell], and a number of other new languages just because of the install burden. IMO, if trial and adoption are your goals then as little friction as possible to get to "hello world" is a good route. (And an unzip to the directory of your choice then a double click on "Test_Hello_World.bat" are about as good as you could get.)
  - vosper 12y ago
    It's not the same thing at all, but could you use Virtualbox to run a Linux VM on Windows, and play around with languages in that?
vram22 12y ago
>(FWIW: The sad state of Windows is that almost every installer out there, MinGW included, means crapping in your system to some extent and never knowing what went on nor being able to removed all traces of what was installed. With each installed application you have to make a conscious decision whether it's worth the unpredictable OS pollution to install the application on a particular machine ... because you know with each install that your headed to that inevitable last one where you have to wipe the entire OS and start over.) This is a huge point, and a huge downside about Windows, even in recent versions. E.g. some time ago I installed some utility EXE and suddenly my Skype stopped working - in a really weird way - the UI itself changed, IIRC it did not show the login screen, though it did start the app. But could not use it since I had no way to log in. Had to roll back to a previous system save point or some such to undo the damage. The Windows registry (being a single point of failure [1], plus not getting cleaned out or updated completely (i.e. not all the registry keys getting updated) on installs/uninstalls due to buggy (un)installers), and DLL hell [2] are major causes for this. [1] http://en.wikipedia.org/wiki/Single_point_of_failure http://en.wikipedia.org/wiki/Single_point_of_failure [2] http://en.wikipedia.org/wiki/DLL_Hell http://en.wikipedia.org/wiki/DLL_Hell