The hybrid drives make a lot of sense, the SSD section is just considered a cache.
It does not really matter that the SSD part is small (in relation to HDD size) as vast majority of files on HDD (or SSD) are never accessed regularly anyway.
The hybrid drive does not loose performance also, as every time the HDD disk part is de-fragmented, the SSD part is wiped clean for a fresh start (trim not required).
They should also be very reliable, as the SSD part will cut down mechanical access, and as the SSD part is only acting as cache, if any of the SSD memory fails it still continues as data always on the HDD part.
A good analogy of hybrid drives is between a CPU's cache memory speed, and the speed of main memory. Similar to CPU cache, providing the drives used as boot/application a high percentage of hits will be from the SSD part.
One downside however is all writes go directly to the HDD section, and of course you loose the advantage of total silence over SSD. I have development files stored on SSD, and every time I compile it's nice not to hear a HDD clicking away, you loose this benefit with hybrid.
As a prediction for years to come: When SSD's becomes cheaper to produce than HDD's (bound to happen some point) I reckon SSD drives will use the same technique employed here, where they use different speed flash memory. Cheaper slower flash memory for main capacity, and smaller but faster (more expensive) flash memory to intelligently move most regularly accessed files to.