Subject: General Tech | October 29, 2013 - 12:27 PM | Jeremy Hellstrom
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.
"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:
- Leak: Almost a Third of Samsung Galaxy Gear Smartwatches Are Being Returned @ Slashdot
- Apple Blocks Lawrence Lessig's Comment On iOS 7 Wi-Fi Glitch @ Slashdot
- Building a Hackintosh The Easy Way @ Techspot
- Thermaltake Tt eSPORTS Battle Dragon Bag Review @ OCC
- 1Sheeld Uses Your SmartPhone as an Arduino Accessory @ Hack a Day
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, Mobile | May 7, 2013 - 12:07 AM | Scott Michaud
Tagged: unreal engine, firefox, asm.js
If, on the other hand, you wish to see an example of a large application compiled for the browser: would Unreal Engine 3 suffice?
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.
- 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
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!
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: General Tech | February 21, 2013 - 12:27 PM | Jeremy Hellstrom
"Mozilla's Firefox web browser now includes a built-in PDF viewer - allowing users to bin plugins from Adobe and other developers.
Here is some more Tech News from around the web:
- Seagate joins OpenStack foundation and Open Compute Project @ The Register
- BlackBerry squashes W-TIFF-F bug that's ripe for malware squirters @ The Register
- Nikon D7100 hands-on preview @ Hardware.info
- Giveaway at Rbmods together with Cm Storm
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 | November 17, 2012 - 05:53 AM | Tim Verry
Tagged: wine, windows, ubuntu, silverlight, Netflix, linux, firefox
One of the major hurdles preventing me from switching to Linux completely (despite my love for Mint) has been Netflix support. While there is a Silverlight-equivalent called Moonlight for the Linux operating system, it does not support the necessary DRM aspects to facilitate Netflix Instant Streaming. Aside from installing VirtualBox and booting an instance of Windows (which basically defeats the purpose of switching), Linux users have not been able to stream Netflix shows.
Thanks to a Linux developer by the name of Erich Hoover, there is a ray of hope for Linux users that want to take advantage of the streaming side of their Netflix subscriptions. Using a patched version of WINE (Wine Is Not An Emulator), Firefox, and an older version of Microsoft Silverlight, he was able to get Netflix streaming to work without breaking the DRM. That’s good news as it means that even though it is not officially supported, Netflix is not likely to actively break or fight it.
Netflix Instant Streaming running on Ubuntu 12.10 (32-bit).
Currently, it has been tested on the 32-bit version of Ubuntu 12.10, but other distros are likely to work as well. Users will need to compile WINE from source, apply five patches, and then install Firefox 14.0.1 and Silverlight 4. Right now, there is no GUI or pre-compiled version, and at least the first few steps require the use of the terminal. Thankfully, I Heart Ubuntu has put together a step-by-step guide outlining exactly what you need to type into the terminal to get Netflix streaming up and running. The site notes that the WINE patching process could take a good chunk of time if you are on an older computer. Further, Silverlight 5 does not work, so using the older version is necessary.
This is great news for the Linux community, and along with the Steam for Linux beta things are definitely looking up and moving in a positive direction for the open source operating system. Obviously, this is far from native support, but it is a huge improvement over previous workarounds. A PPA is also reportedly in the works to make the installation of the patched WINE version even easier for those not comfortable with the terminal. Until then, check out the I Heart Ubuntu guide for the full setup details.
The developer asks that you donate to the WINE Development Fund if you find his Netflix support patches useful.
Image credit: iheartubuntu