My point is that you might be measuring customer needs/migration path in a way differently than customers do (if you repeatedly see them move away to a 3rd party, especially one particular 3rd party).
A common theme in this thread is that people inside Rackspace see Rackspace Cloud + Slicehost as very similar, because 1) they have a common corp ownership 2) they have an increasingly common (but hidden-to-users) back-end 3) they have common staff in some cases.
But the customers in this thread see Linode + Slicehost as much more similar because 1) their control panels are a bit more similar 2) they share DNS flexibility + other featuers 3) Price (Linode moving in more attractive direction for some use-cases).
Neither interpretation is necessarily right, but in this era it's definitely time to rethink what customer needs are (if you're outlining a migration path). I don't think RS is wrong for discontinuing Slicehost (I'd definitely wanna EOL older products), I just think they're wrong in how they parse features, experiences, and what user needs are.
I see since I posted earlier that user:polvi (hiya!) says the Cloudkick posse is working on the control panel for RSC. I've no doubt that all providers will greatly up their UX game (something something Dave McClure design dogma :D).
It just feels disingenuous for RS peeps to say over and over "Slicehost services are not dying, it's just the brand that's going away" when real features and real UX are going away, at least for a window of time. And it's totally normal for users to go where those features and UX can be found, even if it's a separate company. To users, that feels easier.
UX at rackspace now is ick at best, but since the Polvi virus is currently spreading in the place, I'd bet on significant improvement.
I just see that there are two independent issues. One is that Rackspace UX needs help, the other is that there are dual/competing brands, one of which is feature stranded. Clearly they are related when you consider collapsing the brand into one, but I still think it's worth thinking about them in terms of two distinct issues.
A common theme in this thread is that people inside Rackspace see Rackspace Cloud + Slicehost as very similar, because 1) they have a common corp ownership 2) they have an increasingly common (but hidden-to-users) back-end 3) they have common staff in some cases.
But the customers in this thread see Linode + Slicehost as much more similar because 1) their control panels are a bit more similar 2) they share DNS flexibility + other featuers 3) Price (Linode moving in more attractive direction for some use-cases).
Neither interpretation is necessarily right, but in this era it's definitely time to rethink what customer needs are (if you're outlining a migration path). I don't think RS is wrong for discontinuing Slicehost (I'd definitely wanna EOL older products), I just think they're wrong in how they parse features, experiences, and what user needs are.
I see since I posted earlier that user:polvi (hiya!) says the Cloudkick posse is working on the control panel for RSC. I've no doubt that all providers will greatly up their UX game (something something Dave McClure design dogma :D).
It just feels disingenuous for RS peeps to say over and over "Slicehost services are not dying, it's just the brand that's going away" when real features and real UX are going away, at least for a window of time. And it's totally normal for users to go where those features and UX can be found, even if it's a separate company. To users, that feels easier.