Translations across large numbers of objects, create performance issues

[kirkbushell]

Due to the nature of converting eloquent model objects to translated entities and collections, it's currently quite an expensive operation (in PHP) to do this, as well as providing all translated values.

This is both an open discussion and issue to help generate a dialog of how best to approach this problem whilst maintaining the SQL performance that this package provides (all translations for all nested objects are done in one query).

This may possible include some API changes, which is why the issue is marked for version 2.0.

[kirkbushell]

@valorin feel free to contribute here, as well - as your input and knowledge is quite in-depth regarding the package :)

[kirkbushell]

I think as a starting point, the base repository probably shouldn't use eloquent objects, but rather do a straight db query and work with stdClasses. In this manner, the number of expensive objects will be vastly reduced, as it doesn't need to do all the hydration work.

[kirkbushell]

This may have been resolved (at least in part), by #3