# One does not simply extend Promise **URL:** \ **Category:** Spec Reading\ **Created:** [March 3, 2023, 8:37am UTC](https://es.discourse.group/t/one-does-not-simply-extend-promise/1627 "2023-03-03T08:37:13Z")\ **Posts on this page:** 1\ **Showing post:** 15
**Author:** ![WebReflection](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/webreflection/32/248_2.png) [@WebReflection](https://es.discourse.group/u/WebReflection)\ **Post date:** [March 3, 2023, 7:40pm UTC](https://es.discourse.group/t/one-does-not-simply-extend-promise/1627/15 "2023-03-03T19:40:24Z")
[this reply](https://es.discourse.group/t/one-does-not-simply-extend-promise/1627/13) explains my concerns which, at this point, are all around `.then(callback)` or even `.catch(callback)` specifications. To put it in daily words, imagine we start an email conversation, and every time there's a followup the initial email is not just embedded as beginning of the conversation, is presented as intermediate _reset_ of such conversation, as if no _follow up_ (then) discussions happened in between ... that is: every time a _follow up_ comes after, you get to re-read, re-answer, re-execute, the beginning of the conversation, even if it moved to other topics, as that's what a `.then(doStuff)` is supposed to do ... Do you find this mental model helpful for anything at all? Can you please show me a single use case where the current state around `.then` promises is desired? Thanks! --- _[View the full topic](https://es.discourse.group/t/one-does-not-simply-extend-promise/1627)._