4 ms·

> JavaScript interpreter you can run outside the browser. You're moving the fencepost. This thread is about how to render composable HTML components. Why do y

> JavaScript interpreter you can run outside the browser. You're moving the fencepost. This thread is about how to render composable HTML components. Why do you need to run a JavaScript interpreter to do that? You just need an HTML interpreter. We do have JavaScript and that interpreter is the web browser. By your logic that the interpreter should be in the same language as the stuff being interpretted, why are we using JavaScript to interpret HTML? My original criticism was also about the dependency hell/culture around the Node ecosystem, moreso than Node’s capabilities as an interpreter.

nawgz 4y ago
> This thread is about how to render composable HTML components I quite literally joined the fray in response to a question that asked: "how do you add JavaScript to your web bundle?" To me, it would be appropriate to say: "the class of JavaScript we can easily support in this app must be exclusively browser-testable, and we ignore DX-style features JS devs expect as our app just rebuilds and reloads quickly" > why are we using JavaScript to interpret HTML? Who is doing that? We're using JavaScript to have dynamic HTML updates client-side, but calling that "interpreting" is hilarious. > My original criticism was also about the dependency hell/culture around the Node ecosystem, moreso than Node’s capabilities as an interpreter. Which makes it even more strange that you basically took a fat shit on Node.js with no expansion [0] [0]: > How do you plan to add JS to your Go web app? This is what I mean by Node.js being a hammer and everything looks like a nail. You don’t need Node.js to write JavaScript.