3 ms·

Yeah? Have you measured it? Aside from that, do you have anything meaningful to say about the points actually raised? Let's take your claim as a given. If i

by cxr 3y ago

Yeah? Have you measured it? Aside from that, do you have anything meaningful to say about the points actually raised? Let's take your claim as a given. If it were 2003 instead of 2023 and people kept bringing up, say, problems with Windows but refused to speak about them in those terms—instead insisting on framing with a generalization about "computers"—would that have been acceptable on the basis that 90+% of the world is using Windows? It plainly wouldn't have, and that's true for a case where we actually know that we were dealing with numbers of 90% or more, and not just lazy attempts at retorts that are fired from the hip and by a reasonable guess probably won't actually hold up under scrutiny, anyway.

troupo 3y ago
> Aside from that, do you have anything meaningful to say about the points actually raised? You didn't raise points. You went off on a rant by completely dismissing the tongue-in-cheek article about tooling issues in the frontend space as something about "node-only". All the points the author raised are: - about frontend aka client-side - about javascript ecosystem And this ecosystem is ubiquitous. Much more ubiquitous than "no, this is not frontend, I do client-side and I don't use it". > If it were 2003 instead of 2023 and people kept bringing up, say, problems with Windows but refused to speak about them in those terms—instead insisting on framing with a generalization about "computers" See? This is not a point. This is argument by analogy. You're pretending that this analogy is valid (it isn't) and you're expecting me to argue with you.
- cxr 3y ago
  > this ecosystem is ubiquitous I wrote a perfectly lucid response which you ignored completely. Your choosing to ignore it, or to read it as if it means something other than what it does, does not mean that I don't have a point (wat). > Much more ubiquitous than "no, this is not frontend, I do client-side and I don't use it". Who are you quoting (and what is it even supposed to mean, besides)? > you're expecting me to argue with you Nope.
  - troupo 3y ago
    > I wrote a perfectly lucid response which you ignored completely. I wrote why, and you definitely literally ignored what I wrote. > Who are you quoting (and what is it even supposed to mean, besides)? I'm very shortly representing what you wrote. So it's for you to answer what this means. > Nope Yup. Otherwise you wouldn't resort to bad analogies. Anyway. This is going nowhere. Adieu.
    - cxr 3y ago
      > I'm very shortly representing what you wrote. No, you aren't—and the point at which you are attempting to explain what it is that I really meant or was thinking (explaining me... to me) is the point at which you have stumbled upon a strong indicator that you have lost the plot. Viz: > Yup [you are expecting me to argue with you]

by cxr 3y ago

troupo 3y ago

> Aside from that, do you have anything meaningful to say about the points actually raised? You didn't raise points. You went off on a rant by completely dismissing the tongue-in-cheek article about tooling issues in the frontend space as something about "node-only". All the points the author raised are: - about frontend aka client-side - about javascript ecosystem And this ecosystem is ubiquitous. Much more ubiquitous than "no, this is not frontend, I do client-side and I don't use it". > If it were 2003 instead of 2023 and people kept bringing up, say, problems with Windows but refused to speak about them in those terms—instead insisting on framing with a generalization about "computers" See? This is not a point. This is argument by analogy. You're pretending that this analogy is valid (it isn't) and you're expecting me to argue with you.

cxr 3y ago
> this ecosystem is ubiquitous I wrote a perfectly lucid response which you ignored completely. Your choosing to ignore it, or to read it as if it means something other than what it does, does not mean that I don't have a point (wat). > Much more ubiquitous than "no, this is not frontend, I do client-side and I don't use it". Who are you quoting (and what is it even supposed to mean, besides)? > you're expecting me to argue with you Nope.
- troupo 3y ago
  > I wrote a perfectly lucid response which you ignored completely. I wrote why, and you definitely literally ignored what I wrote. > Who are you quoting (and what is it even supposed to mean, besides)? I'm very shortly representing what you wrote. So it's for you to answer what this means. > Nope Yup. Otherwise you wouldn't resort to bad analogies. Anyway. This is going nowhere. Adieu.
  - cxr 3y ago
    > I'm very shortly representing what you wrote. No, you aren't—and the point at which you are attempting to explain what it is that I really meant or was thinking (explaining me... to me) is the point at which you have stumbled upon a strong indicator that you have lost the plot. Viz: > Yup [you are expecting me to argue with you]