Reputation
1,217
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
2 11 22
Newest
 Yearling
Impact
~36k people reached

  • 0 posts edited
  • 5 helpful flags
  • 21 votes cast
May
14
comment Single codebase for client and server with Node.js
@funkybro - Just going out on a limb and guessing you're my downvote. This question is highly subjective, so it's impossible to give an non-subjective answer. There are debugging tools (node-inspector being the most popular). It's inherently difficult to debug async programs, but that's not specific to JS, it's true of any concurrent language (Erlang, Go, threaded C/C++/Java, etc.). Care to elaborate?
May
14
answered Single codebase for client and server with Node.js
May
14
comment Why not use a RTOS with microkernel architecture for highly concurrent web servers?
Why do you want an RTOS? Also, hard or soft real-time? A hard RTOS would be very hard for a micro-kernel because of its async nature.
May
11
awarded  Critic
May
11
awarded  Custodian
May
11
reviewed No Action Needed How important is Domain knowledge vs. Technical knowledge?
May
11
reviewed Reviewed Log defects for failures of other systems?
May
11
reviewed Reviewed How to use GPL v3 with Apache License 2.0?
May
4
comment Why are many programmers moving their code to github?
With Google code, I can star issues, which lets the devs know which issues are important to the community and helps me keep track of progress. Github only seems to have anonymous following, which can lead to comment spam (+1, me too, etc). This is significant for popular projects with limited resources.
May
4
comment Why are many programmers moving their code to github?
It's also fantastic for finding the most maintained branch. I recently had to find which fork of a certain repository was actually maintained (non-trivial because the more up-to-date forks hadn't yet floated to the top of a google search).
Apr
8
awarded  Nice Answer
Apr
7
comment Term for accidental features
@smp7d I'd say the same thing, but with a wink.
Apr
7
comment Term for accidental features
@MasonWheeler Citing a feature as "accidental" shows you don't have good quality control. An "undocumented feature", on the other hand, sounds planned, even if it was an accident. I write code for a lot of government clients, and they don't like surprises.
Apr
7
answered Term for accidental features
Apr
7
comment Term for accidental features
I call them "undocumented features", though I often use it sarcastically to refer to a bug. Not sure if that's standard though.
Apr
7
awarded  Nice Question
Apr
4
accepted Map of functions vs switch statement
Apr
3
revised Map of functions vs switch statement
added 320 characters in body
Apr
3
comment Map of functions vs switch statement
@pdr - Right. My inclination was a map of commands to functions, but I'm a relatively junior programmer in a CS design course. My professor likes lots of classes, so there's at least 2 legitimate solutions. I wanted to know the community's favorite.
Apr
3
comment Map of functions vs switch statement
The commands are unique strings. I can map these to integers if needed.