Hi!

Imagine a youtube video player.

The relation between the play button and the player itself is a composition — the play button doesn't make sense outside of the player.

Now, imagine a playlist with a bunch of players. The relation between each player and the playlist itself is an aggregation — a player can both exists independently or as part of a playlist.

Hi!

Yes, the book has been recently translated into Korean as well.

Yes, that's correct, stars mean popularity by the most accurate metric I have — my experience (lol). However, until today, there were some glitches in the Korean version, and the stars didn't appear there correctly, maybe that was a source of confusion.

Thanks a lot for your feedback! I'm glad that you liked my work!

Thank you! I'm glad that you like it!

Hi! Thank you for the idea. I'll consider it when Apple makes the fees more reasonable.

Hi all!

We are actually very close to releasing the Korean 1.0 release. At this stage, I would be glad to get some early feedback from real users. If you have a few hours of spare time to participate in the beta review, please send me an email to support@refactoring.guru and I'll send you the detailed instruction on how to proceed.

Радий, що вам сподобалось, Вадиме!

Hi Daniel!

Thank you for asking!

1. Yes, I think it indeed violates SRP because both of these features can be implemented independently (at least, in many OOP languages).

2. Practically speaking, I personally don't care that much about following SRP. To me, SRP is just one of the indicators of the design. Still, as an author, I can't ignore this issue completely because I'd get backfire from the opposite camp. In any case, if I could do my thing efficiently while violating SRP, I would definitely do it. If it bites me in the future, I will refactor it away.

BTW, if anyone reading this topic wants to add something to the discussion, you're very welcome!

Thank you for your feedback!