@ Ismayil Khayredinov, I understand your frustrations with Elgg lagging behind when it comes to best practices. You have contributed a lot of work to Elgg core and even several plugins development. The truth is, several goals that have been set by you and several others to make the future Elgg superior suite like Laravel are completely achievable.

I think there are several community members here who should give their feedback. However, for this to be achieved we should go through 5 steps processes in order to change things that are holding back elgg from changing from old technology to future technology platform.

1. First we should learn what the Elgg issues are
2. Elgg community should then define the problems and which problems need clear answers
3. Then Elgg community should generate possible solutions for Elgg
4. Elgg community should abandon perfection and develop a plan and build Elgg
5. Finally, the elgg community members should continue testing and getting feedback from other Elgg community members and customers.

@ Ismayil Khayredinov, when I was reading your past post suggestion concerning "JS boilerplate and spaghetti code we have to write to achieve simple AJAXification" I was surprised that most of the community members sited time has an obstacle to achieve JS Framework.

I think the secret of making Elgg a better framework is within the posts and discussions on this community. It is our job as community members to search, read and try to implement those ideas in order for Elgg to grow.

For example 3 years ago on GitHub one of us tried to develop Laravel's controllers for elgg.

I honestly don't think the community has much to contribute to Elgg's future. It's a lot of discordant voices that all want a different thing. What we need is people like Michele, who invest time and funds to drive Elgg development based on real-life use cases. All the discussions that happened here in the past about the "future" ended up pissing off everyone on the core team and not resulting in anything constructive. What Elgg needs is people who don't talk much but do work and contribute actual code to core. We need people with vision who can translate it into code. I have the roadmap figured out in my head, but I am burned out and don't want to lead the way. I will put together my thoughts in a list, perhaps it might inspire someone.

The data directory must be specified from the root of the filesystem. E.g. /home/my_account/original.com/dataDir.