We’re pleased to announce the release of mozjpeg 2.0. Early this year, we explained that we started this project to provide a production-quality JPEG encoder that improves compression while maintaining compatibility with the vast majority of deployed decoders. The end goal is to reduce page load times and ultimately create an enhanced user experience for sites hosting images.
With today’s release, mozjpeg 2.0 can reduce file sizes for both baseline and progressive JPEGs by 5% on average compared to those produced by libjpeg-turbo, the standard JPEG library upon which mozjpeg is based . Many images will see further reductions.
"The ousting of Eich, the DRM problem -- all those imbroglios have tarnished the image of Firefox," said Google+ blogger Alessandrom Ebersol. So, on one side, "agnostic users left Firefox because they were told its new CEO was a conservative bigot. The folks who care about freedom, privacy and open Internet left Firefox because of the DRM module to play Netflix.
Mozilla organized two national events in India during the month of June this year: Indic FirefoxOS L10n Sprint 2014 and Mozcamp Beta 2014.
Indic FirefoxOS L10n Sprint 2014 was more of an implementation-based sprint with the goal to motivate Indic language localization teams to translate strings for its upcoming Firefox OS based $25 phone. Mozcamp India Beta was an event for meeting mentors, planning for the future, and strategizing Mozilla’s mission in India.
For KDE desktop users unhappy with the level of integration with Mozilla's Firefox web browser, the situation might finally be changing.
There's been a bug going back to early 2002 about properly integrating Mozilla with KDE, "Mozilla has 'Windows Integration' on win32, I believe it should have such a thing on KDE as well (gnome folks, feel free to file your own bug). We should at least provide an icon in the KDE menu, perhaps we could even tell KDE that some file types can be opened with Mozilla..." That bug, Mozilla Bug 140751, has been open for the past twelve years and finally now might be inching closer to being resolved.
The Deepin Desktop Environment is written using Google's Go language and makes use of heavy HTML5. DDE also uses Compiz as its compositing window manager. As in the past some desktop environments / window managers have impaired the full-screen Linux gaming performance, I ran some simple Linux gaming benchmarks on Sunday to see if the Deepin 2014 performance differed at all from upstream Ubuntu 14.04 LTS. Ubuntu 14.04 was tested with the stock Unity 7.2 desktop using Compiz, GNOME Shell 3.10.4, and Xfce 4.10 all from the stock Trusty Tahr archive.
At this year's Great Wide Open conference, Steve Klabnik gave a talk about Mozilla's Rust programming language. Klabnik previously authored an introductory Rust tutorial entitled Rust for Rubyists, and this talk serves a similar purpose. However, instead of being Ruby focused, this talk was aimed at programmers in general. Hence the talk's title: Rust for $LANGUAGE-ists.
This is a maintenance release that fixes major bugs discovered and reported by the community from the previous stable version, antiX MX 14.1.1, and updates various packages.
According to the quite small changelog, antiX MX 14.2 updates the powerful LibreOffice suite to the latest stable version, 4.2.5, updates the documentation, and adds support for Broadcom wireless devices on the CD image.
Folks from Collabora and Red Hat have been working on making Firefox on Gtk+ 3 a thing. See Emilio’s blog post for some recent update. But getting Firefox to build and run locally is unfortunately not the whole story.
I’ve been working on getting Gtk+ 3 Firefox builds going on Mozilla build infrastructure, and I’m proud to announce today that those builds are now going through Mozilla continuous integration on a project branch: Elm, and receive the same automated testing as mozilla-central.
And when I said getting Firefox to build and run was unfortunately not the whole story, I meant it: if you click on the Elm link above, you’ll notice that there’s a lot of orange, when it should be all green.
The issue we had to solve is that GTK+ 2 and GTK+ 3 cannot be loaded in the same address space. Moving Firefox from GTK+ 2 to GTK+ 3 isn’t a problem, as only GTK+ 3 gets loaded in its address space, and everything is fine. The problem comes when you load a plugin that links to GTK+ 2, e.g. Flash. Then, GTK+ 2 and GTK+ 3 get both loaded, GTK+ detects that, and aborts to avoid bigger problems.