The Go App Engine team is small. Right now our focus is on stability,
ease of use, improved API support, and bringing the Go runtime out of
"experimental" status. The features you've described are desirable but
are hardly core requirements, so it's unlikely we'll have the time for
work on such things for a while.
However, most of the stuff you describe here could be built on top of
the existing datastore API. If you're up for it, I would encourage you
to try implementing it yourself.
> - Alternate Datastore Column Names for fields
> - Functions for decisions: store/index this property?
These two are on our short-term roadmap already.
Can we have a compromise for the embedded types? I think many apps will have fields which are not primitive (num, bool, string, byte, key) or slice of it. If a field is not one of these but is exported, can the SDK store it as a Compressed gob? This way, the only limitation is that it cannot be queried upon, but it can be stored/retrieved and used in code. It's hard to build just this feature by itself without re-building most of the functionality that the SDK already provides.