Earlier quoted context omitted.
What about Go? It seems like their approach is that if they define the style guide and build it into tooling, your code style (for Go) can only be the 'approved' style. Or, put another way: People only have code styles because languages leave ambiguity. By removing that ambiguity you force your user-base to be consistent therefore increasing communication and productivity. I tend to agree. It really grinds my gears w…
Rust has grappled with the issue of how far to push styling rules. E.g. from 2016: https://github.com/rust-lang/rfcs/pull/1607#issuecomment-227... I think it's worth reading more of that thread for some pros and cons of being very strict with styling rules. Note that being too strict can lead to code being less readable in specific edge cases. This may or may not be considered a fair trade off.
Lilith: x86-64 OS written in Crystal
241–250 of 265 posts
Re: Lilith: x86-64 OS written in Crystal
#242Oh wow someone actually posted this! Thanks a lot for the comments and criticisms guys, really means lot to me. Before I go I'll answer some questions, so ask them away!
Re: Lilith: x86-64 OS written in Crystal
#243Earlier quoted context omitted.
I can only see 1,209 repos after using Crystal for close to a year, some are no longer maintained. https://github.com/topics/crystal There are lacking of stories around the cloud computing or any large businesses has success with Crystal. They need more of those to gain support if they don’t want to remain in “uncharted territory” which mentioned in their interview.
https://crystalshards.xyz/ is the de facto aggregator of various libs for the language.
Re: Lilith: x86-64 OS written in Crystal
#244Earlier quoted context omitted.
I have had a huge amount of issues trying to use both Ruby and Rust on Windows for server / client use cases. It's not just that it "works" on Windows, but that it works easily out of the box for common use cases. Meanwhile Python and Golang work great on Windows with no extra effort. It's like night and day.
What issues did you have with Rust? I use Rust on Windows every day.
Re: Lilith: x86-64 OS written in Crystal
#245Earlier quoted context omitted.
Mentally context switching between Ruby and any other language to do the translation actually is kind of a hassle.
I could imagine, that the subtle differences could get you ugly problems while porting.
Re: Lilith: x86-64 OS written in Crystal
#246Earlier quoted context omitted.
V have first-class Windows support, what is your problem?
My problem is that it doesn't actually work on windows. Get the latest build, run it with no arguments, get a large error instead of the REPL.
Re: Lilith: x86-64 OS written in Crystal
#247Earlier quoted context omitted.
What are some? I wrote a small ascii snake game with it and found it generally OK.
It’s been somewhat overhyped by the author.
Re: Lilith: x86-64 OS written in Crystal
#248Two things that I immediately respected about Crystal's landing page [1]: - It shows numerous code snippets covering various functionalities. Not just "Hello world" but code samples that give you a very solid flavor of the language. - Its spinning logo can be manipulated with the mouse. [1] https://crystal-lang.org/
Re: Lilith: x86-64 OS written in Crystal
#249Earlier quoted context omitted.
I am subscribed to the windows support github issue since 2013, so Crystal is definitely older than 5 years. I think its around 7 years old
The first release, 0.1.0, was in 2014. [0] [0] https://crystal-lang.org/2014/06/19/crystal-0.1.0-released.h...
Re: Lilith: x86-64 OS written in Crystal
#250Earlier quoted context omitted.
The first release, 0.1.0, was in 2014. [0] [0] https://crystal-lang.org/2014/06/19/crystal-0.1.0-released.h...
First official release maybe. But folks have been using Crystal since before that. This is the Github issue in question; https://github.com/crystal-lang/crystal/issues/26
The main point was comparative age of languages. Like OCaml which is more than two decades old compared to Crystal which is young.