Earlier quoted context omitted.
How nice of them. Makes you wonder how many apologies are outstanding.
Only one, from @zeeg.
What It's Like To Be Ridiculed For Open Sourcing A Project
461–470 of 826 posts
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#462Earlier quoted context omitted.
the worst bit is that a lot of the ridicule seems motivated by the fact that it's fashionable to hate on node.js. this tweet as much as admitted it: https://twitter.com/steveklabnik/status/293831920872194050
the hatred of node.js always reminds me of anti-apple people.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#463Earlier quoted context omitted.
Why do you have such a strong objection to someone spending their own free time to simplify and / or mimic [insert unix tool functionality here]. It clearly serves a purpose and it's apparently useful. Most importantly, it exists , so there's no need to argue over how you think it should have been implemented. I'm sure if you were to release your own [script / wrapper], someone would find use for it, in the same mann…
I know it someone's right to do this, of course. I object because I come from an environment (software industry) where I have spent hundreds of hours undoing people's poor jobs where they wasted time and money reimplementing (incorrectly) library functions, system commands, etc. Because of this personal experience, I reacted the same way many reacted when seeing her script. So, I decided to explain to her and attempt…
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#464Earlier quoted context omitted.
Two reasons why it's better to memorize the cruft: 1. You can pipe find/sed/grep/cut/awk/whatever to other utils. Today you might be replacing, tomorrow you might be analyzing text logs, and the more core utils you learn the more things you can do with them. 2. When you're ssh'd into another box that doesn't have that spiffy replace utility, now you don't know how to do an inline replace.
Your argument that it wouldn't be available on other boxes can be applied against any new command, no matter how fantastic, so it doesn't seem very constructive to me.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#465Earlier quoted context omitted.
It's a people problem, not a developer problem. Watch the gossip magazines trash actors' clothes and haircuts.
> Watch the gossip magazines trash actors' clothes and haircut And also reading some of the more interesting messages on the Linux Kernel mailing lists, specifically messages by Linus. It's sometimes entertaining to read them and the responses in defense of Linus because he's awesome. I wonder what the reactions from HN would be if it was Linus, or some really high profile programmer, making these comments?
Someone gets in a fistfight over a woman, this is not mature, but it's different from cold-cocking strangers on the street because you think it's fun.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#466Earlier quoted context omitted.
I've been coding since 1993 and I have never made room in my brain for stuff like -print0. Moreover, there are times when you'll want to do this stuff from within another program. What are you going to do, shell out to a find(1) pipeline? Then people like me will be giving you shit. There's nothing wrong with rewriting sed in Javascript.
I looked up what print0 does as I use find and xargs a lot. Here's what print0 does - it separates the filenames with a null byte so that names containing spaces and newlines can be interpreted correctly. Hopefully someone else will find it useful.
On the bright side, normalizing file names before batch-processing them was a good idea too.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#467Earlier quoted context omitted.
At this point, I blame it on the assumption that Aspergers must run rampant and is severely underdiagnosed in the dev community.
Think about this: this statement, right here, is a completely unfounded (i.e. you have no evidence about any of the 3 people being ASD, and the probability of all of them being ASD is really low even among geeks like us), passive-aggressive (you are attacking people with ASD but making it appear sympathetic), pseudo-intellectual (how much do you really know that you didn't read in superficial internet threads) insult…
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#468Earlier quoted context omitted.
The tool is simpler than sed because it misses a lot of stuff that sed actually does. That's what you and the people mocking this project have missed. Well, there's also the old idea of "if you don't have anything nice to say, don't say it." Or the idea of constructive criticism. Or the idea of contributing useful patches to the project. So yes, there is something you and the armchair experts missed: software doesn't…
I disagree, slightly. Mockery is sometimes the only way to make the powerful, oblivious or powerfully oblivious pay attention. I agree that it is not a reasonable tool against someone who isn't hurting anyone.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#469At my office, I would be very angry if I encounter your tool. That would mean that the guy who has brought it was too lazy to learn the proper way and makes me waste my time learning how to use a useless tool. Your tool has no advantage over standard unix tools, it is just limited to a reduced number of use cases. This kind of tools does not favour improvement of skills or good practice. I think this is the cause of…
I think you should update your README.md file in order to indicate the proper way of doing things and to discourage the use of it for any other purpose than learning. Ack isn't a "standard unix tool" either. I use it all the time. You're being a presumptuous asshole in telling her to discourage the use of it just because you don't like it. I get that you're trying to be nice. You're not succeeding. You're being the p…
Many developer are always on the same environment. They can use their own tailored tools and may not need many of the basic unix knowledge.
I think that good practices should be encouraged. The good practices improve the skill of people and reduce the costs at the society level. The basic knowledge of unix tool has an exponential rewarding effect (by learning a couple of new tips, you can solve many new needs). This tool facilitates the avoidance of these good practices.
I do not like people ignorance and I favour knowledge. I do not like losing time (except on HN) and I favour speed. I admit, this is a personal opinion.
We do not have much time to learn everything. I think the time spend learning "replace" should better be spend learning "sed". Try to use sed each time it is not longer than opening a text editor and doing a find and replace manually. This way you will not lose your skill.
Ack is not a basic tool you have chosen to avoid learning grep. All the basic options of grep are the same in ack. As a result you will not loose skill by using ack.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#470(I copied this from another HN posting) I was one of the people who made a comment about this. I'm also assuming the reason I was pulled into this is because people much more important than me said similar things. I'm not going to defend that I think attempting to replace sed/grep is a bad idea (especially not in 140 characters), but I will defend people's opinions. Everyone has one, most of them you won't agree with…
In other words, if someone says something nasty, you have no right to say anything about it. Because the nasty person has an opinion, and it's their right. Great logic!