AppHarbor uses nginx as a load balancer and it currently doesn't support HTTP/1.1 proxying with upstream servers, which is required for Websockets support. It was recently introduced in the development branch (v. 1.1.4 http://nginx.org/en/CHANGES) and should make it's way into the stable branch soon.
We (AppHarbor) are adding support for node.js on a beta-basis primarily to collect initial feedback from our users. Improved support for debugging node apps is certainly something we'll look into.
Sorry about the confusion - didn't mean nginx would have WebSocket support when HTTP/1.1 proxying is supported. It seems like it's a necessary feature before it can happen though.
A Firebug like prompt is the plan i.e. "Script is taking too long to finish, do you want to stop it..." maybe every (n * X) time interval for n is every time the msg is shown for a specific peace of code.
As the readme notes, it's completely unsafe if you perform any mutation operation.
As to the performance hit, I'd expect almost none when not in use for long-running processes: it spawns a thread, and that thread will then wait on a socket accept, no connection, no resources spent. You'll still be paying in memory for the server thread, but that's it (the server thread only creates two objects, an rlcompleter.Completer instance and a function).
We've been using rfoo to do this. It doesn't seem to impact performance when you're not using it. When you are using it, it's unsafe if you do unsafe things. We primarily use it for debugging by passively inspecting the messed-up portion of the server's state.
For find, you need to use single quotes so your shell doesn't automatically expand the .java glob into the names of all the files. Also, find uses one dash for parameters, and can take an exec parameter:
find . -name .java -exec wc -l {} \;
The {} means "replace with filename" and the semicolon (escaped so your shell doesn't eat it). This will run wc -l <filename> for every file that matches.
The -regex flag lets you do the same thing as -name with regular expressions.
The problem with this is we run n different wc's, as opposed to just one with all the parameters. We can use xargs to fix this:
find . -name .java | xargs wc -l
This even gives you a total!
The really* simple solution (which is probably best) is to just use shell globbing:
wc -l *.java
While find and xargs are definitely useful, the easy solution here works better
You can skip xargs altogether with the plus sign instead of semicolon.
-exec utility [argument ...] {} +
Same as -exec, except that ``{}'' is replaced with as many path-
names as possible for each invocation of utility. This behaviour
is similar to that of xargs(1).
The problem with just wc -l *.java is that it don't recursive directory.
This is an interesting alternative to StackOverflow, though I think that you might be able to hit a wider and more skilled audience in an already established community.
This also works with live camera feed because of how OpenCV handles video streams. You can extract frames from the stream and then run the same face detection code on those extracted frames.
This is a great post given that a lot of the OpenCV functions, while powerful, are either missing documentation or have outdated documentation.
This is the problem that I had when I was applying to colleges: I used to ignore classes that bored me but were required and instead spent time that should have been spent on homework, etc. doing programming side projects and learning CS concepts.
When application season rolled around, I had to compete with candidates who had a much shallow understanding of their area of study, but had a much stronger overall GPA, loads of random APs, etc. While I did mention my side projects and depth in my area of interest, I didn't think to submit code or the actual projects; I usually just mentioned it in the questions or essays (which I'm not certain anyone even reads). This lead to quite a few rejections.
I'm at Georgia Tech now and doing well, because all my classes, more or less, are related to what I'm interested in. While I'm very happy here, I'm curious if I would be as happy if I wasn't accepted to Tech, and were instead studying in a place without such abundance of opportunity. I'm sure there are others in similar situations.
Well, the long school years is a way to structurally hide mass unemployment now that we don't have child labour. If youngsters could provide meaningful work and pick up their skills on the way, things would look radically different. Especially in the turtle-pace that tuition normally take. Sure, learning takes time to settle, but why not do something meaningful while the learning settles?
If you have talent, and work hard to cultivate it, then you can take advantage of the opportunities that are around you. Doesn't matter if you're at GA Tech or MIT, there are always more good opportunities than good people.
I definitely agree; it's just a matter of finding the right people.
Anecdote: attending some of the tech talks that companies give at Tech, there is always a gradient of people, from the people that are there for free food to the people that are there to ask questions and get something out of it. These tech talks are thinly veiled recruiting events, and the latter set of people are always approached afterwards for interviews or networking purposes.
No idea where this came from (or if it's a good idea to feed the trolls; "hn_is_dumb" - really?), but Tech does have the policy to accept most and then fail out those who don't belong there. Only 29% of incoming freshman graduate in 4 years.
I'm glad Tech has this policy because there are lots of bright people here that did the same thing I did in high school and they do well here for similar reasons.
Neither seem to support WebSockets (though the Heroku article I found was a bit dated[1]) for the time being.
From the article, it seems like AppHarbor doesn't automagically pull in the dependencies from the package.json, which Heroku does.
Add-ons wise, there is a lot of overlap, but Heroku definitely has more at the moment.
Heroku lets you run one-off processes, which is nice for debugging. I couldn't find this functionality on AppHarbor.
[1]: http://blog.heroku.com/archives/2011/6/22/the_new_heroku_2_n...