Видео

12:26 "you cannot use two workers to. handle the same request". Yes in this case you are right. What about with PHP ZTS? We can have multiple threads to achieve true parallelism. Any input on that?

This is really really insightful. Thanks!

great job pro

great job pro

thank you sir

How do you handle three levels of nesting

Great Content, friendly reminder, be careful with the empty space.

wouldn't this make the users table have multiple NULL columns for each type if they have different fields (other than the parent's one) ?

You have no idea what you're talking about

deletes my post...lol

yeah PHP suffers without "normal arrays"

Thank you!

Min 13:20 the class "UserSetthings" can be "final readonly class UserSetthings".

Brilliant explanation

Can't we use it with api?

I would probably do this only if the class is used more than 3-5 places, if it is less, always go for array for simplicity.

Brother excellent video!! It’s so good getting into the details. I appreciate how you make it digestible even for someone new like myself. Really helps the info stick.

Porque só vejo esse video hoje

Useless video no example nothing

Why didn't you just rerecord the video? I get an error message on your video before the error even comes up - I won't watch the video now! (that's advice)

Flowcharts are important to do before programming

Agreed

I found your channel because of STI. I'm hooked. Excellent how you get things working and show it, then move things from the child model to the parent and it's still working, then remove it to a trait. It demystifies what the packages do and that's really valuable. The depth of explanation is really thorough and the pacing works really well for me.

PHP 5.6?

Excellent video! What font do you use? It's awesome.

This is basically the datamapper pattern inside the activerecord pattern. Horrible. I really, really, really, really hate Eloquent and Laravel as a whole.

I would only add that, as a general rule, it should be understood that arrays are much more efficient in terms of memory and processing. Therefore, for any process that requires iterating over collections that can grow large, arrays should definitely be used, and objects should not be used at all. For maintainability, architecture definitely matters. Given the above, as a general rule, I would use objects as a means of communication between software components within the defined architecture, but the implementations for handling large data collections should be abstractions that use arrays behind the scenes. Let's say that algorithms, which need to be implemented correctly from the start and rarely modified, should definitely be implemented using arrays.

Great video. I've been using this approach a lot lately. How do you work when you have an attribute in UserSettings that must be set after the object creation and need to use it inside the notifyUser function? When do you check if the attribute was set or not? Thanks so much.

i do this on last my project, for Entities in laravel implemented clean architecture. and very helpful for maintaince data return from services and repositories

what if i want to early exit from say the 2nd pipe and skip the rest of the pipes?

Well this is not a array. An array is one data type. When you are putting in different data types it's more a data container or table.

Video title is misleading. A handy solution when it come to simple read-only operations sure, but it is by no means an "alternative" to the arrays. Think about what you can achieve with arrays when it comes to data manipulation and processing. Not to mentioned numerus PHP's build in and custom-tailored functions to process data.

Years of writing PHP, and i still learnt something new today, thanks lad.

Cool do more PHP videos and courses.

What you call arrays in other languages is actually vectors if you are coming from an actual programming language.

Yeah, I do this all the time. Makes refactoring much less stresfull. Also, using Propel ORM for the sam reaoson. It allows you to change the database schema without having to worry that code will break. Too bad worse ORM solutions like Eloquent are more popular than Propel. I guess PHP developers suck.

It is Value objects ?

One (still) useful usage of array is a pseudo Tuple: function doSomething(){ if (somethingWentWrong()){ return [null, new SomeBusinessException()] } return [SomeDto, null]; } function someConsumer(){ [$data, $error] = doSomething(); // } A pseudo Result<T> monad, but until PHP had generic, Tuple will have to suffice

Of course this is good approach to replace assoc arrays with objects, but it would be nice to see such approach in framework configurations instead of arrays/yaml files.

laravel throws errors when you access a key that isn't set i thought that was the default behaviour, maybe i don't know php that well

this has become a LOT more relevant since PHP introduced constructor-defined readonly properties. Creating value objects, DTOs whatever is now pleasant and elegant.

Thats solid principles applied into php. Thats awesome!

It had never occurred to me to treat arrays as objects.

This is all dependable on the context... good thing for complicated data but overkill for some simple data... Generally the video is a good hint about what can you do in PHP as a programming language. "Chose your 'weapons' wisely!"

The timing for this video couldn't be better as I was literally talking about these exact points yesterday with my team. Great content man, kudos from Brazil! Also it was awesome to see u on Laracasts as well 🤩 Parabéns meu bom

Nice video, what if we have numbers of array elements like current_period and previous_period, is it good to pass on constructor ? ruclips.net/video/7g8WCApiz04/видео.html

Honestly, I'm quite baffled that PHP devs don't use classes more. "We need to pass an array to this function" okay, so use get_object_vars? Create a toArray method? The good thing about having a class is that you can add default values to the state and easily create a copy of it, along with a strict schema to follow.

your username in comments doesnt render. wtf?

By far the biggest thing to be aware of with Swoole is that if your code encounters an error, the entire worker has to be restarted, which kills all requests that it had been handling concurrently at that time. In FPM, just that request is affected. You have to be a LOT more defensive with your code in Swoole, which can be difficult sometimes due to PHP's ancient error model.

Mateus, I didn't watch the whole video, but it appears you're trying to do what the *spatie/laravel-data* package does, just take a look a it