8 ms·

Our tooling is written in Node.js. So developers must have Node installed on their machines to utilize our tooling. When they use our CLI to watch the file sys

Our tooling is written in Node.js. So developers must have Node installed on their machines to utilize our tooling. When they use our CLI to watch the file system for changes for live-reload or to build their extension, etc., that's a Node.js program. The build target is browser Javascript, though.

cxr 4y ago
> Our tooling is written in Node.js. Sure. My question is why.
- ghotli 4y ago
  Surely you are trolling? That's a very, very common setup. Nothing complicated or out of the ordinary requiring specific tooling for the dev environment. The output that runs in the browser at runtime has its own set of same constraints. Modern browser version, etc.
  - cxr 4y ago
    > Surely you are trolling? First of all, don't do that. It's obnoxious. Secondly: > That's a very, very common setup. So? Falling back on the argument that, essentially, "lots of people do this" is about as worthy as attempting to counter by saying that the other person/what they are doing is weird[1]. (It's actually slightly more respectable, but that's only because of how unrespectable the call-them-a-weirdo path is.) You either have an argument for $THING that will hold up under scrutiny without appealing to how weird/anti-weird $THING is, or you don't. Thirdly, you are not compelled to comment. (What makes your decision to join in even more mystifying is that you were not the person being addressed—at least their impulse to do so would have made sense, even if the argument was still a bad one.) If you don't actually have an answer, why bother commenting at all? 1. https://news.ycombinator.com/item?id=30721113 https://news.ycombinator.com/item?id=30721113
- httgp 4y ago
  Why not?
  - cxr 4y ago
    You mean aside from everything I already said? ("But why male models?")
- cuylerstuwe 4y ago
  It’s a norm for frontend devs to build CLI tools in the language/evironments/ecosystems they’re most familiar with.
  - cxr 4y ago
    That's an interesting way to respond, given the context. NodeJS doesn't run on the frontend, so your argument here would be an even _stronger_ reason to favor using Chrome as your runtime...

cxr 4y ago

> Our tooling is written in Node.js. Sure. My question is why.

ghotli 4y ago
Surely you are trolling? That's a very, very common setup. Nothing complicated or out of the ordinary requiring specific tooling for the dev environment. The output that runs in the browser at runtime has its own set of same constraints. Modern browser version, etc.
- cxr 4y ago
  > Surely you are trolling? First of all, don't do that. It's obnoxious. Secondly: > That's a very, very common setup. So? Falling back on the argument that, essentially, "lots of people do this" is about as worthy as attempting to counter by saying that the other person/what they are doing is weird[1]. (It's actually slightly more respectable, but that's only because of how unrespectable the call-them-a-weirdo path is.) You either have an argument for $THING that will hold up under scrutiny without appealing to how weird/anti-weird $THING is, or you don't. Thirdly, you are not compelled to comment. (What makes your decision to join in even more mystifying is that you were not the person being addressed—at least their impulse to do so would have made sense, even if the argument was still a bad one.) If you don't actually have an answer, why bother commenting at all? 1. https://news.ycombinator.com/item?id=30721113 https://news.ycombinator.com/item?id=30721113
httgp 4y ago
Why not?
- cxr 4y ago
  You mean aside from everything I already said? ("But why male models?")
cuylerstuwe 4y ago
It’s a norm for frontend devs to build CLI tools in the language/evironments/ecosystems they’re most familiar with.
- cxr 4y ago
  That's an interesting way to respond, given the context. NodeJS doesn't run on the frontend, so your argument here would be an even _stronger_ reason to favor using Chrome as your runtime...