Post 9zpRfomUSFPTiRpFcu by vertigo@mastodon.social
 (DIR) More posts by vertigo@mastodon.social
 (DIR) Post #9zpReq5A8D6JSh5nlI by vertigo@mastodon.social
       2020-09-28T20:25:51Z
       
       1 likes, 0 repeats
       
       So, I looked at EmuTOS source code this morning.  I don't think I'll be porting this software to the #Kestrel3 .  Reasons include:1. As I expected, it is tied tightly with the m68k architecture.  And, that's OK; it does what it says on the tin.  I just was hoping that some of the footwork for making it more portable has already been done.2. There is no migration plan; nothing to tell me, "Start here."  Tripos, however, does have at least *notes* to this effect, which is very helpful.
       
 (DIR) Post #9zpRfomUSFPTiRpFcu by vertigo@mastodon.social
       2020-09-28T20:33:51Z
       
       1 likes, 0 repeats
       
       What I am thinking for the #Kestrel3 going forward is I should port Tripos (yes, that means system software will be written in BCPL, not C) to get *something* working.Then, try to bring up a GUI environment within Tripos.  It won't be compatible with GEM, but I envision it would share its essential features (its overall architecture, for example) along with some repairs to GEM's architectural deficiencies (8.3 filename limitation, single-click latency, etc.).
       
 (DIR) Post #9zpRfzMJ7w0CWQezqK by vertigo@mastodon.social
       2020-09-28T20:35:02Z
       
       1 likes, 0 repeats
       
       I might even take some architectural cues from Plan 9 and Rio.Whichever is easier to get off the ground and working sooner.