moving away from Sling, Jackrabbit, Felix

Shouldn't ADEP move away from Sling, Jackrabbit, and Felix, and Java in general?

From my experience with Day CQ stack is that:

1. Felix is unstable.
   1. Or, developers have to be careful when writing OSGi bundles.
   2. Why would you have to have running felix instance before you can deploy OSGi bundle?
   3. What if the server if busy?
   4. OSGi hotswapping is very very difficult problem.Probably it needs language implementation level support to get it right.
2. Jackrabbit is unstable.
   1. really unstable.
   2. TarPM optimization deletes data tar.
   3. admins have to manually run datastore garbage collection.
   4. needs a lot of attention from sysadmins.
3. Jackrabbit is hierarchical.
   1. hierarchical database...
   2. name data that can fit hierarchical structure.
4. Sling is lols
   1. you store code, data, in repo.
   2. you comple jsp in the server hahahahahahhaah.
   3. exposes data by default.
   4. hairy script resolution.
   5. ad hoc script/template "inheritance"
   6. mixing data structure and representation.
   7. bound to JCR. cannot use relational database as persistence.
   8. applicatino and data are bound.. vendor locking alert.