Mozilla Approves Plans for 64-Bit Firefox on Windows

Subject: General Tech | October 6, 2014 - 03:45 AM |
Tagged: windows, mozilla, firefox, 64-bit

If you had a reason, Mozilla has been compiling Firefox Nightly as a 64-bit application for Windows over the last several months. It is not a build that is designed for the general public; in fact, I believe it is basically only available to make sure that they did not horribly break anything during some arbitrary commit. That might change relatively soon, though.

Mozilla_Firefox_logo_2013.png

According to Mozilla's "internal", albeit completely public wiki, the non-profit organization is currently planning to release an official, 64-bit version of Firefox 37. Of course, all targets in Firefox are flexible and, ultimately, it is only done when it is done. If everything goes to schedule, that should be March 31st.

The main advantage is for high-performance applications (although there are some arguments for security, too). One example is if you open numerous tabs, to get Firefox's memory usage up, then attempt to load a Web applications like BananaBread. Last I tried, it will simply not load (unless you clean up memory usage somehow, like restarting the browser). It will run out of memory and just give up. You can see how this would be difficult for higher-end games, video editing utilities, and so forth. This will not be the case when 64-bit comes around.

If you are looking to develop a web app, be sure to check out the 64-bit Firefox Nightly builds. Unless plans change, it looks like you will have even more customers soon. This is unless, of course, you are targeting Mac OSX and Linux, which already have 64-bit binaries available. Also, why are you targeting specific operating systems with a website?

Source: Mozilla

Intex Cloud Fx Is a $35 Firefox OS Phone (not for USA)

Subject: General Tech, Mobile | September 13, 2014 - 10:12 PM |
Tagged: mozilla, intex, Firefox OS, firefox, cloud fx

If you were on a mission to make the cheapest possible mobile phone, you would probably not do much better than Intex Cloud Fx. Running Firefox OS, it will cost users about $35 to purchase it outright. Its goal is to bring the internet to places which would otherwise have nothing.

Intex-Cloud-FX-2.jpg

I believe the largest concession made by this phone is its RAM -- 128 MB. Yes, I had a computer with 32 MB of RAM and it browsed the internet just fine (on Netscape Navigator 2 through 4). I also had a computer before that (which was too slow to run Windows 3.1 but hey it had a turbo button). This is also the amount of RAM on the first and second generation iPod Touches. Nowadays, it is very little. Ars Technica allegedly made it crash by scrolling too fast and attempting to run benchmarks on it. This leads into its other, major compromise: its wireless connectivity. It does not support 3G. Edge is the best that you will get.

Other than those two points: it has a 1 GHz Spreadtrum SoC, 46MB of storage, a 2MP camera, and a 1250mAh battery. You do get WiFi, Bluetooth, and a microSD card slot. It also supports two SIM cards if necessary.

Again, at $35, this is not designed for America or Western Europe. This is for the areas of the world that will probably not experience the internet at all unless it is through a mobile phone. For people in India and Asia, it is about the lowest barrier to entry of the internet that is possible. You can also check out phones from other partners of Mozilla.

Source: Ars Technica

Firefox Developer Tools Can Debug Non-Mozilla Browsers

Subject: General Tech | September 11, 2014 - 04:22 PM |
Tagged: firefox, mozilla, web browser, web development

Well this is an interesting feature. Mozilla, like all browser vendors, has been constantly enhancing their web development tools. They are quite impressive, allowing anyone to debug any page, including WebGL shader replacement, audio network manipulation, and injecting Javascript, HTML, and CSS at run time. Firefox OS and Firefox for Android developers were even able to remotely connect to a desktop Firefox browser as if it were an IDE (which it really is these days). Today, Mozilla announced (via their Hacks blog) early support for remote debugging Safari on iOS and Google Chrome on Android.

The currently supported tools are: "Inspector", which allows searching, modifying, and injecting HTML and CSS; "Debugger", which debugs and injects Javascript; and "Console", which displays console output from the open tab and executes individual Javascript statements (which can be multi-line with shift + enter). You cannot, for instance, modify individual draw calls on a running 3D game, like you can with the same tools when manipulating a Firefox tab, but this is still pretty impressive for cross-vendor.

Remote Debugging for Safari on iOS and Chrome on Android is available in early development on Firefox Nightly with an optional extension.

Source: Mozilla

Firefox 29 Launches with Australis Interface and Gamepad

Subject: General Tech | April 30, 2014 - 03:52 AM |
Tagged: mozilla, gamepad, firefox

After three years' reign, the orange Firefox button has been retired by Mozilla. Firefox 29 introduces the new Australis interface, with its curved tabs and a simple menu button comprised of three horizontal lines (the "Hamburger Icon"). The interface missed its targets a few times but is finally here.

ilovetheweb.png

Obviously, Australis makes the browser look more like Google Chrome (and less like Opera). Users of Mozilla's Thunderbird will also find it more familiar as that program skipped Firefox 4's direction and immediately adopted parts of Australis as they developed. Thunderbird still lacks a few bits and pieces, its development having slowed since its transition to Extended Support. But this is not about Thunderbird -- it is about Firefox.

In terms of actual features, Australis brings a new Bookmarks button, which is basically two buttons, and is pretty slick to both add and access links to favorite web addresses. The little star-dropping animation is a subtle hint to the user that a bookmark has been added to the list, accessed by the right-most button. Many users will be upset by the removal of the Add-on Bar, a place where extensions can leave a button or two without clogging the rest of the interface. Mozilla seems to expect that extensions, if they absolutely must leave a button, will cram it next to the gigantic location bar (or less-gigantic search bar); that, or affected users will just install an Add-on Bar extension.

Also in Firefox 29 is the finalized, and enabled by default, Gamepad API. With it, web games can be controlled with devices such as the Xbox 360 controller. If you want to see a geeky example, one is available at html5gamepad.com. This website lists every compatible game input device and their current state. In my testing, Firefox 29 was able to detect both my Xbox 360 controller and my Thrustmaster T-16000M joystick -- and register their inputs independently.

There's not really anything, from the technical side of things at least, to prevent split-screen gaming in the browser. Detecting the input devices did not even require restarting the browser, although that is a good troubleshooting step, as Firefox detected it immediately after I plugged it in and pressed a button. The flight stick, probably because it has never been attached to this instance of Windows before, required the good old unplug and replug of its USB cord after Windows "Add New Hardware" finished in order to register input. It is not perfect, but still pretty good.

Firefox 29 launched in the middle of the night on Tuesday, April 29th. It is free and, if Firefox is set to automatically update, you probably already have it. If not? Get it.

Source: Mozilla

Need another reason to upgrade from WinXP? You might be stuck with IE

Subject: General Tech | October 29, 2013 - 12:27 PM |
Tagged: winxp, firefox, chrome, browser

With 160 days remaining until the current official support expiration for WinXP unless you are willing to pay for the privilege of getting critical updates there is only a little time left in which third party providers need to continue support for the aging OS.  Two of the most noticeable of these will be Firefox and Chrome, both of which will be discontinuing development for their browsers on WinXP.  Their older versions will still work but will slowly succumb to more and more security vulnerabilities as they are discovered but not patched for WinXP.  This may not be the straw that breaks XP's back but recall that YouTube abandoning IE6 support was one of the driving forces behind the decline of that browser.  Slashdot comments for your entertainment here.

An update to this information does show that you have a while to go before this is a major concern as Firefox does not have a specific date in mind and Chrome is extending development for a few years yet.  You should still really consider upgrading to Win7 in the near future.

winxp.jpg

"While Windows XP is still going strong the sun is rapidly setting on this old platform fast. Firefox plans to end support for XP which means no security fixes or improvements. Chrome is being discontinued a little later as well for Windows XP. Windows XP has its die-hard users refusing to upgrade as they prefer the operating system or feel there is no need to change."

Here is some more Tech News from around the web:

Tech Talk

Source: Slashdot

Firefox 23 Shipped. Nice Icon. Nice Icon. Nice Icon. Nice Icon.

Subject: General Tech | August 7, 2013 - 03:47 AM |
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.

Firefox-23-logo.png

Also removed was the preference to disable JavaScript. Fear not, users will still be able to modify the setting by diving into about:config. Interested users will actually need to, because this change will revert the setting to the default on position if users had previously disabled it. I assume this was a user experience decision for users who temporarily disabled Javascript right before updating Firefox; users tech savvy enough to want Javascript off will know to dive in to the settings registry.

Or just, you know, install NoScript or something.

Firefox-23-memory.png

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.

Firefox-23-dev.jpg

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.

Source: Mozilla

Unreal Engine 3 compiled to asm.js

Subject: Editorial, Mobile | May 7, 2013 - 12:07 AM |
Tagged: unreal engine, firefox, asm.js

Over the weekend we published a post which detailed Javascript advancements to position the web browser as a respectable replacement for native code. Asm.js allows for C-like languages to be compiled into easily optimized script executed at near native performance on asm.js-aware browsers, but are still functional as plain Javascript otherwise. If you wish to see a presentation about asm.js and compiling native code into web code, check out an online slideshow from Alon Zakai of Mozilla.

If, on the other hand, you wish to see an example of a large application compiled for the browser: would Unreal Engine 3 suffice?

UnrealHTML5.jpg

Clearly a computer hardware website would take the effort required to run a few benchmarks, and we do not disappoint. Epic Citadel was run in its benchmark mode in Firefox 20.0.1, Firefox 22.0a2, and Google Chrome; true, it was not run for long on Chrome before the tab crashed, but you cannot blame me for trying.

Each benchmark was run at full-screen 1080p "High Performance" settings on a PC with a Core i7 3770, a GeForce GTX 670, and more available RAM than the browser could possibly even allocate. The usual Firefox framerate limit was removed; they were the only tab open on the same fresh profile; the setting layout.frame_rate.precise was tested in both positions because I cannot keep up what the state of requestAnimationFrame callback delay is; and each scenario was performed twice and averaged.

Firefox 20.0.1

  • layout.frame_rate.precise true: 54.7 FPS
  • layout.frame_rate.precise false: 53.2 FPS

Firefox 22.0a2 (asm.js)

  • layout.frame_rate.precise true: 147.05 FPS
  • layout.frame_rate.precise false: 144.8 FPS

Google Chrome 26.0.1410.64

  • Crashy-crashy

For Unreal Engine 3 compiled into Javascript we notice an almost 3-fold improvement in average framerate with asm.js and the few other tweaks to rendering, Javascript, and WebGL performance between Firefox 20 and 22. I would say that is pretty enticing for developers who are considering compiling into web standards.

It is also very enticing for Epic as well. A little over a month ago, Mark Rein and Tim Sweeney of Epic were interviewed by Gamasutra about HTML5 support for Unreal Engine. Due in part to the removal of UnrealScript in favor of game code being scripted in C++, Unreal Engine 4 will support HTML5. They are working with Mozilla to make the browser a reasonable competitor to consoles; write once, run on Mac, Windows, Linux, or anywhere compatible browsers can be found. Those familiar with my past editorials know this excites me greatly.

So what do our readers think? Comment away!

Cloth simulations in Javascript, optimized for asm.js

Subject: General Tech, Mobile | May 4, 2013 - 06:47 PM |
Tagged: mozilla, javascript, firefox, asm.js

Web browsers are getting really good at being general-purpose application platforms.

You can write most applications in web standards if you are willing to give up some level of performance for the gained ubiquity. HTML5, Javascript, and CSS are very full featured; WebGL and WebCL extend functionality by backing apps with surprising GPU horsepower; WebAPIs such as gamepad, telephony, and accelerometer support also keep advanced hardware-specific features open to web developers.

asmjsdrool.png

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.

Javascript is often, simply, good enough.

Mozilla has recently added support for the draft asm.js in their Aurora prerelease channel for Firefox. The specification is designed to permit a subset of Javascript to be flagged for optimization in compatible browsers but otherwise execute as normal everywhere else. It is also possible to compile more native code into Javascript if you can afford the ever-decreasing performance hit. Early implementations of asm.js execute code compiled from C within half of native performance.

asmjs.png

Because... pants.

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.

James Long of Mozilla compiled a cloth simulation into this Javascript subset. It will run in multiple browsers but will perform better in Aurora both in cloth precision and, as I have found, responsivity.

Check it out, imagine what you could be doing in your web browser in the near future.

Source: James Long

Happy 0th Birthday Firefox OS

Subject: Editorial, General Tech, Systems, Mobile, Shows and Expos | February 26, 2013 - 04:19 AM |
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.

firefoxos.jpg

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.

Source: Mozilla

Mozilla Rolls Out Firefox 19 Web Browser With Built-In PDF Viewer

Subject: General Tech | February 22, 2013 - 05:11 AM |
Tagged: web browser, pdf viewer, mozilla, firefox

Mozilla recently rolled out Firefox 19 to its stable browser channel, bringing several new features and bug fixes to the masses. The most prominent new feature is a new built-in PDF reader that is now enabled by default. Using the PDF.js javascript libraries, the reader converts PDF files into HTML5 web pages. It is nice to see Mozilla incorporating the reader in the browser by default, eliminating the need for users to use Adobe Reader or other browser plug-ins (like this one we covered previously).

Firefox 19 PDF Viewer.jpg

 

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.

Source: Mozilla