4 ms·

Yes, ok. But this doesn't say it's a bad tool? Only a not very used tool? (I know that you've not claimed neither; only that is not a very used tool)

pwg 7y ago
It would give you specific data to use for your initial hypothesis: "I am sure there are quite a few who know this gnu-tool" My hypothesis is that you will find that instead of "quite a few who know" (implying a large value and/or majority) that if you start asking you will find that reality is "very few even know" and an even smaller subset of those very few actually utilize.
- claes-magnus 7y ago
  It is very hard to estimate such matters when you're a junior developer. :) Say you're right. Actually, I don't doubt you. I am certain that I will find I was wrong when I wrote that. But still, this does not mean sed is not a tool worth learning and I am very greedy in such contexts. I love learning. And in some contexts, it seems very reasonable to use sed (and awk) rather than js, python or a 'richer' language?
  - pwg 7y ago
    You are reading in something I never said. This is what you are reading in: "this does not mean sed is not a tool worth learning" I never said, nor implied, that. None of my prior responses have said whether sed is worth, or not worth, learning. My responses were focused only on your initial hypotheses that implied a large number know of it. My hypotheses is if you actually test your statement within your JS dev. groups, you'll find a shockingly low number of members who even know sed exists. Now, as for my opinion of sed, it is a fine tool, and it is well work knowing how to use it (at the very least knowing how to use it for its most common usage, replacing strings with other strings). I myself reach for it quite often when I need to do something that it is good at doing. And, yes, for you, it is well worth learning something about it. It is also well worth you learning something about many of the other CLI tools, such as head, tail, join, comm, seq, etc. There are a huge number of them, and they can often allow you to solve a problem without ever writing a single line of code (unless you consider a Unix pipeline to be 'code').
    - claes-magnus 7y ago
      I wrote, >> Yes, ok. But this doesn't say it's a bad tool? Only a not very used tool? (I know that you've not claimed neither; only that is not a very used tool) But since you continued to stress your hypothesis and ignored this, I (incorrectly) presumed you had another agenda. I misinterpreted you, and I am thankful for you sharing knowledge on the other stuff. :) Sorry! This is exactly what I am beginning to realize: >> hey can often allow you to solve a problem without ever writing a single line of code (unless you consider a Unix pipeline to be 'code' Therefore it is very valuable for me when someone who obviously have greater knowledge points this out. Thanks! This was also my point with my project: a demonstration aiming to show that we didn't need JS, but only a few lines of sed. :)

pwg 7y ago

It would give you specific data to use for your initial hypothesis: "I am sure there are quite a few who know this gnu-tool" My hypothesis is that you will find that instead of "quite a few who know" (implying a large value and/or majority) that if you start asking you will find that reality is "very few even know" and an even smaller subset of those very few actually utilize.

claes-magnus 7y ago
It is very hard to estimate such matters when you're a junior developer. :) Say you're right. Actually, I don't doubt you. I am certain that I will find I was wrong when I wrote that. But still, this does not mean sed is not a tool worth learning and I am very greedy in such contexts. I love learning. And in some contexts, it seems very reasonable to use sed (and awk) rather than js, python or a 'richer' language?
- pwg 7y ago
  You are reading in something I never said. This is what you are reading in: "this does not mean sed is not a tool worth learning" I never said, nor implied, that. None of my prior responses have said whether sed is worth, or not worth, learning. My responses were focused only on your initial hypotheses that implied a large number know of it. My hypotheses is if you actually test your statement within your JS dev. groups, you'll find a shockingly low number of members who even know sed exists. Now, as for my opinion of sed, it is a fine tool, and it is well work knowing how to use it (at the very least knowing how to use it for its most common usage, replacing strings with other strings). I myself reach for it quite often when I need to do something that it is good at doing. And, yes, for you, it is well worth learning something about it. It is also well worth you learning something about many of the other CLI tools, such as head, tail, join, comm, seq, etc. There are a huge number of them, and they can often allow you to solve a problem without ever writing a single line of code (unless you consider a Unix pipeline to be 'code').
  - claes-magnus 7y ago
    I wrote, >> Yes, ok. But this doesn't say it's a bad tool? Only a not very used tool? (I know that you've not claimed neither; only that is not a very used tool) But since you continued to stress your hypothesis and ignored this, I (incorrectly) presumed you had another agenda. I misinterpreted you, and I am thankful for you sharing knowledge on the other stuff. :) Sorry! This is exactly what I am beginning to realize: >> hey can often allow you to solve a problem without ever writing a single line of code (unless you consider a Unix pipeline to be 'code' Therefore it is very valuable for me when someone who obviously have greater knowledge points this out. Thanks! This was also my point with my project: a demonstration aiming to show that we didn't need JS, but only a few lines of sed. :)