استاذ محمد .. قبل كل شي بصراحه جدا فخور بجهودك لتطوير اللارفل .. هناك طلب دائم على المحتوى العربي .. فلماذا لا تكون انت صاحب المحتوى العربي الخاص بلارفل و العمل على فيديوهات بالعربي لدعم الحتوى وسد حاجه المبرمجين العرب
how is this code different Flight::where('departed', true)->lazy(100) than Flight::where('departed', true)->limit(100)->paginate() ? i guess both will 100 items in chunk
Flight::lazy(100) gets all the flights in chunks of 100, limiting memory usage. Flight::paginate(100) will get you one chunk with 100 flights, but not all the flights. Let's say you need all the flights for a calculation and want to limit memory usage during that calculation, then lazy() could be of help. If you just want to get 100 flights and return them for use in a view, for instance, use pagination.
I hate the new way of writing Atributes. The code handling atrributes u'r showing is too short to be representative. Even with the code related to addresses, code itself start to look very strange. The old getter/setter method is really clean and easier to learn/understand and maintain. What's getting me upset from some new advanced features that are being added to Laravel is that it's becoming more and more cryptic, using all PHP permited and all "tricks" with arrays, keys, indirect calls to methods, ... What led me to Laravel is that contrarily to Symphony, it had clean and simple implementation not dealing on cryptic config files and YAML stupid descriptions. Laravel is slowly adding more and more cryptic way of implementation of features and this is a pitty.
It’s always exciting to see the brisk pace of improvements and evolution of Laravel.
Good work on the video, Mohamed!
the quality is getting better and better ... and nice shirt Mohamed :D
i agree...i love to see it!!!
I appreciate the attention to visual detail.
It is showing through to me.
I like the new way to set accessors and mutators, really clean and feels like less magic.
That transformation of accessors and mutators is so dope
I like the previous syntax, it is more readable
@@dibbyo456 i prefer this one though it's far more cleaner and easier to read for me
Love the new attribute methods
That's my favorite ✨
Its been 9 years Its because of laravel i still use PHP
استاذ محمد .. قبل كل شي بصراحه جدا فخور بجهودك لتطوير اللارفل .. هناك طلب دائم على المحتوى العربي .. فلماذا لا تكون انت صاحب المحتوى العربي الخاص بلارفل و العمل على فيديوهات بالعربي لدعم الحتوى وسد حاجه المبرمجين العرب
MashaAllahh very good explanation, thanks for updated us on Laravel.
This is dope, I love Laravel
🔥
👌
great video!
thank you for you good content 🙏
Please make tutorial on Laravel octane
what is mutex? thanks
how is this code different Flight::where('departed', true)->lazy(100) than Flight::where('departed', true)->limit(100)->paginate() ? i guess both will 100 items in chunk
Flight::lazy(100) gets all the flights in chunks of 100, limiting memory usage. Flight::paginate(100) will get you one chunk with 100 flights, but not all the flights. Let's say you need all the flights for a calculation and want to limit memory usage during that calculation, then lazy() could be of help. If you just want to get 100 flights and return them for use in a view, for instance, use pagination.
I hate the new way of writing Atributes. The code handling atrributes u'r showing is too short to be representative. Even with the code related to addresses, code itself start to look very strange. The old getter/setter method is really clean and easier to learn/understand and maintain. What's getting me upset from some new advanced features that are being added to Laravel is that it's becoming more and more cryptic, using all PHP permited and all "tricks" with arrays, keys, indirect calls to methods, ... What led me to Laravel is that contrarily to Symphony, it had clean and simple implementation not dealing on cryptic config files and YAML stupid descriptions. Laravel is slowly adding more and more cryptic way of implementation of features and this is a pitty.