Hi Alan and Pito and all,
I guess the thing of most interest is 'easily' hooking your low level hardware to the 'web' or network.
LiteBSD has tcp/ip 'built in'.
My comment would be that something like fuzix could be very useful if well documented and has a test suite to insure 'proper' working.
In the PDP days there was a LOT of test software. There were so many subtle ways in which things could be different due to a broken ball bond inside a package, a defective design, etc.
Today is really no different except that all the stuff is inside a chip and so complex that complete testing is only a dream. And has become somthing like 'it seems to work' and people buy it.
That seems to me to by why interpreters like Java are so popular. The interpreter 'instructions' can be more easily tested for some corner cases.
But when the interpreter is designed to have hidden internal 'features' all bets are off. I assume hidden internal 'features' are all over the place at this point.
And internal flash memory makes things MUCH worse since the 'chip' operation now depends on its long term history.
And then there is the issue of custom, one of silicon made to look like commodity silicon.
So I guess that supports software that will run on multiple commodity chips. If it doesn't seem to work OK, change the chip or even the processor version or manufacturer it is running on. And test with different equipment for identical input, output operation.
And so I get back to easy portability. And multiple implementations all 'known' to work. Which is probably more or less of a dream.
I notice that retroforth 12 has an even smaller and more documented kernel.
Lots of fun