If you're familiar with thumbnail display you know Facebook has Haystack for efficient image serving. It goes very low end. Sparkey or CDB or BAM (mentioned in this post) could be much less complex and can do similar work. Why did they go Haystack route I dont get it.
Are you asking why they didn't use Haystack? Haystack isn't released publicly as far as I can tell (plus, just because another company writes something doesn't mean it's actually good).
Sorry not being clear enough. Yes I was kind of asking why they didnt try simpler options. When you look at their paper on Haystack you see that it's essentially a constant local database.
can you please expand on this? everybody says C-CORP for a startup for flexibility, investor trust and so on. OTOH, C-CORPs are costlier and more complex. but you're an INC and "real" startups as DBAs! if you make blog post on this that would be great.
QT, really? Using a framework for a must-be-power-efficient device on a much-slower-than-desktop cpu. I'm not a QT or C++ expert and wondering outcomes of using QT for webOS. There is absolutely a hit on power and speed but how much?
Qt is about as low level as iOS's Objective-C runtime (both are compiled to native code and offer semi-manual memory management.) Meanwhile Android is based on full-blown virtual machine (Dalvik) with garbage collection.
HTML5 on the other hand is an elephant in the room. Promoting it as THE way to write apps for WebOS was a huge mistake. It's terrible inefficiency lead to stuttering ui and godawful memory consumption.
Also Qt has been used for graphical embedded projects for years (e.g. it doesn't require X11 on linux and can be compiled on many different architectures.)
<quote>HTML5 on the other hand is an elephant in the room. Promoting it as THE way to write apps for WebOS was a huge mistake. It's terrible inefficiency lead to stuttering ui and godawful memory consumption.</quote>
Agreed. Applications can be written in Javascript using the Enyo framework (Enyo 2 for Open WebOS) so you don't see much html5, but applications can also be written in c++ and their performance is excellent.
Enyo v2 is really superb and you get an awful lot of gui magic for very little: http://enyojs.com/ It recently released it's first stable 1.0 but even their pre-stable versions were really quite comprehensive.
Purely anecdotal, but in Android (Cyanogenmod) vs webOS power management I've found webOS beats it hands down. I just turned my Touchpad on now for the first time in a few days and the meter is reading as 43%. I don't use it heavily, usually just in hour or two sessions and charge it about once every four or five days.
Email nor anything related to core email protocols do not need to be fixed or redesigned. It's doing what it was supposed to be used for and still doing it very well. Over the years desktop and web mail people have added too much and its 70s design idea of anyone can send mail to any other's inbox (btw, creative idea at the time worked till 2000s) have cooperatively decreased its usage.
We still need this universal and mature protocol but we should do a different thing for communication. period.
Hard as in writing code in three different languages. Apart from that I think tech community giving too much credit for Apple and especially Google. They could have fixed this native vs html5-js-css thing two versions ago.
Three different languages that provide vastly superior runtime libraries and tooling that facilitate implementing first-class applications on the target platform.
I agree that supporting multiple platforms is suboptimal, but instead choosing a suboptimal common platform isn't any better.
We already tried that once with Java desktop applications, and Java at least tried to provide a viable common widget/platform toolkit.
Sorry. What I meant was, web applications have been a successful cross platform way of delivering software for the past 10 years. I don't see any reason why it can't continue on mobile, especially now that the hardware is catching up.
I've searched a little while and found that it has no support for camera (or sensors) in mobile devices. It looks like HAXE/NME is heavily geared towards game development.
Apple is kind of a special case for a few reasons. There are definitely parallels though.
Apple shot to popularity in America first before Japan, leading the way for Japanese consumers.
Insanely great customer service is definitely a big part of Apple's way of doing business, considering the genius bar strategy.
They also have a large team on the ground here. Steve Jobs identified Japan as a huge opportunity, and flew here to hire the Japan CEO himself years and years ago.
Actually they don't have much choices on dropping some specific email features to make UI better. Anyways I think it's just like MS Metro. One cannot say OMG this is cool as we say with Apple properties but people continue to use those (inferior) UIs.
