HNHacker News
TopNewBestAskShowJobs

masterkain

39 karma · joined October 10, 2012

Software Engineer / Cloud Computing and Music
submissionscomments
masterkain··on Dropbox Webhooks
At AudioBox (https://audiobox.fm) we have a strong use case for it. We are already providing our users a "live filesystem" with Box, exciting that Dropbox is also adding this.

We'll have a look at this after our next release.

masterkain··on Coursera blocks access to students in Cuba, Iran, Sudan and Syria
dark times
masterkain··on Github Reliability
often ignorant people that wants to target a specific project.
masterkain··on BitTorrent’s File Synchronizing Service Sync Launches as an iOS App
This is old news, I have the app on iOS since quite some time now. The article also is dated Aug 27.

The app itself is not bad, very simple, just pay attention to your Cellular Data settings, much like any other sync apps out there.

masterkain··on Ask HN: Dealing with a huge MySQL database - help
stackoverflow -> this way
masterkain··on Ask HN: Is NodeJS stable enough to build the next Twitter?
Is yours a large or small app? Do you use streaming/piping/remote services?

Regarding bugs, there are too many to list, just see the tracker and spend some time browsing through them https://github.com/joyent/node/issues?direction=desc&pag... I'm fairly sure you can find pretty much anything.

I'm considering removing all the npm modules from my project and go raw, since most of the obscure bugs are in the ecosystem anyway.

Somehow I missed domains are also in 0.8, thanks!

masterkain··on Ask HN: Is NodeJS stable enough to build the next Twitter?
Domains are 0.10 specific I believe, and 0.10 is still bugged in few areas. I'd stay on 0.8.23 for quite some time since we are talking about stability.
masterkain··on Ask HN: Is NodeJS stable enough to build the next Twitter?
I'm in the streaming field too; how can you say it's working great if you haven't launched yet to the public?
masterkain··on Ask HN: Is NodeJS stable enough to build the next Twitter?
It works for us, but it comes with a lot of issues, some of which are pretty major, although this holds more true in the ecosystem, not always in core. Problem is see is that no one seems to know how to solve them (it's a callback, no it's node, no it's v8), takes so much time or just plain don't care (socket.io, I'm looking at you), so you're on your own if you encounter something critical.

Either case start getting traction, don't over optimize at the start and watch out for memory leaks: there are tiny bits of best practices that you must follow (always consume the response? check. close the request appropriately? check. don't crash the whole node process? check.), some of which not really well documented, that can ruin your day should you get some important press and are not implemented correctly.

Take a look at the issue tracker of the libraries you are going to use, check if there's something that can affect you and perhaps contribute back!

masterkain··on AudioBox lands on Android: stream from your favorite cloud
Hello folks, BlackBerry and Ubuntu One Music support is up next.

Let us know if you have a cloud service that you would like to see integrated!

masterkain··on 7 billion people on 1 page
Explained in the FAQ: http://www.7billionworld.com/faq.php