crosstalk

Author here - this xv6 port to the D1 (based on the riscv64 xv6 version developed at MIT) is an experimentation vehicle for me and my students since working with qemu alone can be a bit boring and it's easier to test some feature in a tiny OS. Of course, it's also fun to work on it... "...won't be big and professional like gnu." :) Based on the experiences with xv6, we are also working on porting some other non-mainstream systems to RISC-V hardware, including Plan 9, Inferno, Oberon, Smalltalk-80 (see my Raspberry Pi bare metal ARM version at https://github.com/michaelengel/crosstalk) and the f9 microkernel. If you have any questions about the xv6 port just ask. Shameless plug - I'm looking for a PhD student to work on OS/compiler/architecture-related topics in my research group here at Bamberg University (in the northern part of Bavaria

What if those already-used tools weren't as-good for writing Smalltalk programs? ---- > … its own OS and GUI. Well there are examples of bare metal Smalltalk (I'm guessing we could say the same of Java?) https://github.com/michaelengel/crosstalk but that was kind-of unusual and afaik commercial Smalltalk implementations targeted specific host OSes. ---- Similarly back in the '80s commercial Smalltalk implementations provided their own GUI L&F (and in the '90s Java provided their CrossPlatformLookAndFeel aka Metal). When OS GUIs became available in the '80s, Smalltalk implementations either targeted specific host OS GUIs (so on MS Win use MS Win controls) or provided portable GUIs based on emulated L&Fs (OS/2, Motif, MacOS, MSWin) (and in the '90s Java provided AWT/Swing…). IBM Smalltalk (Visual Age) GUIs were based on what would beco