41–50 of 62 posts
Earlier quoted context omitted.
Should fix the line height so the lines connect to each other.
which browser doesn't show that right? chrome and firefox have connected lines for me
Not that that helps in any way, since you never know which font might be used^^
Why the 205.5? Why wouldn't this work as 205 + RND(1)?
You can recreate the magic in bash: while true; do printf "\u$((2571 + ($RANDOM & 1)))"; done
while true; do printf "\u$((2571 + ($RANDOM & 1)))"; sleep 0.02; done
Why the 205.5? Why wouldn't this work as 205 + RND(1)?
205 + RND(1) would always evaluate to 205 when truncated.
205.5 + RND(1) pseudo randomly selects between 205 and 206
Lacks randomize()
I think Commodore BASIC had a more complex way of seeding the random timer: https://www.c64-wiki.com/wiki/RND POKE 56328,0 : REM real-time clock activate with 1/10s -> clock runs ($DC08) PRINT RND(0) : REM Random number addicted by timer and real-time clock
Providing a neg number to RND would "reseed" the random number generator. TI was a "system" variable that updates every 60th of a second.
Love it! Brings up so much nostalgia from the days of programming on my old TRS-80. But is it really a maze? Once you start, you don't seem to get much choice of path...
https://www.youtube.com/watch?v=lWyZO-yPnvM
For anyone not familiar with the TRS-80, who finds the code somewhat weird.. the BASIC implementation was written by Microsoft. Only the first two letters of variable names were significant. Although interpreted, the ROM tokenized typed lines, meaning it didn't care about spaces.
This led to such gems as:
FORK=10 TOMATOES STEP LADDER
Why the 205.5? Why wouldn't this work as 205 + RND(1)?
RND(1) returns a value between 0 and 1, but always lower than 1. Thus, the result of 205+RND(1) will always be 205 point something, which in turn will be truncated to 205. Thus, it will always result in the same character.