>>201
Name
Please help me out here. Literally Robowaifu OS or just RWOS seems the best choice atm. There is a robotics SDK framework out there for Ubuntu called "Robotics OS" or just "ROS" (it isn't an OS, btw). This seems like a pretty well-established naming convention by now, so it seems fine to me.
Hardware
The ARM platform seems to be the best choice for this project for quite a few reasons, wide availability, probably the most diverse set of hardware vendors going, very low power consumption, cheap. Stress on those last two. With it's heritage in phones, the ARM architecture was designed from the start to be both energy efficient and inexpensive. It has grown more capable with each successive generation until now it's quite a formidable CPU device in the A7 and up, but it has basically maintained this original heritage throughout.
While security is undoubtedly also an issue for this platform, you don't hear about a lot of exploits and backdoors on this system, and my basic instinct is that it's better than AMD, and way better than Intel in this regard.
So, what particular ARM-based system? There are tons of them, but the RaspberryPi is the most well-known among the SBC (Single Board Computer) class. There is also the Pi Zero, which is a very low-cost variant (US$5) that has both a lower physical and power footprint. Then there's also the Beaglebone, both the Black and the Blue. The latter has specific benefits for robotics and was designed with this field particularly in mind.
While there's a ton about the RaspberryPi Foundation I don't like (it's cucked af now, though as usual it didn't start out that way), given the large amount of community support behind it I'd say that at the least it's the best starting point, though probably not the best final solution. Kind of like how starting with Ubuntu is a good choice for a Linux beginner just because there's such a large user community out there even though real enthusiasts rarely stay with it for long β there are much safer, much leaner distros out there.
Packaging
And since I want to use a clustered unikernel OS approach, naturally I want a cluster of RPis to constitute the Robowaifu brain. We'll use C++ as the language for the Robowaifu OS and run it on a cluster of networked SBCs for the Robowaifu Brain. The other attendant robotic sensors, motors, servos, actuators, and various output devices in the overall system will be networked to connect back to the RW-Brain hardware, and interact there with the RW-OS for control, data, and other services.
The RWBrain and RWOS will also house the waifu's personality and ability to communicate back with her master as well ofc.
* * *
(2 of 2)
>===
-
fmt cleanup
Edited last time by Chobitsu on 08/23/2023 (Wed) 03:35:54.