if you aren't a huge fucking nerd you might not be aware that we spend way too much time debating the pros and cons of operating system types that will probably never leave the basements they were dreamed up in.
in my case, the design is of such an obscure type that there isn't much literature on the topic outside a handful of computer science research labs. as you can imagine there's no common parlance for something so odd, but I use the term "language kernel" or langkernel. not to be confused with an exokernel, through they can share some minor design patterns ^^
es q soy una chica, super poderosa
in reply to es q soy una chica, super poderosa • • •the way this works is that all of the operating system facilities are provided as language features. including managing access to low-level hardware access. in #tomo, for example, the cpu is completely virtual and garbage collected. the os does eventually generate machine code or interpret instructions, depending on the runtime settings, but as a programmer or user everything is presented through the lens of the language environment.
some programmers might find this distasteful, but that's ok. inside the os all of the regular low level stuff is possible and can easily be added or accessed through a device. the goal is to keep this collection of potentially unsafe trusted code as small as possible. the language environment works towards a similar goal by forcing everything to be done in a shared language runtime. like on the java vm, you can still use a variety of languages but everything ends up interoperable and runs on the same engine!
es q soy una chica, super poderosa
in reply to es q soy una chica, super poderosa • • •Devine Lu Linvega
in reply to es q soy una chica, super poderosa • • •es q soy una chica, super poderosa
in reply to Devine Lu Linvega • • •@neauoire i haven't quite landed on how i want the forth part to work, but in order to have the nanopass or prescheme optimizations happen it'll have to end up expressed as a scheme dialect at some point. its very likely that i'll end up with something that looks like joy.
i want something that i can use to explore the dis vm runtime context at a very low level. i'll probably end up doing a couple of different forths that don't have anything to do with scheme while i'm working on the project tbh.
Devine Lu Linvega
in reply to es q soy una chica, super poderosa • • •es q soy una chica, super poderosa
in reply to Devine Lu Linvega • • •@neauoire i think dis is somewhere between CISC and VLIW, newton is an ARM chip i think? dis is surprisingly high level in certain areas. like car, cdr, and cons are all there in the isc. you can also do CSP operations like create and communicate over channels. its pretty neat.
http://doc.cat-v.org/inferno/4th_edition/dis_VM_specification
i haven't found any forths targeting it, but i might have missed it! that would be neat to stumble upon.
Dis Virtual Machine Specification
doc.cat-v.orgDevine Lu Linvega
in reply to es q soy una chica, super poderosa • • •Ah yeah it's the Hobbit 😀
https://en.wikipedia.org/wiki/AT%26T_Hobbit
One side effect of the Hobbit design is that it inspired designers of the Dis virtual machine (an offshoot of Plan 9 from Bell Labs) to use a memory-to-memory-based system that more closely matches the internal register-based workings of real-world processors.
microprocessor
Contributors to Wikimedia projects (Wikimedia Foundation, Inc.)