---
title: "Comment by fishbite on \"JavaScript Promise Chain - The art of handling promises\" | Hashnode"
description: "Hey Tapas, I first read some of your work on Synchronous vs Asynchronous JavaScript – Call Stack, Promises, and More synchronous-vs-asynchronous-in-javascript ,"
url: "https://hashnode.com/posts/javascript-promise-chain-the-art-of-handling-promises/610cc4d5b79d6a113667ebaa/comment/639251aa0771b6e5cf4a8fdb"
---

[Discussion](https://hashnode.com/posts/javascript-promise-chain-the-art-of-handling-promises/610cc4d5b79d6a113667ebaa)

Comment [JavaScript Promise Chain - The art of handling promises](https://hashnode.com/posts/javascript-promise-chain-the-art-of-handling-promises/610cc4d5b79d6a113667ebaa)

[fishbite](https://hashnode.com/@fishbite)

[Dec 8, 2022](https://hashnode.com/posts/javascript-promise-chain-the-art-of-handling-promises/610cc4d5b79d6a113667ebaa/comment/639251aa0771b6e5cf4a8fdb)

Hey Tapas, I first read some of your work on **Synchronous vs Asynchronous JavaScript – Call Stack, Promises, and More synchronous-vs-asynchronous-in-javascript**, which was enlightening on the underlying workings of the JavaScript engine. Thanks so much for that, it was the first time that anyone had explained that.

I was enjoying this post up until the point where you wrote the `fetch()` function at which point I was rather disturbed and momentarily discombobulated! Personally, I think you should rename that function (function getFakeAPI() lol!) because we have the fairly recently introduced **FetchAPI**

Just my 2 penny's worth :-P

...but thanks again, great post.

fishbite
