Conversation

Notices

1. Embed this notice
   ᒪᐸᒋᓐ(:raccoon_x3:)PUNK (itzpaquet@novo-atlantis.null.media)'s status on Thursday, 31-Aug-2023 05:18:20 JST ᒪᐸᒋᓐ(:raccoon_x3:)PUNK
   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 ^^
   
   #theWorkshop
   • Embed this notice
     ᒪᐸᒋᓐ(:raccoon_x3:)PUNK (itzpaquet@novo-atlantis.null.media)'s status on Thursday, 31-Aug-2023 05:18:17 JST ᒪᐸᒋᓐ(:raccoon_x3:)PUNK

     in reply to
     one of my development goals is to move away from the limbo runtime and replace it with a new engine based on a combination of scheme and forth. this is very much inspired by prescheme and nanopass compiler development. learning about APL and BQN (especially co-dfns) has thrown me through a loop, so i might be revisiting some of this because data parallelism is something that i would love to have access to for scientific programming stuff that i want to do in the future.
     Sexy Moon likes this.
   • Embed this notice
     ᒪᐸᒋᓐ(:raccoon_x3:)PUNK (itzpaquet@novo-atlantis.null.media)'s status on Thursday, 31-Aug-2023 05:18:19 JST ᒪᐸᒋᓐ(:raccoon_x3:)PUNK

     in reply to
     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!
   • Embed this notice
     Sexy Moon (moon@shitposter.club)'s status on Thursday, 31-Aug-2023 05:22:03 JST Sexy Moon

     in reply to
     @itzpaquet can you link me to tomo again, I promise I'll bookmark it this time. I searched my history and didn't find it.