News for hackers. Stuff that matters.
Re:Crystal in Production: Diploid by dingdingdang on Saturday October 28, 2017 @12:42PM (#15575679)
Yep, proper Windows support is a must for easy to use dev setup - Go is OK'ish in this sense but Crystal is currently really difficult to get running (either vm or Win10 Linux sub-system or Cygwin hack needed!)
Re:Crystal in Production: Diploid by vram22 on Saturday October 28, 2017 @04:10PM (#15576572)
Thanks. Still wondering what the reason is though - but based on what you said, it seems like POSIX-like APIs being needed may be the reason. Maybe for the concurrency features or other language / library features of Crystal. But then again, Go has concurrency features but works on Windows, and of course Windows has threads anyway, which are usable from C/C++ and other languages.
Re:Crystal in Production: Diploid by faaq on Saturday October 28, 2017 @07:39PM (#15577257)
Here is an installer waiting for Crystal support on Windows https://github.com/faustinoaq/crystal-windows-installer :)
Re:Crystal in Production: Diploid by vram22 on Sunday October 29, 2017 @10:59AM (#15579542)
Thanks.
Re:Crystal in Production: Diploid by RX14 on Saturday October 28, 2017 @04:33PM (#15576655)
It's simply a lack of manpower to port to the windows APIs. There's a partial windows port, but it needs a lot of work before it's merged into master.
Re:Crystal in Production: Diploid by acangiano on Saturday October 28, 2017 @04:31PM (#15576649)
BTW, with a bit of fidgeting, it's possible to get Visual Studio Code for Windows to use Crystal for WSL quite nicely. On the other hand, Crystal in a VM is faster.
Re:Crystal in Production: Diploid by faaq on Saturday October 28, 2017 @07:39PM (#15577256)
Re:Crystal in Production: Diploid by acangiano on Sunday October 29, 2017 @01:15AM (#15578048)
I had to change a few more settings to get it to work properly. I should blog about it at some point.