On spdy-dev they considered adding SNI to the spec as a requirement but didn't:
https://groups.google.com/forum/?fromgroups#!topic/spdy-dev/...
(At this point implementing SPDY without SNI would be kind of absurd, but it would be spec-conforming.)
Yes you are so correct.
SPDY is for the future.
Getting a SSL certificate is not a big issue and not too costly. And for blogs and simple websites SPDY adds less. So don't implemmnt it.
So why anyone needs to worry?
Android browser supports SPDY but doesn't support SNI.
Granted, it does nothing for your older non-SNI browsers, but they won't be speaking SPDY or HTTP/2.0 or whatever it winds up being called.
http://en.wikipedia.org/wiki/Server_Name_Indication