Maglev is a persistent, distributed runtime - there's a virtual object space which is accessible from many VMs across many machines, and is transactionally pers

Maglev is a persistent, distributed runtime - there's a virtual object space which is accessible from many VMs across many machines, and is transactionally persisted to disk. So it's not so much that there's an incompatibility (you could use normal ActiveRecord from Maglev) as that it provides a better integrated alternative. What's being discussed here is to what degree this integrated alternative should present an API compatible with ActiveRecord.