Right! I’m in a bad mood today and the crap out of CES 2018 isn’t helping. My short review is “most of these are garbage, and the rest have some brain damage.” Here’s a quick run down of the big ticket items and why I do or do not like them. (more…)
It’s great fun to wave your hands in the air and yell about the Terminators killing everyone, just as it’s fun to pretend the zombie werewolves are coming or the undetectable sky man has had enough. Today I’d like to make the case that the AI could prolong the human race – even prevent an apocalypse.
Prosthetic arms, prosthetic hands, and prosthetic limbs are useful and good… but Marginally Clever Robots won’t be making them any time soon. Read on to find out why.
Robot Overlord Java app contains lots and lots of classes, some of which are robots and their gui.
I want robot developers to have an easy time adding their robots to RO. A simple interface, minimal distraction, and examples to work from are Good Things. I’m told that RO can use a Service Provider Interface (SPI) to load a jar it’s never seen before, a jar that contains an implementation of the interface. I would then
What I’m discovering is that SPI is tricky tricky.
There are several possible points of failure, none of which can be clearly eliminated as possibilities. Worse, I’m not sure how these plugins would be debugged. Running RO would not give a lot of insight into the plugins’ inner workings. Would I still be able to tweak code in real time? That is a must.
So I ask you, dear reader: am I way off track? What do?
I should note here that I do not want to have to run RO from the command line with a custom classpath. While I’m able to do it, I doubt that the people who buy robots and use them will even know how to open a command line. Imagine a grade school teacher trying to set up for their students, or your aged mother who’s used to OSX. It ain’t happening. You don’t want that tech support phone call and neither do I.
