D
Debuggable
debuggable.com · Company blog · on HN since 2009
Debuggable is a company blog from developers working with node.js, covering file uploads, streaming, testing, and JavaScript performance.
What HN saysCommenters point to its node.js posts as helpful explanations of node's event model and as examples of fast streaming file uploads.
20HN people shared it
8linked it in comments
18stories submitted
420story points
14 years agolast shared
2009people per year2026
Most-shared posts
- 1Understanding node.js8 people · 12 points · first shared 2010 · discussion on HN
- 2Parsing file uploads at 500 mb/s with node.js4 people · 84 points · first shared 2010 · 28 comments on HN
- 3Streaming UTF-8 (with node.js)2 people · 22 points · first shared 2010 · 13 comments on HN
- 4Git Fake Submodules2 people · 3 points · first shared 2010 · discussion on HN
- 5Test driven development at Transloadit1 people · 133 points · first shared 2010 · 65 comments on HN
- 6Is RightJS really faster than jQuery?1 people · 74 points · first shared 2009 · 18 comments on HN
- 7Why are you not using a SSD yet?1 people · 49 points · first shared 2011 · 95 comments on HN
- 8Nerd badge of honor : Testing node.js modules with Travis CI1 people · 34 points · first shared 2011 · discussion on HN
- 9How to fork & patch npm modules1 people · 6 points · first shared 2011 · discussion on HN
- 10Announcing transloadit.com1 people · 1 points · first shared 2010 · discussion on HN
- 11How To Save Half A Second On Every CakePHP Request1 people · 1 points · first shared 2009 · discussion on HN
- 12Disable strict host checking for git clone1 people · 1 points · first shared 2012 · discussion on HN
- 13Streaming file uploads with node js:4ac094b2 b6c8 4a7f bd07 28accbdd56cb1 people · first shared 2011
- 14Hacking a commercial airport wlan:480f4dd5 50a0 40c6 aa60 4afccbdd56cb1 people · first shared 2011
What HN people wrote when they linked it
EzGraphs · 2012-11-14
Described in use for fast video encoding:
http://debuggable.com/posts/parsing-file-uploads-at-500-mb-s-with-node…
ManuelKiessling · 2011-04-19
I too still don't understand 100% what's going on behind the scenes of node/V8 regarding threading/parallelism, but this post here helped me a lot to understand it from a bird's eye perspective:
http://debuggable.com/posts/understanding-node-js:4bd98440-45e4-4a9a-8…
It's also linked from The Node Beginner Book.
dpapathanasiou · 2011-02-12
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:4ac094…
http://blog.new-bamboo.co.uk/2009/12/7/real-time-online-activity-monit…
http://blog.andregoncalves.com/post/1620276144/inaugural-twitter-strea…
devmonk · 2010-09-02
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-8…
mhansen · 2010-08-20
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…
kelvinjones · 2010-07-19
http://transloadit.com/
The developers wrote about using node on their blog: http://debuggable.com/posts/parsing-file-uploads-at-500-mb-s-with-node…
udfalkso · 2010-06-21
I found this post helpful:
http://debuggable.com/posts/understanding-node-js:4bd98440-45e4-4a9a-8…
alnayyir · 2011-03-31
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…
Illustrious real-time…