The Crystal Programming Language • Hacker News Board

Re: The Crystal Programming Language

#111

Post by EpicBlackCrayon » Fri, Sep 02, 2022, 10:54 PM UTC

svnpenn wrote: post #95

beta-ziliani wrote: post #92

Earlier quoted context omitted.

It just requires the build tools. If you use scoop, that entails to: > run `scoop install vs_2022_cpp_build_tools` (from the "required libraries" link in https://crystal-lang.org/install/on_windows/ )

That just installs Visual Studio: https://github.com/neatorobito/scoop-crystal/blob/main/bucke... no thank you.

This specifically installs the Visual C++ Compiler and the Windows headers so that you can get a command prompt with all that in your PATH. It is not a full-fat VS install. The difference is something like 20-30GBs for the full VS install vs 1-2GB for these specific components.

Re: The Crystal Programming Language

#112

Post by svnpenn » Fri, Sep 02, 2022, 11:07 PM UTC

EpicBlackCrayon wrote: post #111

svnpenn wrote: post #95

Earlier quoted context omitted.

That just installs Visual Studio: https://github.com/neatorobito/scoop-crystal/blob/main/bucke... no thank you.

This specifically installs the Visual C++ Compiler and the Windows headers so that you can get a command prompt with all that in your PATH. It is not a full-fat VS install. The difference is something like 20-30GBs for the full VS install vs 1-2GB for these specific components.

Meanwhile, LLVM-MinGW is 108 MB:

https://github.com/mstorsjo/llvm-mingw/releases

Re: The Crystal Programming Language

#113

Post by db65edfc7996 » Sat, Sep 03, 2022, 12:07 AM UTC

bovermyer wrote: post #65

hahaitsfunny wrote: post #17

Earlier quoted context omitted.

You can ditch Nims GC and runtime and bring your own if you want. Of course you'd lose access to most of the stdlib but this is why Nim can be used and is popular for embedded / bare metal. Tmk Crystal still lacks Windows support as well and probably other os's / archs's compared to Nim

Windows support is close. See this issue: https://github.com/crystal-lang/crystal/issues/5430

Windows support has been a target since 2013. That's too long for me to put any credibility in projections on when it will be generally released.

Re: The Crystal Programming Language

#114

Post by npn » Sat, Sep 03, 2022, 4:34 AM UTC

svnpenn wrote: post #112

EpicBlackCrayon wrote: post #111

Earlier quoted context omitted.

This specifically installs the Visual C++ Compiler and the Windows headers so that you can get a command prompt with all that in your PATH. It is not a full-fat VS install. The difference is something like 20-30GBs for the full VS install vs 1-2GB for these specific components.

Meanwhile, LLVM-MinGW is 108 MB: https://github.com/mstorsjo/llvm-mingw/releases

now you are just arguing for the sake of argument. unzip the file and it will expand to a 400MB folder.

Re: The Crystal Programming Language

#115

Post by svnpenn » Sat, Sep 03, 2022, 1:33 PM UTC

npn wrote: post #114

svnpenn wrote: post #112

Earlier quoted context omitted.

Meanwhile, LLVM-MinGW is 108 MB: https://github.com/mstorsjo/llvm-mingw/releases

now you are just arguing for the sake of argument. unzip the file and it will expand to a 400MB folder.

Have you ever installed Visual Studio? I have. Even just the build tools DOWNLOADS 1-2 GB, as other user mentioned, which is still 10 times what you get with other options.

Re: The Crystal Programming Language

#116

Post by nTalle » Wed, Sep 07, 2022, 9:16 AM UTC

I used Crystal every day for 2 years. It is for me one of the best languages. Fun and powerful but there are some big problems, I switched to Elixir.

Among the problems :

- A too long compilation. For 2 projects, the compilation in dev env takes more than 30 seconds for each compil, the developer experience is dead at this cadence.

- IDE integration: auto-completion, go to def, API docs, etc works when it wants (almost never).

- The community is too small which results in a lack of docs, examples, help. I spent days searching in Github projects, just to see examples of basic things.

- Instead of focusing on a main framework that makes everyone agree, everyone makes their own framework, their own libs (including me). The result is a lot of time and energy spent on duplicate packages and frameworks that are not necessarily maintained.

I continue to follow the evolution from afar, one day it may be possible to integrate Crystal in WASM, acceptable compile times, maybe a productive main framework :)