Why is this on the front page of HN? Anyone read http://corte.si/posts/socialmedia/trouble-with-social-news.h... ? Unfortunately, that article is spot-on. I want to be reading industry news, not someone's social gossip. Specifically, I want to read articles about optimizing Erlang, the latest developments in NoSQL databases, developer war stories, and changes in the funding landscape. I don't want to hear about someo…
It's on the front page of HN because this community cares about civility, online interactions, open source contributions, and gender issues in technology.
Node, Twitter, and Apologies
51–60 of 82 posts
Re: Node, Twitter, and Apologies
#52Why do people hate Node so much?
Re: Node, Twitter, and Apologies
#53Earlier quoted context omitted.
Node inherits the warts of Javascript. Node the framework is quite good and handles abstracting out threading/async incredibly well. Node the community is still young, but growing. On two recent projects, I tried two different http auth related modules (digest auth). Both had been active for awhile and recently updated (within a month or two). Yet, despite digest auth being pretty established/spec'd out, had some ser…
Outside of some very low-level modules that wrap C calls, most of the node modules are either very specialized or incomplete. I definitely find it easier in most cases to just rewrite functionality than to fallback on the recommended modules. Fortunately the C++ API isn't too far abstracted from the V8 API
Re: Node, Twitter, and Apologies
#54I'm gonna copy what I said in the other thread, because it's more relevant now: You know, reading the various devs' tweets, they use twitter in a way that is completely foreign to me. Is there anything these guys think that they don't tweet? ("Hey, who's picking me up from the hotel?" is not something I'd ever announce to the world at large.) This incident shows a danger of working that way--one of these guys apparen…
Re: Node, Twitter, and Apologies
#55Earlier quoted context omitted.
I don't hate node However, the tools around using Node and JS are inferior to other languages (C/C++, Java, C#, even PHP and Python). Further, the language doesn't have the cleanest history in terms of design, so in a project with multiple people on it, you are leveraging coding guidelines, linters, and the like to have any real consistency. A colleague raised an interesting question which I will paraphrase -- given…
Google, through Closure Tools, and other groups and people have built tools around javascript. For example, JSHint is a pretty good linter and fixjsstyle is a nice little tool to fix formatting. Certainly JS isn't as amenable to static analysis as C, but with time we'll see more.
Sublime JSHint JSFormat (or fixjsstyle)
To get code to some basis of style consistency.
Debugging -
node-inspector or console.log
In the last six months, node-inspector has gotten a lot better, but a lot of times inserting console.log is just faster (mmm...printfs).
Re: Node, Twitter, and Apologies
#56Earlier quoted context omitted.
I don't want to hear about someone apologizing for an offensive Twitter post. Go ahead and keep downvoting me for expressing an opinion -- I'm sure I'm not the only one with similar feelings :) --> To respond to the posts below: I think the original post is fine, I didn't make this comment there. Hearing about that is interesting and is a fine example of how easy it is for users with social capital to abuse it, a rem…
How is "I made this thing, shared it with the world, and was ridiculed by high profile members of the community" not a developer war story?
Re: Node, Twitter, and Apologies
#57Earlier quoted context omitted.
Google, through Closure Tools, and other groups and people have built tools around javascript. For example, JSHint is a pretty good linter and fixjsstyle is a nice little tool to fix formatting. Certainly JS isn't as amenable to static analysis as C, but with time we'll see more.
What you outline is my gripe. Typical NodeJS dev setup amongst those I know: Sublime JSHint JSFormat (or fixjsstyle) To get code to some basis of style consistency. Debugging - node-inspector or console.log In the last six months, node-inspector has gotten a lot better, but a lot of times inserting console.log is just faster (mmm...printfs).
Btw I prefer console.error :)
Re: Node, Twitter, and Apologies
#58It's okay. People sometimes say hurtful things despite historically having strong opinions about never belittling other people publicly. It doesn't mean that they truly mean it, and it doesn't mean that you should take these negative things to heart either. People slip up because we're multifaceted creatures and despite our intentions to be the best person all the time, well that's just not possible.
Regardless of whether what you're being criticized for is justified or not, it is inevitable if it's been made public. The irony in this case is that the bully is being made feel worse because of his past blog posts, which is also sad but just as inevitable. It's okay Steve, we all fuck up, and the ease of doing it on Twitter doesn't help.
Heather, I promise you that any decent potential employer is still exactly that. Nobody will disqualify you from a job position based on something you've made. You've open-sourced it, so if anything you get bonus points. You will always be criticized, the trick is to ignore the haters and know that people in a situation of genuine critique (i.e. candidate interviewer) will never judge you (as badly) as some people on Twitter did.
Do not let this discourage you from contributing publicly in future either, even if your code IS shit. Everyone's code is shit, at least to some people. As long as you're happy with it, that's all that matters. Also, somewhere down the line you'll look back at it and think "Wow, that's shit code", which just means you've gotten so much better.
Re: Node, Twitter, and Apologies
#59I'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: Node, Twitter, and Apologies
#60I was one of the people who made a comment about this. 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…
Also, I think the "If you don't like, ignore it. If you can't ignore it, then you won't survive," is self-serving advice. It'd be easier to take seriously if you were one of the nice people.