This isn't the CLR. In our world, we compile entire MSIL for the kernel into x86 instructions at installation time. There is no libc at the bottom. However, we do have around some assembly code. Like a kernel written in C, our C# kernel needs assembly code to handle the lowest part of the interrupt dispatch on the x86. But once the assembly code has finished, it dispatches directly into compiled C# (no C). BTW, there is some C code in the system, primarily for the debugger stub.
Beer28 wrote:comment withdrawn.
Beer28 wrote:I just finished it, at the end Charles commented on the OS having a webserver asking if it "parsed html and stuff." (52:10)A webserver reads the file off the disk(the document portion of the http request header), optionally shoots it to registered functions of interpreters loaded as modules in it's proc address, like mod_php or mod_perl, or even mod_mono, or does cgi piping(older style) to an interpreter process, then takes that output and throws it back down the tcp line with send(socket,,);An http server doesn't do any type of document processing on it's own, that's the browser on the client side that parses it, and sets it up for drawing to the client area. That's why the guy came back right away and said "http".
Manip wrote:It was just lots of edits as he watched the video, very messy, no loss.