Maybe before we spend a lot of time complaining about how federal prosecutors are unsympathetic assholes, we should start by examining our own community.
A similar sentiment: http://www.shirky.com/weblog/2013/01/remembering-aaron-by-ta...
What It's Like To Be Ridiculed For Open Sourcing A Project
321–330 of 826 posts
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#322Very disappointed with the people that made these statements, they should know better.
Kicking other peoples puppy is never cool, people forget where they started.
Some times you have to take this sort of crap on the chin and keep hacking away, the best thing you can do in situations like is just ignore them.
I think in this case they have realised how stupid their statements where and are hopefully truly sorry for the hurt they have caused.
Also a note to those with many followers, don't be a dick.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#323Heather, I agree that people are unnecessarily rude to you. Don't sob. Your code shows you are already a more capable programmer than most of the ones I interview. No one has given you a clear answer as to why your code is reinventing the wheel, so allow me to do it politely. I took every single example from your README, and show you below how everything can be reimplemented with sed -r (nice extended regex syntax, m…
both Perl and Python use PCRE
No, Perl doesn't.
PCRE was written because a lot of people liked some of the ideas that were first introduced in Perl's regular expression engine. But PCRE was a reimplementation, and never was all that compatible with what Perl was doing.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#324Heather, I agree that people are unnecessarily rude to you. Don't sob. Your code shows you are already a more capable programmer than most of the ones I interview. No one has given you a clear answer as to why your code is reinventing the wheel, so allow me to do it politely. I took every single example from your README, and show you below how everything can be reimplemented with sed -r (nice extended regex syntax, m…
Thank you for taking the time to write these translations. In fact, I'm going to bookmark this thread and use it as a reference in the future.
I feel these examples serve more as a selling point for why one would use something like `replace` over a cacophony of flags and pipes. The interface for `replace` is simple and elegant. It does one thing, and it does it well. I think that's commendable.
P.S. The `sed -r` flag does not exist on POSIX systems like OSX. You'll have to use something like perl -pie, or write a convoluted buffering loop.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#325Earlier quoted context omitted.
Both of you seem to think he said "instead." Consider the clauses rephrased: "Maybe we should start by examining our own community, before ..." Why? I'd guess because the blog post refers to celebrity hackers bullying another hacker. The community -- more than just these few guys -- can't even behave civilly. It's a case of the pot calling the kettle black.
Compare the cause-and-effect of both the situations. One can send someone to jail for life and destroy their finances, reputation etc... the other can hurt someones feelings. Contending the latter should be addressed before (or even comparatively) to the former is what I take issue with.
If empathy were a limited resource that demanded to be spent only in descending order of the seriousness of the potential injury, then you might have a point.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#326There are a few open source projects which I would be willing to ridicule. In general the projects have traction, a significant history, and horrible code which never gets more than marginally better over more than a decade. It is one thing to be starting out. It is something else to decline self-improvement.
The problem though is this (and I have been on the receiving end of very harsh criticism of people I respected, some of which was shown correct over time), that there are often problems with critics jumping to conclusions and at the same time not being very detailed. Thus a response like these tweets can only be a "gut reaction" and never really very helpful to anyone. There is no time involved trying to grok the code. There is no opportunity to discuss what potential tradeoffs have been made or why. These two things need to be corrected.
I don't think folks should criticize code without trying to work with it and understand the API's. I don't think folks should leave a critique like "that's the old 1990's way of doing things" or "that code sucks." It is much better to get something like "So I see a few problems with the code... and ...."
In fact the few times I have gotten the latter (publishing code and getting responses like "I see some important concurrency issues there. This isn't safe to run on production.") I have been happy with the panning because I could fix the problems. But that's a far cry from what the article is referring to and it is, unfortunately a lot less common, IMO.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#327(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. Whether they're nice or not. I'm generally not a nice person, at least online, that's my choice. That said, especially with this being the internet, you have to deal with others opinions.
While some people may go above and beyond (even myself sometimes) and actually be very mean with their opinion, that doesn't change the fact that they're entitled to it. If you don't like it, ignore it. If you can't ignore it, then you won't survive.
The fact that people somehow managed to turn this into the continuous drama debate about gender is just pathetic.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#328What the fuck. (And I rarely say that word.) We've got to grow up. This is 9th grade all over again. You know, those weird people that do things that you don't understand? They're the ones that grow up and make big impacts on the world. Why can't we get over our negativity? We can't stop ourselves from thinking horrible things, or even saying them out loud to people around us, but surely we can restrain ourselves fro…
the hell are you talking about?
every person that created something worthwile in this world has been ridiculed. for good reason. i hate the fact that people here spout that uber positivity crap.
you know what, you mess up -> you get ridiculed, what do you do? you make something better.
The world is not this pretty flower place where everyone can be happy and strive at the same time. there is no rich without poor, and there is no great without bad.
please everyone be happy is a stupid argument to make. it actually makes people NOT improve.
it has nothing to do with elitism developer community. it's the same everywhere. you don't get patted on the back for doing something mediocore at best, well that is, unless you're an mba.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#329What the fuck. (And I rarely say that word.) We've got to grow up. This is 9th grade all over again. You know, those weird people that do things that you don't understand? They're the ones that grow up and make big impacts on the world. Why can't we get over our negativity? We can't stop ourselves from thinking horrible things, or even saying them out loud to people around us, but surely we can restrain ourselves fro…
[deleted]
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#330Earlier quoted context omitted.
Please, tell me you're jocking: on your platform you cannot afford a pipe but you can launch node.js? by the way: "-print0 | xars -0" is really idiomatic, you know? Lucky you didn't have a single filename with spaces to handle...
I don't know what this even means. I'd already be running v8 runtimes. They're unavoidable. But there's no need to fork and exec (many times over) just to sweep a filesystem tree for files matching patterns. It's the shell, by the way, that cares about "spaces in filenames". Not dicking around with shell metacharacters is just one of the many wins you get by not shelling out to accomplish basic programming tasks.
I get what you're saying for the "already in a REPL" thing, but as far as fork/exec overhead, xargs does a single fork/exec for every thousand or so files you search; the overhead is tiny compared to everything else.