I wanted to address that earlier, but I did not yet have the time to do so…
When I bought the last t3n I stumbled about a short article considering the “roadmap” of Neos and Flow.
In this article called “Neustart für Neos” @christianm states that Flow was primarily developed for the purpose of beeing the foundation for Neos, and explicitly not as an independent Framework for developing PHP-Applications.
This is really bothering me since then I have to admit. Me and my partner @saR are currently in the progress of developing a trimmed open-source alternative for tools like mailchimp and campaign monitor. And since Flow always has been advertised as an extremely flexible, secure and easy-to-use Framework for developing scalable enterprise-grade applications, that article really made us think, if we chose the “wrong” tool for what we have in mind.
Of Course, going with (the) flow seemed pretty reasonable, because a lot of paradigms we read about where default features of the Flow Framework and no one can take away the knowledge we gained about DDD, MVC and AOP.
Nevertheless, what I really want to know is:
Should we stick with flow or switch to something like Yii or Laravel?
Since we do have an MVC-based Application here, it wouldn’t be a big problem to switch the framework, since we can move the Domain-Model, Controller, Services and Views in a pretty “straight-forward” way.
If we stick with Flow, should we consider another Framework for our next Projects?
As I learned yesterday it really is a blast working with Flow and Neos Backend-Modules, but I’m pretty sure in a lot of scenarios we might not combine our Flow applications with a Neos site.
And if this tight integration is what the future for Flow brings, we really would like to know that for sure!
Best Regards and lots of love,
@chri____ and @saR