I wrote a book about the Meteor JavaScript framework, which is available for free, but I also sell a video training series that's based on the book: http://meteortips.com
For the sake of shameless self-promotion, I'd also like to suggest my book for anyone who feels Discover Meteor moves a bit too fast: http://meteortips.com/book/ (It's free.)
Don't overestimate automated translation. My girlfriend is a native Japanese speaker (and professional translator) and she laughs when she sees the results of Google Translate. Especially for a language like Japanese, nothing's going to beat a human being who takes pride in their work.
Previously, I shared the free, online book I wrote about Meteor — http://meteortips.com/book/ — and this course is based on that book. Same scope, but it's much easier to demonstrate certain ideas through video.
Previously, I shared the free, online book I wrote about Meteor — http://meteortips.com/book/ — and this course is based on that book. Same scope, but it's much easier to demonstrate certain ideas through video.
Software-wise, just got a few scrappy demos I've thrown together. One creates an RSS feed for YouTube channels so you can subscribe to them as video podcasts. Problem is, it relies on hot-linking Google's servers and I'm sure it breaks all sorts of conditions in their Terms of Service. Still, want to finish it so I can at least use it myself.
Outside of that, I'm working on a screencast series for the Meteor JavaScript framework:
In that regards, it's mostly a matter of simplicity. It's easier for us to work with the devices we have (and love) and to market based on a specific target.
My partner already does "specialise" in translation. She does freelancing for a living. I simply had the theory that it'd be more effective to niche down, and I chose to target iOS because: I'm a user of iOS, I have some iOS development experience, and the App Store is growing in Japan. We're not basing our livelihoods on the decision. It's just something we're testing.
Because we feel like we can offer better service by specialising, since we can test the apps ourselves, etc. We want to give every app a considerable amount of attention so the final result isn't just a translation that "makes sense," but that will be truly appreciated by users in Japan.
Note: We were having trouble with the original email in this post so I've switched it over to my personal email. If anyone's sent a message already, please resend. Thanks. :)
As for your suggestion, I'll have to check out that Udacity course like you suggested. My worry is that the book could become too heavy on the theory within the first few pages — I mostly want to get the reader's fingers on the keyboard as soon as humanly possible — but can see where you're coming from and will do what I can in the next few versions of the book. :)
Usually refer to it as just "Meteor" but, in the form of a headline, "Meteor.js" feels a tad more descriptive. Even if someone has never heard of Meteor, they can see that it at least has something to do with JavaScript.