This is really impressive! Crystal was just barely on my radar until now: it's a lot higher up now. For anyone unfamiliar: https://crystal-lang.org/
Crystal has the most badass color on Github. Solid black.
Lilith: x86-64 OS written in Crystal
251–260 of 265 posts
Re: Lilith: x86-64 OS written in Crystal
#252Earlier quoted context omitted.
In what way is Elixir's syntax like Ruby's? It has "end" on blocks and string interpolation with "#{whatever}", but everything else is different. It's about as close to Ruby as Ruby is to Python (which is to say, not much).
I think it really helps that you can write mostly functional code in Ruby by just chaining higher-order array functions, and you can use Pipes in Elixir to do this almost identically -- when you consider the fact that all the higher-order array functions have identical or very similar names and parameters in the two languages. My Ruby code is like 95% chained higher-order array functions. My classes almost never have…
Re: Lilith: x86-64 OS written in Crystal
#253Earlier quoted context omitted.
Maybe it's just because I come from Ruby, but Crystal seems like an amazing language. I'm interested why it seems to be getting little attention compared to Go, Rust, & Julia. It seems in the same league to me. Kotlin and Swift have more obvious reasons for their adoption.
What's Crystal's unique selling point? It's older than Rust, Kotlin, Swift, Nim, or even OCaml, and doesn't really offer anything they don't. More Ruby-like syntax? Fine, but most people don't particularly like Ruby syntax.
Re: Lilith: x86-64 OS written in Crystal
#254Earlier quoted context omitted.
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.
What is "latest build"? V does not release any stable build and you can get "large error" on any platform right now when trying random "latest build" without any effort to investigate the issue.
Re: Lilith: x86-64 OS written in Crystal
#255Re: Lilith: x86-64 OS written in Crystal
#256Earlier quoted context omitted.
Presumably they're following python's example here.
Python works just fine with tabs, but the language-endorsed style guide (PEP 8) recommends against them. (However, the usual plugin for Vim requires adding "let g:python_recommended_style = 0" to work correctly.)
Re: Lilith: x86-64 OS written in Crystal
#257Earlier quoted context omitted.
> I don't (usually) want my compiler to do linting, and I certainly don't want language authors to dictate my code style from on high. Enforced code style consistency has considerable advantages. "Linting" probably shouldn't be a thing.
Across a specific project, team, or org, sure. That's what style guides, formatters, linters, and pre-commit hooks are for. The core language is the wrong level of abstraction for this stuff.
Re: Lilith: x86-64 OS written in Crystal
#258Earlier quoted context omitted.
What issues did you have with Rust? I use Rust on Windows every day.
It's been a while, but it was the common issue with certs that Ruby on Windows also has. I just couldn't get it sorted for whatever reason. Maybe it's not an issue anymore though? Rust http client works OOTB on Windows?
Re: Lilith: x86-64 OS written in Crystal
#259Earlier quoted context omitted.
I found Crystal about a year ago and absolutely fell in love with it. It just “clicks” for me. My sense from reading most peanut-gallery commentary that the biggest reasons it hasn’t taken off more (yet) are: 1. Real multi-threading (it’s now in alpha - but previously just had single-threaded concurrency - and sorry I might be getting that terminology wrong). 2. Windows support (I personally don’t care but I haven’t…
Does anyone actually care about Windows support?
This has been hurting RoR adoption for long, although at this point it probably no longer matters.
Re: Lilith: x86-64 OS written in Crystal
#260Earlier quoted context omitted.
Thanks but the code isn't that clean, there are hacks here and there and it isn't organized as clearly as I wanted to but feel free to look through it.
> the code isn't that clean It's cleaner than a solid 90% of the code I've read over the years :)