Oh 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!
How old are you?
shhh.
Lilith: x86-64 OS written in Crystal
131–140 of 265 posts
Re: Lilith: x86-64 OS written in Crystal
#132Oh 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!
How/when did you get started with coding? How did you learn your skills and how do you stay so productive?
Re: Lilith: x86-64 OS written in Crystal
#133I wonder what the plan is for a media layer - audio and video streaming, etc?
Sure would be fun to write a content-creation app - i.e. DAW - for such an environment.
Re: Lilith: x86-64 OS written in Crystal
#134Oh 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!
- What are the things that you have patched in crystal and libc?
- Any plan to release ISO for us to quickly run it in our local system?
Re: Lilith: x86-64 OS written in Crystal
#135Earlier quoted context omitted.
My thoughts exactly, I know people have their own tastes and preferences, but I think it's off-putting to newcomers.
Perfectly fine as per European standards.
And probably by asian standards too.
Basically anyone non-american is ok with this i think (knowing the author is probably also underaged). I hope US scare of anything barely related to nudity won't be the new norm.
Re: Lilith: x86-64 OS written in Crystal
#136Earlier quoted context omitted.
Interesting choice of syscalls: https://github.com/ffwff/lilith/blob/master/userspace/librar... . No fork; instead it seems to implement spawnv.
fork is not friendly to concurrent programming: fibers/threads/callbacks - what should you do with all this after fork? While it is possible to create and manage some rules, it is simpler not to fork at all.
Yes. Fork was a clever hack for one point in time, back when processes were simple, single-threaded, and lightweight. It's always had the misfeature of inheriting resources which you didn't ask for. Not including it makes it mildly annoying to port existing programs, but 99% of the time programmers want spawn and are forced to build it from fork(), not the other way round.
Re: Lilith: x86-64 OS written in Crystal
#137Oh 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!
How/when did you get started with coding? How did you learn your skills and how do you stay so productive?
I second this, please, oh lord, tell us!
Re: Lilith: x86-64 OS written in Crystal
#138Oh 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!
I just wanted to say, to build such a fully-featured OS on your own, and in such a short time frame, is an incredible achievement!
I very much look forward to reading through the code and learning more about it.
Re: Lilith: x86-64 OS written in Crystal
#139Earlier 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?
Well, I guess devs on Windows do.
Windows support means less friction for people who wants to try it out.
Re: Lilith: x86-64 OS written in Crystal
#140Earlier quoted context omitted.
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 :/
Google's Fuchsia has a similar approach to Posix (no fork, signals, etc). Maybe some of their wording would be of use?
https://fuchsia.googlesource.com/docs/+/refs/changes/56/1013...