Author: Virgil Dupras <firstname.lastname@example.org>
Date: Mon, 26 Dec 2022 09:29:35 -0500
I'm removing the mescc part because the code targets too primitive a CC. DuskCC
can do better than this already and the hoops that the mescc code goes through
to go around its CC limitations don't look good.
1 file changed, 11 insertions(+), 8 deletions(-)
diff --git a/ROADMAP.md b/ROADMAP.md
@@ -33,10 +33,11 @@ Same thing for a hex editor.
## Begin porting UNIX apps
-I was thinking of beginning with something like [GNU diffutils][diffutils]. I've
-also been [hinted][hinted] at [mescc-tools-extra][mescc-tools-extra] which has
-versions of some important tools (ungz, etc.) in a dialect of C that is a better
-fit to more primitive compilers. Seems like a good fit.
+I was thinking of beginning with something like [GNU diffutils][diffutils].
+Another good one to port would be [libcaca][libcaca]. Being able to do some
+vizualization on the Grid without needing to enable the graphics mode would
+bring a lot of flexibility to the system.
@@ -69,13 +70,16 @@ configuration.
## Graphical system
-Being able to push pixels to screen will eventually allow for PDF viewing and
-will also allow varvara-based uxn roms to run on Dusk.
+Graphics are already in Dusk, but there's a long way to go to make them
+convenient and fast. So, it's a WIP.
## New architectures
What about the Raspberry pi? An [ARM port is in progress][arm-port].
+Otherwise, I have an old Powerbook 520 lying around and I'd love to have Dusk
+running on this, so m68k is right there on the roadmap.
## Disassemblers, emulators
Disassemblers and emulators are very useful tools to play around. We should have
@@ -95,6 +99,5 @@ Especially to access mass storage through it.