Live data from Hacker News

Lilith: x86-64 OS written in Crystal

github.com

151–160 of 265 posts

Re: Lilith: x86-64 OS written in Crystal

#151
post #33

Earlier quoted context omitted.

That never stopped the Go community from porting Go to Windows. It was never ported by core maintainers, but by Go developers themselves.

And yet it was ported, and has OK support. Crystal on Windows is a non-starter right now.

> OK support

I havent had issues with Go on Windows or any OS, is there something broken about Go in Windows?

Re: Lilith: x86-64 OS written in Crystal

#152
post #17

Earlier 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?

I never thought there would come a time when I would want windows-support. However, the case is, that Windows as it is today, is quite inevitable. Hence if you want Crystal, you probably want Windows support.

Re: Lilith: x86-64 OS written in Crystal

#153
post #46
post #44

Earlier quoted context omitted.

Okay, port your existing Ruby code to a compiled language, giving it multiple times the speed? Maybe three is a slight business opportunity here. Also, give your developers a more productive language that can go where Ruby can't (like OS development), which is 90% instantly recognizable — may also be worth something?

Is it really so hard to port Ruby code to any of the languages I mentioned? Even with Crystal you will still have to make changes to your code, is having to use a slightly different syntax such a big difference? If you've got Ruby code and you haven't already ported it, how badly do you need the speed?

Mentally context switching between Ruby and any other language to do the translation actually is kind of a hassle.

Re: Lilith: x86-64 OS written in Crystal

#154

Neat project, though slightly undermined by the drawing of the half-naked underage girl in the readme

So This guy (an high school student), writes a OS, from scratch, and you made an account to say that his choice of wallpapers "undermines" his project. I guess you're one of the people that supports things like that bullshit code of conduct that is popping up pretty much everywhere. RIP the hacker spirit of the 70s. May it rest in peace. Welcome to this brave new world where people like you are welcome instead of bei…

If the 70s hacker spirit included thinking there was nothing wrong with posting a picture of a half-naked woman in a tech project then good riddance.

Re: Lilith: x86-64 OS written in Crystal

#156

Earlier 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.

I wouldn't say it's getting "little attention," rather it's relatively new (for a language) and not backed by a major player who can instantly give it a huge spotlight / platform. For being a 5-year old indie language out of South America, I think it's doing quite well, and projects like this are good evidence of why. Ruby is an outstandingly productive language. Copying the expressive syntax and ergonomics of Ruby i…

Two other languages that I can think of that have their roots in South America are Lua and Elixir.

Re: Lilith: x86-64 OS written in Crystal

#157
post #81

Earlier quoted context omitted.

That seems decidedly unsafe to say, but even if you’re right, the second paragraph doesn’t follow from the first. “Everyone generalizes from one example! At least, I do.”

It's been shown repeatedly. Arthur Whitney is another example. In fact, basically every major technological innovation of the past two centuries has been because of people doing this. The first was just to share an example. The second paragraph is common knowledge.

We do depend in a profound way on people trying the impossible for our civilization to progress. But at the same time most attempts to do the impossible do end in failure and I think it would be mistake to say that people trying do the impossible do better on average than those who don't. Rather, we should encourage play, tilting at windmills, etc knowing full well that we're accepting the danger of failure now but making an investment in the future.

Re: Lilith: x86-64 OS written in Crystal

#158
post #46

Earlier quoted context omitted.

Is it really so hard to port Ruby code to any of the languages I mentioned? Even with Crystal you will still have to make changes to your code, is having to use a slightly different syntax such a big difference? If you've got Ruby code and you haven't already ported it, how badly do you need the speed?

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

#159
post #12

Earlier 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.

I'm not familiar with all those langauges but I found the inference of union types pretty impressive.

foo = ENV["FOO"]? || 10

Re: Lilith: x86-64 OS written in Crystal

#160
post #90

Earlier quoted context omitted.

Kotlin - it's on JVM which is a good thing for some and a bad thing for others. It's easier to distribute standalone crystal binary for example. Swift - crystal throws exceptions, swift explodes... Ocaml - the functional approach is not for everyone. Rust - I like rust a lot. But sometimes I want to write something quick and I'm happy to sacrifice some memory and speed to not have to deal with the ownership issues. N…

You can use Kotlin/Native [0] or just plain Kotlin over Java with GraalVM which produces compact binaries. [0] https://kotlinlang.org/docs/reference/native-overview.html

Kotlin/native's stdlib isn't feature complete. You have to use raw syscalls to do anything.
Post reply on HN