From: cross@spitfire.i.gajendra.net
In article <2eLSL.316602$5S78.216629@fx48.iad>,
Scott Lurndal wrote:
>cross@spitfire.i.gajendra.net (Dan Cross) writes:
>>In article ,
>>Scott Lurndal wrote:
>>>cross@spitfire.i.gajendra.net (Dan Cross) writes:
>>>>In article ,
>>>>wolfgang kern wrote:
>>>>>easy answer: it is C, aka limited+bloated+weird HLL-stuff.
>>>>
>>>>It certainly seems like the time for building large systems in C
>>>>has passed. Frankly, we have better choices now.
>>>
>>>We had better choices three decades ago when we were writing full
>>>operating systems (large scale, distributed) in C++[*][**].
>>
>>Eh.... I don't know that C++ is a particularly compelling
>>improvement over C. It retains many of C's poor semantics, such
>>as the type promotion rules that can lead to hidden UB,
>>nullable pointers, etc, while the object and template semantics
>>are often surprising and unintuitive.
>>
>>>We designed a hypervisor at SGI in the late 90's in C++[**].
>>
>>Was that part of the Disco work?
>
>More like inspired by it. It was a skunkworks project with
>about 8 people working on it, including the chief scientist jwag.
Oh cool. I always thought that MIPS would be hard to virtualize
because of the ksegs and soft-TLBs. It was never clear to me
how a hypervisor could, in general, know the format of the guest
page tables. I know the Disco folks had to make some changes to
Irix to get it to work.
>>I've been pleasantly surprised at how well Rust fits the problem
>>domain. It's not perfect, but is much better than I had assumed
>>it would be when I first started playing around with it and it's
>>miles ahead of C.
>
>It's on my list to look at, but probably not 'til I retire.
Highly recommended. The first time I walked off the end of an
array in an ersatz ACPI parser and got a well-defined panic
instead of overwriting random data, the hair on my wrist stood
up.
- Dan C.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
