Following
Over the last year we've been putting every new major mobile platform through a battery of tests to assess how they stack up as an HTML5 application platform. So far, it's been thumbs up on Apple, RIM and HP tablets and thumbs down on Android tablets. But we're still crossing our fingers that the Ice Cream Sandwich release of Android will make the grade.
To date, we haven't spent time on Windows phones, mostly because the Windows Phone 7 browser was so poor …
…around... We need competition, we deserve options. Microsoft, Google, Apple, Opera and Mozilla are all vital to the ecosystem of the web; to push each other to become better and to foster innovation that everyone gains from. I work for Mozilla, but I would definitely not want to see Firefox (or Gecko's rendering engine) as the only one out there. We need a balance to together form and grow the future of everyone.
To me, when it comes to just one owner, one rendering engine …
This means Apple's native APIs are accessible from Node, so you could create GUI apps for Mac OS. There are examples out there of GUI code already: cocoa-hello-world2.js .
SockJS
SockJS (License: MIT ) is a WebSocket emulation library that attempts to provide simple APIs for both server and clients, while remaining as close to the WebSocket API as possible. It's designed to work from behind restrictive corporate proxies, and browsers that …
…native app for say iOS using CocoaTouch, and the really excellent tools Apple has been working on since the NeXT days. But it's also important to note that for many categories of applications, for example games, these apps use technologies like Unity3D, so in a sense many of the most successful, most engaging applications people use on say iOS aren't native. I think it really comes down to the tools - and for developing apps using web technologies, these are far less sophisticated …
HP washing its hands of webOS: discontinues tablets, Pre phones
Mozilla Hacks Weekly, August 18th 2011
For you Swedes out there: Att vara två dömande ögon i ett designerhem - alldeles lysande skrivet!
Thoughts on Android and Firefox in emerging markets
speak.js: Text-to-Speech on the Web ? Mozilla Hacks - the Web developer blog
Why working at home …
…where big ideas were shot down for being too risky. Many of the folks at the top wanted to be another Apple, and you can't fight that war. Android has been so successful through a) hard work by engineers and b) a disruptive and very different business model. Java is yesterdays technology though, and if we saw webOS at Google I think that Android would have been even more than it is today. The interaction model is vastly superior. This doesn't mean that the user experience is …
…browser. And, as 3D transforms are hardware-accelerated, you can get a very decent framerate, even on ( Apple's) mobile devices.
This is an interesting point, because a lot of people have been frustrated at Canvas performance on iOS. Given the author's background in AS3, perhaps this library will appeal to Flash developers looking to build interactive content for mobile WebKit browsers?
Fayer
Fayer (License: dual MIT / GPLv2 ) is a library that helps selectively …
What does it mean for your relationships with Apple, Google, Microsoft?
We don't expect that it will affect our relationships with other organizations.
Does this replace work that's already being done on Web APIs for desktop and mobile?
We are already pushing hard on new Web APIs, and have been for some time. We'll continue to implement and standardize new APIs for Web content while the B2G project ramps up.
How is this different than the Webian Shell project? …
…component model for the web . Maciej Stachowiak ( Apple) outlined a number of a concerns with it. It seems still in the early stages, but this will eventually allow for better control of styling form controls and creation of your own controls (i.e. reusable components).
Olli Pettay ( Mozilla) put forward a proposal to replace mutation events . Everyone is in favor of replacing mutation events because of their complexity , but exactly how is still …
…biggest factor in going native is access to the burgeoning ecosystems surrounding each platform (like Apple's App Store or Google's Android Market). From a marketing and positioning perspective, being in those app stores and having access to those ecosystems is huge.
Obviously the downside to native is having to maintain lots of versions of the app — writing code for iOS is very different from writing code for Android — and having access to the resources to maintain those …
The Tech Reflector is a Social News website about Javascript. We're reading 40 blogs, so that you don't have to. - John, Editor.
