4 ms·

I am planning on adding this book to my wishlist, but I agree with the reviewer's note at the end: > My only criticism of the book is the naming of the styles.

I am planning on adding this book to my wishlist, but I agree with the reviewer's note at the end: > My only criticism of the book is the naming of the styles...In many cases, there are already establish names for the styles, but instead of using them, the author came up with her own. For example: Trinity instead of MVC, Things instead of Objects, Hollywood instead of Callbacks, Bulletin Board instead of Pub/Sub and Kick Forward instead of Continuation-passing. Those names are OK, but it is much better to stick to the industry standard ones. I'd definitely include this change in a 2018 edition, too.

kerkeslager 9y ago
MVC = Model View Presenter? Objects = Structs or Workers? Callbacks = Continuations? Pub/Sub = Observer pattern? Depending on what programming language background you come from, you may not use the "established" names either.
- barrkel 9y ago
  Generally speaking, solution to a terminology problem isn't to create terminology n+1.
  - kerkeslager 9y ago
    That depends what the terminology problem is. If the problem is that you're going to be criticized by a bunch of pedantic linguistic prescriptivists who want you to use their terms in the way they want, creating new terms avoids that criticism.
    - abiox 9y ago
      > avoids that criticism is that really important to avoid? and one is just gaining new criticisms in trade, no? and of course, going bespoke and inventing everything yet again has it's perks. maybe you'll get to be the person who "invented" a term, should it catch on. great for the resume. :)
  - dronescanfly 9y ago
    The good old: Oh look, there are n different services, but all of them have not completely nailed it and my specific use case is not covered. I'll create a new service that does all of the stuff the old services already did, aswell as this new thing, thus making the old n services obsolete. Everyone will be thankful for the unifying service and hail me for reducing the number of choices from n down to 1. That's how we ended up with n+1 different services.
- sobani 9y ago
  MVC is not MVP see also https://stackoverflow.com/questions/2056/what-are-mvp-and-mvc-and-what-is-the-difference https://stackoverflow.com/questions/2056/what-are-mvp-and-mv... Objects vs Structs - a struct is just a collection of data, while an object is a collection of data AND behavior (methods). Callback vs Continuation - I wouldn't expect a continuation to be called more than once, while I callback can. Pub/Sub vs Observer - with the observer pattern you register for updates directly on the object that is responsible for them, while with pub/sub there is a central component involved and you don't even need to know who originally published it. So no, for none of the examples you gave you can just replace one term with the other.
mdpopescu 9y ago
That was intentional, see [1] [1] https://youtu.be/Gw4WJJoDl3U?t=14m30s https://youtu.be/Gw4WJJoDl3U?t=14m30s
- faitswulff 9y ago
  So it seems like @kerkeslager's reasoning in a sibling comment was correct, that it ignited a naming war. That said, maybe a list of tags for the styles would help? "Also called: [functional, imperative]" etc.?
- always_good 9y ago
  Basically, she came up with her own names so that the examples could work stand alone without everyone bringing their "but to be called X it needs Y!" baggage and quibbling about it.

kerkeslager 9y ago

MVC = Model View Presenter? Objects = Structs or Workers? Callbacks = Continuations? Pub/Sub = Observer pattern? Depending on what programming language background you come from, you may not use the "established" names either.

barrkel 9y ago
Generally speaking, solution to a terminology problem isn't to create terminology n+1.
- kerkeslager 9y ago
  That depends what the terminology problem is. If the problem is that you're going to be criticized by a bunch of pedantic linguistic prescriptivists who want you to use their terms in the way they want, creating new terms avoids that criticism.
  - abiox 9y ago
    > avoids that criticism is that really important to avoid? and one is just gaining new criticisms in trade, no? and of course, going bespoke and inventing everything yet again has it's perks. maybe you'll get to be the person who "invented" a term, should it catch on. great for the resume. :)
- dronescanfly 9y ago
  The good old: Oh look, there are n different services, but all of them have not completely nailed it and my specific use case is not covered. I'll create a new service that does all of the stuff the old services already did, aswell as this new thing, thus making the old n services obsolete. Everyone will be thankful for the unifying service and hail me for reducing the number of choices from n down to 1. That's how we ended up with n+1 different services.
sobani 9y ago
MVC is not MVP see also https://stackoverflow.com/questions/2056/what-are-mvp-and-mvc-and-what-is-the-difference https://stackoverflow.com/questions/2056/what-are-mvp-and-mv... Objects vs Structs - a struct is just a collection of data, while an object is a collection of data AND behavior (methods). Callback vs Continuation - I wouldn't expect a continuation to be called more than once, while I callback can. Pub/Sub vs Observer - with the observer pattern you register for updates directly on the object that is responsible for them, while with pub/sub there is a central component involved and you don't even need to know who originally published it. So no, for none of the examples you gave you can just replace one term with the other.

mdpopescu 9y ago

That was intentional, see [1] [1] https://youtu.be/Gw4WJJoDl3U?t=14m30s https://youtu.be/Gw4WJJoDl3U?t=14m30s

faitswulff 9y ago
So it seems like @kerkeslager's reasoning in a sibling comment was correct, that it ignited a naming war. That said, maybe a list of tags for the styles would help? "Also called: [functional, imperative]" etc.?
always_good 9y ago
Basically, she came up with her own names so that the examples could work stand alone without everyone bringing their "but to be called X it needs Y!" baggage and quibbling about it.