Browsers cannot parse jsx/tsx natively. Deno is transforming the code you write before it is executed in the browser. That transformation is typically referred to as a build step.
Building is creating the runnable artefact, but in the context of the server this artefact is already runnable, so I'd just call that "interpreting" the program
Not at all. We are talking about SSR, and the need for a build step (on the backend). That should be pretty obvious considering the explicit mentions of running the code in the browser, jsx, ts, etc. (Not to mention the backend runtime cannot run typescript/jsx without build either)
> Building is creating the runnable artefact
That's not all that 'building' is...
> but in the context of the server this artefact is already runnable
No it's not. The JIT/interpreter within Deno cannot run this code without doing a build first. This is made very obvious and explicit in the Deno docs.
https://docs.deno.com/runtime/fundamentals/typescript/
> With its built-in TypeScript compiler, Deno will compile your TypeScript code to JavaScript with no extra config needed.
Saying this doesn't have a build step is like saying a python script that compiles and runs a C program from source has no build step.
What I meant by "no build" is "no bundling". I elaborated more in this wiki: https://github.com/fullsoak/fullsoak/wiki/Concepts-&-Example...
Thank you for your help above in making things clearer <3
Hope that helps!
I'll take this to my desk & update the wordings towards your suggestions above - thank you!