Have NONE Results Fade Out After a Time #100
Description
Some functions (like today's PRINT) are not void, because they don't want callers to depend on them vanishing. It's preferable to have people write elide print "..." so that it's clear they are being "vaporized". Today this permits PRINT to say whether it actually printed anything or not, by returning NULL if nothing is output.
However, this can be visually disruptive:
>> print "Hi"
Hi
== ~ ; isotope
>> print "That's extra noise"
That's extra noise
== ~ ; isotope
The web console has the ability to do richer feedback, e.g. it could print the result out but have it fade out and disappear after some amount of time.
On the forum, @BlackATTR wrote:
I like the way you're thinking here. I would like to discuss this in a broader sense in a future video meeting. There are opportunities to enhance basic user interactions and impart an illusion of awareness and intelligence-- as opposed to the rough-edges "80's cash-register" equivalent of interaction. Plus it ties into the "minecraft of programming" ethos.
(I migrated the idea here to streamline a conversation thread.)