I'd have to agree to what some people said here.
While, of course, classes like Sprite and Text are nothing but convenience classes which aren't technically needed, they do make the "S" in "SFML". I support the idea that it should stay simple, and these convenience classes should be implemented, but those who seek performance or more detailed control should be able to use the new API. It's a win-win that way.
What I'm not sure about is the transformation thing. Firstly, I kindof have to agree to Disch, they and views have a lot in common. Furthermore, I think that maybe the Drawable class should stay mostly as it was, basically for the same reasons I mentioned above, but also because in my eyes, this new approach is a step away from object-orientation. This may be debatable, but I think that a drawable entity is the combination of a Mesh and a Transformation, and the former API nailed it.
Besides, I would maybe rename the sf::Point class to sf::Vertex. "Point" to me sounds more like a Vector2i alias than a structure for world coords, color and tex coords.
Other than that, I like that you are now able to define custom meshes! sf::Mesh fits perfectly as the name. It was the missing link in the drawable API and completes it IMO.