---
title: "Comment by Chirag Chhajed on \"JS perfs tooling that came in clutch\" | Hashnode"
description: "Really helpful 🙌🏽🙌🏽"
url: "https://hashnode.com/posts/js-perfs-tooling-that-came-in-clutch/678f2e4af155cc1e68a92a27/comment/678f362cf155cc1e68a92a56"
---

[Discussion](https://hashnode.com/posts/js-perfs-tooling-that-came-in-clutch/678f2e4af155cc1e68a92a27)

Comment [JS perfs tooling that came in clutch](https://hashnode.com/posts/js-perfs-tooling-that-came-in-clutch/678f2e4af155cc1e68a92a27)

[Chirag Chhajed](https://hashnode.com/@chiragchhajed)

[Jan 21, 2025](https://hashnode.com/posts/js-perfs-tooling-that-came-in-clutch/678f2e4af155cc1e68a92a27/comment/678f362cf155cc1e68a92a56)

Really helpful 🙌🏽🙌🏽

[Ishan Jain](https://hashnode.com/@ishanJain)

[Jan 21, 2025](https://hashnode.com/posts/js-perfs-tooling-that-came-in-clutch/678f2e4af155cc1e68a92a27/comment/678f362cf155cc1e68a92a56#reply-678f368f646a2b14da776fd8)

thanks, any particular point that you really liked, was new to you? or would love to know more about?

[Chirag Chhajed](https://hashnode.com/@chiragchhajed)

[Jan 21, 2025](https://hashnode.com/posts/js-perfs-tooling-that-came-in-clutch/678f2e4af155cc1e68a92a27/comment/678f362cf155cc1e68a92a56#reply-678f7d1f991fc6e443581971)

[Ishan Jain](https://hashnode.com/@ishanJain) I had read this book called You don't know JS part 1 i guess a while back.

It has these points, like JS is neither interpreted nor compiled. From the book it was `A long-debated question for code written in JS: is it an interpreted script or a compiled program? The majority opinion seems to be that JS is an interpreted (scripting) language. But the truth is more complicated than that.`

Then it had something around the JS flow: \`So what do these nitty-gritty details boil down to? Step back and consider the entire flow of a JS source program:

1.  After a program leaves a developer’s editor, it gets transpiled by Babel, then packed by Webpack (and perhaps half a dozen other build processes), then it gets delivered in that very different form to a JS engine.
2.  The JS engine parses the code to an AST.
3.  Then the engine converts that AST to a kind-of byte code, a binary intermediate representation (IR), which is then refined/converted even further by the optimizing JIT compiler.
4.  Finally, the JS VM executes the program.\`

It was nice to comeback at this stuff for a revision
