What really bothers me is that, like me, I'd say a lot of those people learn daily from the work of others on the internet. What about giving something back? What about doing something to add?
What It's Like To Be Ridiculed For Open Sourcing A Project
451–460 of 826 posts
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#452Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#453Earlier quoted context omitted.
Linus doesn't say things like that. If you don't understand the difference of context, well, look again!
He does. This was pretty nasty. http://shutupmauro.com/
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#454Earlier quoted context omitted.
Impossible to memorize? I wrote all these examples from memory. I tested them in a shell and had a single error (sed -ir needed to be changed to sed -ri because -i takes a glued "suffix" argument). I really don't think it is that hard to memorize the basic find/xargs options. You only have to memorize them once in your lifetime. They are a basic cornerstone of a Unix skillset. By comparison, I often forget the custom…
> Impossible to memorize? I wrote all these examples from memory. Yes. And people can site Pi to the 10.000 digit. Doesn't make it any less useless.
Calling the basic operation of these cornerstones "useless" speaks more about your disposition than the tools, I think.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#455Earlier quoted context omitted.
Here's the other apology, http://blog.steveklabnik.com/posts/2013-01-23-node Heather, don't take it personally - your code is fine! JavaScript, on the other hand, is a wounded warrior by now..
My takeaway: "Twitter makes it so hard not to accidentally be an asshole."
"Most people are arseholes. Twitter makes it so much harder to hide."
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#456This is par for the course in the Rails community. Once some Rails devs get more experienced, they think it's ok to shit on everyone else. Granted, not all are like that...but many are. God forbid you should stumble into #RubyOnRails on IRC. Thank God for Stack Overflow!
This to me is very unfortunate. I'm an experienced Ruby and RubyOnRails developer, and I think that this is totally unacceptable. This is why the Python community flourishes (and I learned to code with Python!), and the Ruby community, which has unfortunately become equated to the Rails community, relatively languishes. I also think it's pretty funny/awful/ridiculous to see Rails devs hating on JS code. (JS is diffic…
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#457Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#458The truth is that there are a whole bunch of morons out there with petty little opinions and with no real achievements of themselves. They call the people Trolls (with a capital T). Ignore them.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#459Earlier quoted context omitted.
Even if she designed it to be used from the command line, and this is still not the only possible use of the JavaScript code which she open sourced, she had one more reason: sed doesn't have JavaScript regexps. Anybody who really wants to use JavaScript regexps doesn't have other choice but to use her tool. Now you can say that you don't need that, but you still has to admit that others may. So you're still wrong.
With all due respect, you add nothing to the discussion, I already acknowledged this in my OP: "There is only one case that justifies reimplementing things: if your tool has the requirement of supporting the exact js regex syntax..." (Please read what I wrote, really!)
b) Regarding those that do want to "run the command line," can you agree that there are users who really want and need to use JavaScript regexps from the command line and not some other regexps with different semantics?
c) Can you accept that these are the valid use cases that your "use sed" arguments just don't cover?
I've read your arguments and I've never seen clear acceptance of a) b) and c). I've also seen that you had to carefully think and even improve your "use sed" implementations, giving also the good argument in favor of her approach. Having the tools that demand less from the user is a good thing. Can you accept that (d) too?
Can you see why we discuss, when you just quote yourself as "There is only one case"? That's why I claim you're wrong. There's not only one case.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#460Earlier quoted context omitted.
You have a valid point but its incomplete, allow me to explain you why we need projects like replace. You are right in telling that sewing a few utilities using pipes can emulate 'replace'. But remember you are talking about learning those 'few' utilities first. Trust me unless you have practiced your way out of these thing with hundreds of hours with experience over years its humanly impossible to remember and use a…
I have just publish a report on monday where I explain that the command line should be used instead of some small scripts that encapsulate for loops. The argument is that basic shell knowledge should be trained in order to not lose skill (or to improve). At my work, these skills are useful when facing unexpected urgent needs. Having a short script is a very poor benefit (simpler syntax and reduced key typing) for a b…