I work at a hw vendor that builds android for our SoC and we're still on N, but it's not because we're resistant to adoption of treble. Treble has been more li

I work at a hw vendor that builds android for our SoC and we're still on N, but it's not because we're resistant to adoption of treble. Treble has been more like the straw or boulder to break the camels back. Not only is it a lot of work on its own, it has also triggered a bunch of refactoring. People are actually excited about Treble and how it should make kernel and android updates easier in the future. It's just a lot of work in the short term.