Knowledge i guess?why ppl waste their time makign completely new accs?
gesior is great and really just give us some extra cool features instead of wasting ur time on a completely new acc that no1 will bother using
Show me acc. maker that uses less SQL queries with same functionality. Smoother? No way.
Lazy loading? Gesior also got lazy loading.
How many queries would generate Laravel when you try to load 'all players, their skills from other tableand their accounts, ordered by skill'. Show me framework that does it by 1 query and offers OOP
Of course you can just write query as I did in Gesior [or create view in database], but then it's not OOP.
Both obviously have their advantages and disadvantages, but dismissing Laravel, or any other framework for that matter, because you aren't aware of how they work is ludicrous. As @Cornex mentioned, Laravel in this case, offers eager loading for queries, which eliminates the n+1 issue that I'm assuming you're refering to. Sure, for every relationship it adds another query, so effectively you could end up with 1, 2 or 3 queries, yes, but that is just by using one method. You can easily create more advanced queries and limit it to 1 query, whether it is by raw queries or by their query builder. Anything you can create through your own framework, I can also do through Laravel. It just offers more convenient ways to do it and whether you decide to use it or not is entirely up to you. There are most likely speed performance gains to benefit from by not using a framework, yes, but even then, it's most of the time not something you would even notice.Show me acc. maker that uses less SQL queries with same functionality. Smoother? No way.
Lazy loading? Gesior also got lazy loading.
How many queries would generate Laravel when you try to load 'all players, their skills from other tableand their accounts, ordered by skill'. Show me framework that does it by 1 query and offers OOP
Of course you can just write query as I did in Gesior [or create view in database], but then it's not OOP.
I think that frameworks are good for big projects, but problem is that you must update your program to make it compatible with current version of framework. Which is not good for small projects with 1-2 developers [acc. maker]. If they got no time to update [things that are not related to their software, they update bacause framework updates!], their software get outdated and people can't use it.Both obviously have their advantages and disadvantages, but dismissing Laravel, or any other framework for that matter, because you aren't aware of how they work is ludicrous. As @Cornex mentioned, Laravel in this case, offers eager loading for queries, which eliminates the n+1 issue that I'm assuming you're refering to. Sure, for every relationship it adds another query, so effectively you could end up with 1, 2 or 3 queries, yes, but that is just by using one method. You can easily create more advanced queries and limit it to 1 query, whether it is by raw queries or by their query builder. Anything you can create through your own framework, I can also do through Laravel. It just offers more convenient ways to do it and whether you decide to use it or not is entirely up to you. There are most likely speed performance gains to benefit from by not using a framework, yes, but even then, it's most of the time not something you would even notice.
In fact, I would argue that if anything, the small speed difference might be the only benefit of using your own custom framework (not saying you shouldn't create your own stuff, it's great, but dismissing other frameworks because of non-issues is a different matter). Whereas by using a larger framework, such as Laravel, everything has been tested by thousands of people, it is proven to work, whereas yours may have been tested only by yourself locally. It also offers a sense of consistency throughout rather than having a bunch of loose files laying about, and each and every one of them work a little bit differently. Do I even need to mention the existence of documentation? There are so many more benefits to using a framework, and in my mind, they all outweigh the slight speed differential.
With that said, I am in no way bashing you or your AAC, I think what you've done for this community is great, but I do not agree with your reasoning in this matter.
how is the project?
cara, use inglês como sua linguagem, aqui é um forum inglês ...@eduardojuniosm quando vai ficar pronto amigao ?
Hello guys!
The project is stopped for a moment while I upgrade myself to the new features of PHP 5.6, and PHP 7. I'm reading this book now Modern PHP: New Features and Good Practices, most likely I'll not use Laravel anymore, let's keep it simple, with Git, Bootstrap 4 (responsive), some nice components from Packagist, nice documentation, good practices (PSRs, programming to interfaces) and a good security. This will be a nice way to put in practice the new knowledge that I'm getting.
Sorry the late for updates. XD
Hello guys!
The project is stopped for a moment while I upgrade myself to the new features of PHP 5.6, and PHP 7. I'm reading this book now Modern PHP: New Features and Good Practices, most likely I'll not use Laravel anymore, let's keep it simple, with Git, Bootstrap 4 (responsive), some nice components from Packagist, nice documentation, good practices (PSRs, programming to interfaces) and a good security. This will be a nice way to put in practice the new knowledge that I'm getting.
Sorry the late for updates. XD
When I can download this ACC? Great style "shadowcores" NICEProject update: "Looks like shadowcores" - problem?