Live data from Hacker News

Lilith: x86-64 OS written in Crystal

github.com

121–130 of 265 posts

Re: Lilith: x86-64 OS written in Crystal

#121
post #85
post #76

Earlier quoted context omitted.

Lots of the crop of new languages with cleaner designs have huge problems with windows. V doesn't work on windows and zig's compiler fails if you use carriage return newlines. They even built in an error message for it instead of just making the parser work. It's kind of ridiculous how these languages shoot themselves in the foot.

I think Zig is probably just being opinionated there; many of the new languages seem to be overly so. Last I checked, both the Zig and Nim compilers refused (on principle, not for any technical reason) to compile code containing tabs (among other things). 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.

Well, good for them wanting to die on that hill.

They will remain dead..

Re: Lilith: x86-64 OS written in Crystal

#122
post #15

Earlier quoted context omitted.

> It's older than Rust, Kotlin, Swift, Nim, or even OCaml, and doesn't really offer anything they don't. Crystal is only five years old. Nim is 11, Rust is 9, Kotlin is 8, OCaml is 23 and Swift is 5. Basically, Crystal is tied with Swift as the youngest. What it offers right now is a simple porting process for those with Ruby codebases.

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

#124
post #54

Is the dev a high school student? From their blog: https://fw.neocities.org/blog/5.html If so, this is crazy impressive.

Apparently they've also written a language, a static site generator in that language, a brainf*ck interpreter, and a markdown parser, among other things. Super impressive stuff. https://github.com/ffwff?tab=repositories

The next Fabrice Bellard?

Re: Lilith: x86-64 OS written in Crystal

#125
post #35

Just this morning I was pondering the same thing in Elixir. I wonder if Elixir and Crystal compete for ruby developers to pick up

I think Ruby developers are a lot more likely to switch to Crystal than Elixir. Elixir encourages a much more functional style than I think Ruby developers are used to.

There is definitely a lot of Elixir developers who come from Ruby. I mean José Valim himself was a core RoR team member.

I'm trying to find an Elixir job right now and pretty much all of these comes with a RoR requirement. (also it seems some companies are moving from Elixir to Go).

As I'm mostly a PHP / Symfony guy I feel the disconnect, and at my current place people really don't care about Elixir at all. Basically Go and Node would be much better prospect for me.

Re: Lilith: x86-64 OS written in Crystal

#127

Earlier quoted context omitted.

AFAIK fork() is specific to UNIX and its descendants; DOS, Windows, and many(most?) other OSs don't have it either.

Sure, but an OS that self-describes as "POSIX-like" would be expected to follow the UNIX approach to things.

POSIX-like, not entirely POSIX! There are basic IO syscalls, and some process management calls, but overall I try to take unix as a guideline rather than trying to reimplement one entirely. I also try to take inspiration from other kernels (like fattr (which is equivalent to GetFileAttributes from WinNT), and spawnv from DOS/WinNT).

I guess I should reword it :/

Re: Lilith: x86-64 OS written in Crystal

#128
post #73

I just missed it on my earlier comment. Homage to the Modula-2 OS, Lilith? https://en.m.wikipedia.org/wiki/Lilith_(computer) http://pascal.hansotten.com/niklaus-wirth/lilith/

Cool coincidence but nah. Maybe its a reference to the first angel in Evangelion? Maybe its a reference to Adam's wife? Maybe its best girl from Machikado Mazoku?

Hint: asuka best girl.

Re: Lilith: x86-64 OS written in Crystal

#130

How does memory management work in Crystal. Is it RC or GC or manual? As a D user, I've been curious about Crystal for a while, but until it gets proper Windows support I won't be playing with it too much.

Out of the box, Crystal does garbage collection through the boehmgc library, however if you pass in some compiler flags you can get application to not use GC.

As for my OS, I wasn't gonna port libgc, and since I have prior knowledge of building a GC in rust (very badly!) I decided to make a tri-color concurrent, mostly precise (through compiler patches), garbage collector, in Crystal.

Post reply on HN