henriquelimao

And this makes sense. They are counting the value paid per 1000 plays. If most of users in spotify are free, the average will be lower. Also, spotify has more plays than apple, so the final value paid might be higher.

Do you have a reference for that?

It is inside the app. It is the same process that you do to make playlists available offline. I only did that from my laptop to an android phone, I don't know if it works in all clients.

The song limit is really better in Apple, but you are able to add your own music in Spotify. To listen to it in other devices I had to download it in them.

It seems that in the end the initial function Post(ReservationRequestDto dto) has to call the tryAcceptComposition which has its dependencies hard coded there. So how exactly this solved the issue?

If you pass the dependencies as parameters in the tryAcceptComposition function, the Post would have to know its dependencies and we would be back to the initial state.

I would like to know the whole example he showed before using this model to see how this scale for more than one function.

It is not common, easy, efficient or idiomatic, but you can: Imagine that in each event handler, instead of doing something, you just update some state somewhere, and after that call a common "draw" function. Inside the "draw" function you redraw all your UI: apply effects, etc. That's it, you have it.