Comments by "MrAbrazildo" (@MrAbrazildo) on "8 Design Patterns | Prime Reacts" video.

  1. 2:48, they just gave a name for a thing that has been made in C for decades: struct CheeseBurger { const char *ing_1, *ing_2, *ing_3 }; #define createCheeseBurger CheeseBurger { "bun", "cheese", "beef-patty" } And then call it by: CheeseBurger a_cheese_burger = createCheeseBurger; 5:20, this is a "lesser version" of C++ for 2 reasons: a) If 1 just wants to customize the initialization, C/C++ way is much better, as exposed above, due to compact syntax. b) If the goal is to customize it along the way, not only on initialization, it should has a control of which f() is allowed do that - and it seems that only C++ has this feature . Otherwise, all sorts of bugs can come from it, because everything will be public, which is the worst nightmare, depending on the project complexity. 10:57, why use an interface for that? Couldn't it be just a class? 16:00, again, why an interface? This thing is awkwardly slow! 21:00, and that's why f() programming < OO: the 1st lacks good facades. In C, you can let that memory management "encapsulated" away in a different file. But there are issues: a) Each file like this will be dedicated to each object, which hurts scalability. b) If only 1 generic file like this is created, then the user will has to keep traveling alongside with that array, which is exposed to dumb mistakes for long unnecessary time. It's still possible to create several macros, trying to hide that array exposure, but it's still a precary solution.
    1