1. Pure web tech on phone OS is simply not a choice, Facebook did it and failed too.
2. It's better to use new tech (pure web) in new market such as IoT. If using in existing market (iOS and Android), customers will ask: is the user experience better than the existing ones? And that's why they decide to end the development: "However, we weren't able to offer the best user experience possible and so we will stop offering Firefox OS smartphones..."
- The Windows version sucks: I have a really long note and now I cannot open it, the whole program just crashes.
- The Mac version is OK. Still running fine.
- The Web version looks cleaner, but it doesn't have a highlight tool??!!
Another major complain is that it's really difficult to store code in a note.
I started using [WizNote](http://www.wiznote.com/) recently and it seems really good: markdown, free, multiple directory support, comments, etc
That sounds cool. So basically I don't need the chromecast audio if I have the PI, right?
I like the iOS' system level of audio output (AirPlay) and didn't know Android is flexible enough that an app can do that!
Server side makes more sense. WPF is an UI framework, even it includes WPF, the user experience will be bad just because it looks so differently than native apps.
I have exchanged to 5 Ups and all of them DOA. Since I bought from Amazon I cannot get refund from Jawbone. Now I have my Up sitting in the draw for months...
Playing with Meteor and mongo recently and have found mongo seems a little bit strange from a transitional SQL point of view, like do I need to embed or reference? Can anyone recommend a good book or source?