---
title: "Comment by Bob Jones on \"Pure vs Impure Functions\" | Hashnode"
description: ""As you all know that JavaScript is synchronous, using console or any callback or promise/fetch will make the function asynchronous." Using console do"
url: "https://hashnode.com/posts/pure-vs-impure-functions/62833c6f504da209d8557134/comment/6285cc0983966a1653f13ab1"
---

[Discussion](https://hashnode.com/posts/pure-vs-impure-functions/62833c6f504da209d8557134)

Comment [Pure vs Impure Functions](https://hashnode.com/posts/pure-vs-impure-functions/62833c6f504da209d8557134)

[Bob Jones](https://hashnode.com/@crazy4groovy)

[May 19, 2022](https://hashnode.com/posts/pure-vs-impure-functions/62833c6f504da209d8557134/comment/6285cc0983966a1653f13ab1)

"As you all know that JavaScript is synchronous, using console or any callback or promise/fetch will make the function asynchronous."

Using console doesn't make the function asynchronous. It may likely make it technically impure though (although it doesn't affect the idempotency of the function either, so that's debatable). To be clear, a function that calls another function can still be a pure function.