It was Adobe that was quoted as working with Aperture users to make the transition easier. Don't know that you can read much of anything into that, as Adobe has been competing with Aperture to gain users for years.
Since many users here are either people who make at least some income from photos, or are heavily invested in photography as a hobby, I find the comments about sticking with Apple rather strange. Reread the OP and comments before the Aperture obituary: the common thread is that Apple doesn't seem to be interested in the dpreviewer niche market. She doesn't love you anymore; move on.
The choice of one particular software program for a DAM is not analogous to the choice of an editor: you can use PS, Pixelmator, Photogene, ACD, GIMP, etc etc for that and produce interchangeable files and it doesn't matter much if one goes kaput. You might have to relearn some stuff, and maybe lose some settings and plugins. But if you commit tons of edits to a database that cannot be migrated to another database, you are seriously painting yourself into a corner. You can export edited product, but you still lose a lot in the process.
So LR fans should take this as a warning as well. I began moving over a long time ago, and accelerated that a year ago when it became clear Aperture was either going nowhere or possibly morphing into something completely different, but even now I wonder if that was smart. I don't think it very likely that LR would disappear. But what if a DAM product came by that was superior to LR, or that added a key functionality that I absolutely had to have, but didn't exist in LR (multiuser, storage on a NAS, speed, etc etc)? What if you have to move to a different operating system (another reason why I had to start making the switch a while ago? Sheesh, I may end up moving a bunch of stuff into Photos on Yosemite even if it isn't a superior DAM, just for all the stuff I accumulate on my iPhone, or for editing or sharing purposes.
No software is guaranteed permanence (occasionally it may resurrect itself, however, cf ACD's Canvas for Mac). The best you can do is create workflows, backup plans, and archive that take this kind of disruption into account. So you don't get caught out again.