Hacker Newsnew | past | comments | ask | show | jobs | submit | mihar's commentslogin

Yep.


Hey, good questions.

A.) You can't download the video, because videos are owned by YouTube and their creators. We just overlay the audio and play the original videos. You can embed the resulting videos though.

B.) Every video has a one-pager with a permalink, like on YouTube.


can't we just dub on the fly, while the audio is being uploaded to youtube or another site? and later share the plugin powered page, that brings together the two link, helping in sharing funny dub overs ?


I agree. Less useful for you, more useful for someone who likes HAML, SASS and CoffeeScript.


I agree that this not an optimal start point for someone who just heard of Backbone.js.

I do think, though, that if someone will still be a bit confused how to stitch things together after reading and poking around for a while, this sort of skeleton could provide just enough insight.

I released this as something that seemed useful to me and in that context should be useful to at least someone else.

If you're unfamiliar with the Ruby world, the usefulness somewhat disappears, but that's said in the prerequisites.


Agree. But I doubt any beginner in web development will be touching Backbone.


I don't know a single tool in that list outside of tangential experience with Ruby. I've worked in some combination of Java, Objective C, C#/VB, PHP, Python and several types of SQL over the last decade. I would hardly call myself a beginner. It doesn't mean this tutorial isn't useful, just that it's only useful for the extremely small subset of developers who happen to use Ruby, HAML, SASS, and CoffeeScript.


Perhaps not. But it seems like the author added an unnecessary level of abstraction for parts of the tutorial. It's his tutorial - he can do what he wants ... but it likely slows, complicates, or excludes-from-participating-in people that aren't well-versed in his chosen toolkit of technologies.


True.


It's one thing to prompt the user when you start recording and another to need to go to chrome://flags.

Permissions for privacy invading features should IMO have a unified interface like they have in the OS like Mountain Lion.


The need to go to chrome://flags has nothing to do with privacy.


You need to go to chrome://flags to enable Web Audio Input. The request for the microphone has nothing to do with that .. it's working with or without Web Audio Input.


It works better as in "is supported on more platforms". But here we were solving the Chrome problem specifically.


It seems it "slipped" through the cracks, although it was discovered before they released version 23 for Mac.

They are working on a fix, but in the meantime, lots of people are inconvenienced using tools dealing with mic access.


RABL is very good at this.


You are correct. You can only decide a meeting when it's due. This is because all the participants are counting on the meeting to be available until that date.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: