TID: Mystic BBS 1.12 A48
MSGID: 1:129/215 268874a8
REPLY: 2:250/5 5894e56a
TZUTC: -0500
 CS>  g0> I was just about to pull the trigger on an Orange Pi 5 today but 
CS>  g0> then
 CS>  g0> saw it doesn't have Wifi and Bluetooth, so I am off to check out 
CS>  g0> some
 CS>  g0> local stores to see if I can get lucky and find stock of anything 
CS>  g0> use
 CS> 
 CS> Something for the future to ponder, would you ever get into trying RISC-V
 CS> compatibility? Seems that RISC-V is quickly being something lots of
 CS> people are shouting about now, might be a good thing to get into?
 CS> 
 CS> Maybe something like a VisionFive 2 might be something to use in the
 CS> future, looks promising.

Yeah absolutely.  I think they started adding RISC-V back into 2019 to the
compiler I use for Mystic, so assuming its in a usable state I don't see why
not.

I do think there is little benefit of RISC-V for a BBS system over existing
ARM/Intel.  The thing it has going for it is energy efficiency which is great
for embedded devices, things that run off of batteries, etc.

But if I am not mistaken it can't hang with Intel in terms of the number of
CPU cycles it takes to do things, which means it'll always be better to grab a
non-RISC device over RISC for a BBS anyway.

... Live every day as though it were your last. One day, you'll be right

--- Mystic BBS v1.12 A48 (Windows/64)
 * Origin: Sector 7 * Mystic WHQ (1:129/215)
SEEN-BY: 1/123 15/0 90/1 105/81 106/201 114/705 120/340 616 123/10
SEEN-BY: 123/120 131 129/215 305 153/7715 154/10 30 40 50 700 218/700
SEEN-BY: 218/840 220/70 90 221/6 226/17 18 30 70 100 227/114 201 229/110
SEEN-BY: 229/111 112 113 114 206 275 307 310 317 400 424 426 428 452
SEEN-BY: 229/470 550 664 700 250/5 8 266/512 267/800 280/464 282/1038
SEEN-BY: 292/854 298/25 301/1 305/2 3 317/3 320/219 322/757 342/200
SEEN-BY: 396/45 460/58 633/280 712/848 770/1 2320/105 3634/12
PATH: 129/215 154/10 770/1 317/3 229/426