Since @terdon is trying to spin it using mendacious allusions and ridiculous percentages, here is the reality about my comments.
They were 3 incidents, and 5 messages in total. No more, no less.
I'll try to reproduce them from memory, since I didn't take any screenshots. My comments are in blockquotes. Any suggestions that they were essentially different from this, or there were other "rude" comments of mine are LIES.
If you think they're noise, I heartily agree with you. But the answers they were attached to were/are much worse. I hope that the spam/sockpuppet voting problem in this "community" will be fixed one day and its enablers removed, but I'm personally too disgusted to continue. This is the last message I post here.
1.
The first comment, the one containing the "garbage" outburst, was borne out of frustration, after @goro was peddling for the 4th or 5th time the same non-working awk
script, supposed to parse .json files by setting FS
to :
:
This answer is GARBAGE. Even if the json file is pretty printed with each field on a separate line, it will fail lamentably when the key or the value contain themselves a colon. And BTW, how was this answer so highly voted? By using sock-puppet accounts?
It was containing another 1 or 2 technical remarks about bugs in the script -- I think to the effect of "you should use -v
to pass a variable to awk
, but I don't remember them exactly. The remark at the end was accurate: the answer, though not working (even with the file at hand), had already 12 or 14 upvotes.
And after @goro, instead of fixing their script, notified me that he had reported my comment and I'll have to suffer the consequences:
LOL. You're upvoting your comments too. Look: if they kick me out and let you do your shtick, that will only make all too clear how things work here.
2.
That was a comment to an "answer" of the form "the stdout device may or may be not copied to the terminal. at some point the stdout device will be turned into pixels and copied (as with cp
) but this is an implementation detail".
Yes, and at some point, the panel those pixels are "copied" to will be smashed into pieces and rare metals recovered. Poor pixels! Seriously, is this stuff bot-written?
3.
To a pompous, (highly upvoted) answer to an absurdly trivial question which was asking whether the gsub
and sub
functions from awk
should be "concerned" with records, fields, FS
and OFS
:
But if you use gsub(".","&&",$1)
, then $0
will be rebuilt too (using the value of OFS
, no less!). So gsub
should be "concerned" about fields, records, and OFS
(In case someone doesn't get it, this is supposed to be tongue-in-cheek. Some questions here look like they're right off festoon(6)).
And finally, my reply to the mean-spirited reaction to it:
This kind of question may have uses. To drive traffic, for instance.