Subject: General Tech | August 20, 2013 - 04:37 PM | Tim Verry
Tagged: zte open, zte, smartphone, msm7225a, mozilla, Firefox OS
Mozilla has been working on its mobile Firefox OS for about a year, and smartphones running the OS are starting to become available stateside. The first bit of hardware running Firefox OS is the ZTE Open, which launched last week for $79.99 exclusively on eBay. Unfortunately, the limited stock ZTE made available is already gone, and there is no word on when more smartphones will be available. (However, in typical eBay fashion, users are turning around and selling the $80 phone for $170 if you really want to get your hands on it...)
According to the eBay listing, ZTE managed to sell 985 of the orange ZTE Open smartphones.
The ZTE Open comes in blue or orange and features low end specifications. Fortunately, Firefox OS and its HTML5 applications do not demand much hardware. On the outside, the ZTE Open has a 3.5” TFT touchscreen with a resolution of 480 x 320, a single home button sitting below the display, and a 3.15 MP rear camera. Internal specifications include a MSM7225A SoC with an ARM Cortex-A5 CPU clocked at 1Ghz and Adreno 200 GPU along with 2GB of internal storage expandable by micro SD card. Other specifications include 802.11n Wi-Fi, Bluetooth 2.1, 3G cellular radio, a 1200 mAH battery, and various sensors (accelerometer, ambient light, and GPS). The Firefox OS smartphone measures 114 x 62 x 12.5mm.
Seeing the ZTE Open sell out of its limited stock in such a short amount of time suggests that there is some positive amount of demand for Firefox OS from enthusiasts, but the smartphone and OS platform still has a long road ahead of it before it becomes a true threat to Android and iOS. Much like the fabled Ubuntu Phone, more than enthusiast demand will be needed, along with support from US carriers and app developers. With that said, it is a good first step into the US market and I hope ZTE makes more phones available soon.
Read more about Mozilla's Firefox OS.
Subject: General Tech | August 7, 2013 - 03:47 AM | Scott Michaud
Tagged: firefox, mozilla
The hottest version of Firefox, for the next 6 weeks, was just released to the world and much discussion came with it. This version, most controversially, removed the <blink> element. What a terrible destruction of HTML history. How can web developers ever make fun of old VCRs? Resort to... CSS?
Pardon me, I think I am going to be sick. Oh wait, that's just not-epilepsy.
While we are talking about... about:... about:memory (hmm, this sentence reminds me of <blink>) has been given a slight graphical overhaul. The controls are now on the top of the report which allows users to know they exist without scrolling all the way down. These buttons have some legitimate use for many users: they can now manually force Firefox to clean up its memory footprint.
Web Developers also have a few new tools to play with including, but not limited to, tracing network traffic too and from their site. This was already possible with various console configurations but not nearly as aesthetically pleasing or even usable. If your element has very big horizontal bars, it takes a long time to load and is a good candidate to optimize first.
In all, Mozilla seems to be very productive with the number of improvements in just six weeks of development time. The next release is expected to leave Beta Channel on, or near, September 17.
Subject: Editorial, General Tech | July 31, 2013 - 08:03 PM | Scott Michaud
Tagged: Privacy, mozilla, DNT
Mozilla Labs is researching a new approach to the problem of privacy and targeted advertising: allow the user to provide the data that honest advertisers intend to acquire via tracking behavior. The hope is that users who manage their own privacy will not have companies try to do it for them.
Internet users are growing concerned about how they are tracked and monitored online. Crowds rally behind initiatives, such as Do Not Track (DNT) and neutering the NSA, because of an assumed promise of privacy even if it is just superficial.
DNT, for instance, is a web developer tool permitting honest sites to be less shy when considering features which make privacy advocates poop themselves and go to competing pages. Users, who were not the intended audience of this feature, threw a fit because it failed to satisfy their privacy concerns. Internet Explorer, which is otherwise becoming a great browser, decided to break the standard by not providing the default, "user has not specified", value.
Of course, all this does is hands honest web developers a broken tool; immoral and arrogantly amoral sites will track anyway.
Mozilla Labs is currently investigating another solution. We could, potentially, at some point, see an addition to Firefox which distills all of the information honest websites would like to know into a summary which users could selectively share. This, much like DNT, will not prevent companies or other organizations from tracking you but rather give most legitimate situations a fittingly legitimate alternative.
All of this data, such as history and geolocation, is already stored by browsers as a result of how they operate. This concept allows users to release some of this information to the sites they visit and, ideally, satisfy both parties. Maybe then, those who actually are malicious, cannot shrug off their actions as a common industry requirement.
Subject: General Tech, Mobile | May 4, 2013 - 06:47 PM | Scott Michaud
Web browsers are getting really good at being general-purpose application platforms.
I can see the web developers drooling already.
But even though performance lags behind reasonable native environments, the divide is rapidly shrinking. Many applications have reached or exceeded the saturation of useful performance at the same time as browser developers narrow the gap between native performance and themselves.
According to David Herman of Mozilla, one of the lead authors of the ASM.js draft, the specification also allows for multithreading through web workers. Applications can take advantage of multiple hardware threads in this way, and potentially other methods as they continue development. I would expect this is especially relevant for mobile devices which tend to have relatively many cores considering their single threaded performance.
Check it out, imagine what you could be doing in your web browser in the near future.
Subject: Editorial, General Tech, Systems, Mobile, Shows and Expos | February 26, 2013 - 04:19 AM | Scott Michaud
Tagged: Firefox OS, mozilla, firefox, MWC, MWC 13
Mobile World Congress is going on at Barcelona and this year sees the official entry of a new contender: Firefox OS.
Mozilla held their keynote speech the day before the official start to the trade show. If there is anything to be learned from CES, it would be that there is an arms race to announce your product before everyone else steals media attention while still being considered a part of the trade show. By the time the trade show starts, most of the big players have already said all that they need to say.
If you have an hour to spare, you should check it out for yourself. The whole session was broadcast and recorded on Air Mozilla.
The whole concept of Firefox OS as I understand it is to open up web standards such that it is possible to create a completely functional mobile operating system from it. Specific platforms do not matter, the content will all conform to a platform of standards which anyone would be able to adopt.
I grin for a different reason: should some content exist in the future that is intrinsically valuable to society, its reliance on an open-based platform will allow future platforms to carry it.
Not a lot of people realize that iOS and Windows RT disallow alternative web browsers. Sure, Google Chrome the app exists for iOS, but it is really a re-skinned Safari. Any web browser in the Windows Store will use Trident as its rendering engine by mandate of their certification rules. This allows the platform developer to be choosey with whichever standards they wish to support. Microsoft has been very vocally against any web standard backed by Khronos. You cannot install another browser if you run across a web application requiring one of those packages.
When you have alternatives, such as Firefox OS, developers are promoted to try new things. The alternative platforms promote standards which generate these new applications and push the leaders to implement those standards too.
And so we creep ever-closer to total content separation from platform.
Subject: General Tech | February 22, 2013 - 05:11 AM | Tim Verry
Tagged: web browser, pdf viewer, mozilla, firefox
Additionally, Mozilla has fixed several bugs and improved performance. The browser will now start-up more quickly than previous versions, and a WebGL drawing operation error has been corrected, for example. Further, Firefox 19 now recognizes more CSS features including @page and support for fixed-width text transformations. A new debugger has also been added to Firefox 19, which should help add-on developers test their code. Also in interesting news, mobile users running Firefox for Android will also be pleased to know that Mozilla has relaxed the CPU clockspeed requirement to a mere 600 MHz–allowing the mobile browser to run on even more Android devices.
The new version is available for download from the Mozilla website.
Subject: Mobile | January 10, 2013 - 04:23 AM | Tim Verry
Tagged: zte, smartphone, mozilla, html5, Firefox OS, ces 2013, CES
Mozilla has been interested in smartphones for awhile now. The Boot2Gecko project has since transitioned to Firefox OS, and now the company is nearly ready to officially release the code and begin getting it onto smartphones and competing with the current giants of Android, iOS, and WP8. According to The Verge, who talked with the company at CES, Mozilla’s mobile operating system will be released within the next two weeks.
The Verge checks out a prototype phone running Firefox OS.
The mobile OS is coded in HTML5 and uses HTML5 applications. While Mozilla plans to introduce an app store to curate things, currently users are able to find run web apps on the Internet. Do not expect Firefox OS to take the smartphone world by storm this year, however. Mozilla will reportedly restrict the mobile OS to low end hardware, with up to 800MHz single core ARM processors. Further, no OEM phones are scheduled for a US release this year (so far). ZTE has confirmed that it is pursuing handsets with Firefox OS pre-installed. Currently, the company is planning at least one low end smartphone release in Europe late this year. US residents will likely not see Firefox OS shipping with phones until next year at the earliest, depending on how well the phones do in the developing markets and when Mozilla opens up the hardware restrictions to higher-end devices.
Until then, you can check out Firefox OS for yourself in a simulator using the Firefox web browser and a browser add-on called the Firefox OS Simulator. To test it out, open up a Firefox browser window and install the add-on from this webpage. Then click the Firefox button and navigate to Web Developer > Firefox OS Simulator. Then, on the left hand side of the window that opens, click the stopped button to start the simulator. A new window will open running the mobile operating system.
The Dialer, Messages, and Web Browser apps in Firefox OS.
PC Perspective's CES 2013 coverage is sponsored by AMD.
Follow all of our coverage of the show at http://pcper.com/ces!
Subject: General Tech | December 26, 2012 - 04:34 PM | Tim Verry
Tagged: mozilla, firefox, browser, Internet, 64-bit
A month ago Mozilla announced that it would no longer release 64-bit versions of its popular Firefox web browser due to a lack of resources. While the stable versions for Windows were 32-bit, nightly builds were available to enthusiasts that were 64-bit and could take advantage of more than 4GB of memory.
Mozilla developer Benjamin Smedberg stated that there was significant negative feedback from the community over the decision to axe 64-bit nightlies. While Mozilla has reaffirmed that they do not have the resources to support 64-bit builds, the developers are proposing a compromise that they hope will assuage users. In short, the Release Engineering team will continue to build 64-bit versions of the Firefox browser, but Mozilla will consider it a teir 3 build and the support is left up to the community.
Currently, the plan regarding 64-bit versions of Firefox involves a forced migration of existing 64-bit users to 32-bit versions via the automatic browser updates. Then, after the migration date, users that want the 64-bit version will need to go and download it again. Once installed, users will be informed that it is not officially supported software and they are to use it at their own risk. Click-to-play plugins will be enabled in the 64-bit builds while the crash reporter will be disabled. Win64 tests and on-checkin builds of the browser will be discontinued.
Interestingly, all browser testing by Mozilla will be done on the 64-bit edition of Windows 8. Yet they are only testing and supporting 32-bit versions of Firefox. The current situation is less than ideal as the x64 Firefox browsers will not be supported by Mozilla, but at least the software will still be available for those that need it. For now, Waterfox is an option for those that need to install a 64-bit browser based on Firefox.
Does Mozilla’s decision to stop supporting the 64-bit Firefox browser affect you? What do you think of the offered compromise?
Subject: General Tech | November 22, 2012 - 01:03 PM | Jeremy Hellstrom
Tagged: mozilla, firefox, dumb, 64-bit
Once upon a time was a little company called Mozilla who had a browser that knew some tricks no other browser did. After a while the Mozilla foundation decided to split up several projects and the Firefox browser was born, again capable of things that no other browser was doing at the time. The other browsers were quick to pick up on these tricks and to emulate them, but Firefox held onto a respectable share of overall usage which slowly eroded as other browsers came onto the scene to steal away some of that share. Apparently this depressed Firefox as it decided to start on a steady diet of add-ons and stuffing extras in below the belt which eventually caused such bloating as to make those who cared about Firefox suggest it might want to think about slimming down a bit or at least wear something a little larger, maybe a size 64.
Instead, according to various sources such as DailyTech, Firefox has decided to dump all development of a 64-bit version of its browser. IE10 supports 64-bit, Opera supports 64-bit and Chrome does on Linux and is working on a Windows version for the near future, leaving Firefox in the company of Lynx. While the news stories are specific to the Firefox browser, it leaves one suspicious about the Firefox OS which is being developed for mobile devices; just what features are going to be abandoned as too hard to continue developing for.
"Fans of the non-profit Mozilla Foundation have waited... and waited... and waited more still, for Mozilla's popular Firefox browser to add 64-bit support. With pickup of 64-bit SKUs of Microsoft Corp.'s (MSFT) Windows operating system rapidly accelerating, it certainly seemed a 64-bit browser would be just around the corner.
Instead Mozilla has made the curious decision to pull the plug on the long-delayed project, while offering only small clues as to why the decision was made."
Here is some more Tech News from around the web:
- The 3D Printing Wars Begin @ MAKE:Blog
- Samsung brews half-asleep OCTO CORE phone brain MONSTER @ The Register
- Win OCZ RevoDrive 3 PCIe SSD and Kitguru fans! @ Kitguru
Subject: General Tech | March 15, 2012 - 08:14 AM | Tim Verry
Tagged: webM, web browser, mozilla, html5, h.264, firefox
Mozilla executives working for the foundation behind the Firefox web browser today announced that they would be giving in to the H.264 codec as the open WebM VP8 codec has lost the war. The H.264 and VP8 (part of WebM) codecs are used to encode and decode video files, and are especially important on mobile devices as Flash support is less ubiquitous (or totally absent if you're using Apple products). In the absense of flash, the web turned to the HTML5 standard which provides <code><video></code> tags that allow direct embedding of videos into websites. Also important is that H.264 has wide support for being hardware accelerated on many mobile devices, enabling smart phones to smoothly playback high quality files that the low power CPU portion of ARM SoCs would otherwise struggle with. This situation is also available to desktop users, but is less of an issue as processing power is not as scarce and can, ah, accommodate Adobe's Flash plugin (heh).
The downside, and where all the controversy arises from, is that the H.264 codec is not free and requires manufacturers or sites that stream H.264 videos for a fee to license it as well as users, though the actual cost for licensing is generally rolled into the cost of the OS, device, or other piece of purchased software. Further, because the HTML5 standard does not specifically define a set video codec, there is room for fragmentation. Adobe, Mozilla, and Google eventually would jump behind what is now known as the WebM standard, which is an open (and free) video codec (VP8) that would not require expensive licensing restrictions. On the other hand, Apple backed the H.264 standard. Mozilla would roll WebM into their browser but not H.264, meaning that users could view HTML5 videos using Firefox but not HTML5 videos encoded with the H.264 codec. Google, Apple, and Microsoft would support the H.264 codec for HTML5 videos, despite Google developing WebM (and the included VP8 video codec) and giving word of mouth support for WebM. This meant that Chrome users could view both WebM and H.264 based HTML5 video.
According to the article, Google promised to drop support for H.264 and move solely to the WebM VP8 codec to entice websites to move to the open codec. Unfortunately, the company never came through with that promise, and has continued to offer dual support while Mozilla was left holding the open source support banner and causing their users to suffer as a result. The article references a study by MeFeedia that suggests that as of December 2011, H.264 based HTML5 video accounts for 80% of the market, implying that WebM has already lost the war. Brendan Eich, Mozilla's Chief Technology Officer noted that WebM needed support from a larger entity than Mozilla, and it needed that support in the beginning. Especially with Apple heralding H.264, for mobile site publishers, WebM really needed heavy backing to compete with Apple's market share and influential support of H.264 to have a chance. He further stated that:
"it might not have worked then, even with Google on-side. Now, with just Mozilla going it alone, all we do is kill our mobile initiatives in order to appear pure...That does not serve our mission or users."
Mozilla is now looking to support H.264, if a bit grudgingly. At this point, not supporting H.264 is only hurting their users and market share and not furthering their push for WebM. After all, if users are forced to look at other browsers just to play videos, it will not be WebM that is the only open source software forgotten (rather, the entire Mozilla web browser will wain).
Granted, Google is not the only company to blame for VP8 not catching on, Adobe also failed to properly push the codec. Also, Google is allegedly continuing to develop VP8 and WebM. Right now; however, losing Mozilla's support seems to be the final nail in the WebM coffin and the recognition that H.264 is the dominant format. More information is available here.