@tychi RISC-V is an open source and free processor architecture and instruction set. Think of it as an open source general computing processor

@brandon thanks, i see the hype now 🤤

@0PT41N heheh :D What kind?

@brandon Using the Ultimate SBC! Probably a portable super computer cluster of these bad boys. Or use it as my main desktop computer if it turns out to be really good. Or who knows the human I imagination is limitless 😁 What would you do I you had one of these in front of you? 🤔 https://beaglev.seeed.cc/

@0PT41N Depending on the SATA driver and amount of RAM available, likely use it as a NAS

@brandon Oh yea! I forgot to add that to the toot. Yup that would be one Over powered NAS 😁 (Unless you host for more then one person🤔 )

@0PT41N I'm not sure about overpowered. I've had issues with throughput even on the RPi 2. Something I'm missing?

@brandon Whats throughput? 🤔

@0PT41N Sorry, I mean to say that the disk writing speeds were slow. That being said, this was USB 2.0 speeds so maybe on one of the newer Pi's I'd be better serviced

@nathand That's a fair point :P Though I'm wondering how much software has been ported to the architecture

@brandon https://wiki.debian.org/RISC-V

Debian, of course, is ahead of the curve.

@nathand I remember the announce of the completion of that port but the last "status update" seems to have been in 2019

@themactep Any specific reason?

@brandon mouse button ceased to work, huh? visit the account. "it's full of stars". he's tinkering with bl602 as we speak.

@themactep Exciting!

@alexbuzzbee heheheh, likely what the biggest blocker will be

@wizzwizz4 ouuu, what would you call it? What's the feature set?

@brandon The current name is EisOS. Features include something functionally equivalent to a capabilities system, a graphical programming language / shell / UI (the UNIX philosophy turned up to 11) and – ideally – native support for having one instance of the OS on your phone *and* home computer *and* laptop, and then splitting a bit off and adding it to another instance later, with resource permissions working perfectly.

Ambitious, but possible.

@brandon I'm waiting for RISC-V because one of the pieces of underlying technology (Eis, a work-in-progress language that's changing a lot in development, but consistently seems to have the right properties for EisOS – if it stops being the case, I'll rename the OS) kind of needs a good description of the processor architecture to work properly, and RISC-V seemed easier than starting with a reverse-engineered description of x86 microcode.

@jordan31 I'd say that's a pretty good use!