Debuggable

Why are you writing about "soft real time" when you don't seem to have done any work in RTOS/embedded?

Your listed project is transloadit, which is a file uploader that does some sort of magic I don't care about. (I'm provincial.)

You also appear to be available as a node.js consultant. That's a first for me. I figured the only "node.js consultants" were ryah and anybody you could catch awake on Freenode.

A burgeoning ecosystem is good. It's not good when virtually every proponent of Node.js I run into makes wild claims.

Checked your submissions, I see in this order from chronological proceeding towards the final entropic state of the universe:

1. jQuery >? *

2. Git

3. Node.js

4. Node.js

5. Node.js

6. Transloadit file jobber thingie (written in JS, on Node.js)

7. Javascript (This is what Node.js is written in, FYI)

8. TDD @ Transloadit (written in JS, on Node.js, Church of the GoF)

9. Realtime encoding - over 150x faster

As easily as I could outright crucify you for butchering the word "realtime" here, I'll simply spare you the trouble and do a text-replace that'll fix your solipsism simulator article (blog)

s/realtime/buffered/g

'Fraid that won't work for your video though. You'll have to fix that yourself. Also, please provide full transcripts (linked, in-line, doesn't matter) in future. Not all of us are hearing.

And to cap it:

http://debuggable.com/posts/hacking-a-commercial-airport-wlan:480f4dd5-50a0-40c6-aa60-4afccbdd56cb

Illustrious real-time…

I'm not an expert, but from what I've seen:

1. It's event-driven and javascript.

2. It already is.

3. It shouldn't be a turf war. It isn't for everything. But, I'd rather write in javascript than erlang, scala, haskell, etc. and I'm sure others would be in the same boat.

4. Heroku, etc. are starting to host, so it kind of already is. Any fast, simple web-based service could be a good candidate for node.js.

See: http://debuggable.com/posts/understanding-node-js:4bd98440-45e4-4a9a-8ef7-0f7ecbdd56cb

ASCII is 7-bit (encoded in 8 bits - the high bit is ignored) and UTF-8 takes 8 bits for most characters, but can take 16+ bits for some characters.

Node is built for massive scalability on applications that (mostly) pass text from one source to another. Thus, having to convert the encoding of every string that passes through node can be a bottlenck.

Felixge has a good writeup of this: http://debuggable.com/posts/streaming-utf-8-with-node-js:4bf28e8b-a290-432f-a222-11c1cbdd56cb

It's useful for streaming large data sets, such as audio or video files.

Here are some examples:

http://debuggable.com/posts/streaming-file-uploads-with-node-js:4ac094b2-b6c8-4a7f-bd07-28accbdd56cb

http://blog.new-bamboo.co.uk/2009/12/7/real-time-online-activity-monitor-example-with-node-js-and-websocket

http://blog.andregoncalves.com/post/1620276144/inaugural-twitter-streaming-with-node-js-and-html5