[deleted]
What It's Like To Be Ridiculed For Open Sourcing A Project
401–410 of 826 posts
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#402I just wanted to point out that the code (I know, it's not about the code) here is perfectly fine JavaScript, much, much better than tons of JS I saw in the wild. "eyes bleed"? What the heck? Have these guys never seen truly bad code? And if it's really just about language war...
Look, I understand that one can prefer one language over another, but trashing the code someone already written (meaning you won't be forced to write this thing in this language if the need be) is so short-sighted, so closed-minded that I can't find proper words to describe it.
I almost refuse to believe that this is the kind of people who are the "stars" of communities - I really thought that to be really good with one language you need to know and respect many others and I thought that being a "star" involves being being good in the language you want to champion. I guess I was just deluded and we're choosing those who yell the loudest as our representatives. Whatever happened to meritocracy?
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#403Earlier quoted context omitted.
There is a huge gulf between Asperger's and full blown autism. People with Aspergers are "normal" people in the sense that they are generally capable of looking after themselves, communicating and working normal jobs etc People will full Autism have severely limited communication skills (often no spoken or written language skills at all beyond repeating a handful of phrases) and require a significant amount of assist…
I thought Asperger's was being removed from the new DSM, so it's all autism now?
Not sure of the new terminology but these are 2 conditions that vary not just quantitatively but qualitatively.
The term Autism as it is used today suggests severely delayed language development. This is not a symptom of Asperger's and sufferers of the latter can often develop advanced language skills.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#404At 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 the strong reactions.
On the other hand, your program seems well coded and I may use it when I need to code something similar in javascript. Thank you for open sourcing it. 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.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#405I never understood such gloating on open source communities. If you can change it for good, why gloat, why complain. There's obviously many reason to rage when you see bad code on commercial and privative stuff, but on open? Dammit, fork it, change it, contribute.
It was a bad behavior and people should understand it.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#406Then I see these people’s follower count, and I sob harder. I can’t help but think of potential future employers that are no longer potential. There's a big responsibility that comes with being well-liked and nice. When someone with a good reputation and the means to broadcast it speaks negatively about someone, it matters much more than someone who is routinely rude, frequently negative, or unknown. I know that if t…
Fair point. Once I read the names of those involved, I was a little taken aback for this very reason. Friends I respect think quite highly of Corey, for instance. Also worth noting, both [Steve and Corey] have published apologies on their own blogs. Both are worth reading.
How nice of them. Makes you wonder how many apologies are outstanding.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#407Earlier quoted context omitted.
Hear hear! I've had a sed book on my shelf for years and I've used it more than once, but 99% of the time I end up giving up on sed and using a GUI-based tool instead of trying to concoct the cryptic lines given above as examples. I absolutely would rather use the clean interface of replace, written in JavaScript or anything else, than to memorize that steaming pile of cruft.
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.
1. Perhaps learn that when you actually need to analyze text logs?
2. Perhaps you don't need to do this. Or perhaps you'll work it out when you ssh into another box.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#408Heather, 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…
Some of my examples can be further simplified (no -print0, no xargs), without a perf issue ("{} +" passes multiple filenames as arguments), with GNU find which is standard on Linux:
replace 'var' 'let' . -r
find . -type f -exec sed -ri 's,var,let,g' {} +
replace 'var' 'let' . -r --include="*.js"
find . -type f -name '*.js' -exec sed -ri 's,var,let,g' {} +
replace 'var' 'let' . -r --exclude="*.min.js,*.py"
find . -type f ! -name '*.min.js' ! -name '*.py' -exec sed -ri 's,var,let,g' {} +
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#409Earlier 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.
I think it is a good argument to learn basis before reinventing the wheel. When using unix, there are already far too many commands to learn. Not having to learn useless commands is a bonus.
Re: What It's Like To Be Ridiculed For Open Sourcing A Project
#410> Steve Klabnik @steveklabnik > @harthvader @zeeg nothing's _wrong_ with it, but I don't want to build my app on top of others' code who are at this level of understanding This message [1] in particular is absolutely disgusting. Someone hacked together a script that met their needs, and threw it up onto GitHub in case anyone else found it useful? Yes, let's take the opportunity to condescendingly insult their mental…
Here's the thing, when someone like Linus Torvald says things like that, we applaud him for it.
Linus doesn't say things like that.
He goes after people who enter discussions without bothering to understand the details or the history. If you want to code your own kernel in Java, that's your prerogative. But if you come to lkml and start preaching C++ advantages, you will get flaked.