Personally, I wonder about the future for the Rabbits. At distributors, a lot of them are marked as "not recommended for new designs". Here at Digi, when looking at SBC evaluation boards, all Rabbit ones are marked "matured", while none of the "featured" ones has a Rabbit.
So it might be that Digi doesn't want to put too many resources into something nearing EOL.
But that is just speculation.
After all they are putting effort into clearing up and opensourcing some of the Rabbit software:
This also opens the way to a possible future for Rabbit development. It already helped with the revival of OpenRabbit (https://github.com/spth/OpenRabbit), and there could be a way to a modern development environment:
* Port Rabbit support from OpenRabbit to OpenOCD
* Add Rabbit support to gdb
* Add ELF support in the Small Device C Compiler (SDCC) Rabbit backends
* Port the libraries from Dynamic C to SDCC
* Add support for Rabbit 4000/5000/6000 in SDCC
Then one could target Rabbits using any modern IDE that supports SDCC (e.g. Code::Blocks) with on-target debugging using gdb via OpenOCD. Such a toolchain already works for the STM8.