This looks cool: Mozilla has released a translation tool as an add-on for Firefox that can do web page translation locally instead of sending data to the cloud! It’s based on Project Bergamot and implemented in WebAssembly.
IMO translation is one of those things like speech recognition that ideally should have always have been local (for obvious privacy reasons), but the processing and data just wasn’t there yet when Google Translate and similar services launched.
I never thought I’d see Microsoft throw in the towel on their browser engine. Or that, by the time it happened, I’d see that as a bad thing.
But it’s true: like Opera did a few years ago, Microsoft is dropping not only the old Internet Explorer engine, but the newer Edge engine, and will be building Edge on Chromium going forward. That means Edge, Chrome, Opera and Safari are all built on the same codebase. (Chromium split from Apple’s WebKit a while back, but they still have a lot in common.)
Monoculture is still a problem, no matter who runs it. We’re already at the point where webdevs are treating Chrome like the defacto standard, the way they did IE6 back in the day.
Firefox is going to be even more important in the future, ensuring that the web continues to be built on interoperable standards instead of one stakeholder’s goals.
Mozilla is a non-profit organization, and like many, they’re running a year-end donation drive. Now is a good time to contribute to their mission to keep the internet and the web open. (I’ve already made my annual donation to them.)
I think I may want to finally shut down or retool that old Alternative Browser Alliance site I ran during the Second Browser War. The last time I made a significant update to it, Chrome was the new upstart.
A good tech support one-liner from (The customer is) Not Always Right: A Flock Of Explorers On A Safari Singing Opera.
Me: “Alright, so what browser are you using to view your websites?”
Customer: “Mozzarella Firefox!”
Lisa the Barbarian: A woman poses with a viking helmet and a sword…and an Opera Browser T-shirt. (via Espenao’s Opera the Barbarian)
CNET UK presents The 30 dumbest videogame titles ever, including “Spanky’s Quest,” “Ninjabread Man,” “How to Be a Complete Bastard,” “Touch Dic” and “Attack of the Mutant Camels.” (via Slashdot).
Cowboy Bebop at His Computer — examples of media articles (especially about pop culture) in which the reporters (and editors) clearly didn’t do their research. The title comes from a caption on a still from Cowboy Bebop. That’s not the character’s name, and the character in question is female. It probably is her computer, though.
Archeophone Records: Actionable Offenses: Indecent Phonograph Recordings from the 1890s. Comedians telling bawdy stories, recorded on wax cylinders. The write-up is PG, though the track list looks to be at least PG-13. Looked up after reading NY Times’ article on voice recordings from 1860 (recorded with ink on paper), which is also worth a read. (via Slashdot)
Edit: Forgot to list the (temporary?) resurrection of 1994-era home.mcom.com, the website of what was then Mosaic Communications Corporation and would soon be renamed Netscape. Subsequently picked up by Boing Boing and Slashdot. For more old web browsers, check out the Browser Archive at evolt.org. (via Justin Mason)
One of the biggest complaints about Firefox since 1.5 was released has been its high memory usage. Go to a forum anywhere and you’ll get people griping about “have they fixed the leak yet?”
It is, of course, much more complicated than that. There are caches, fragmentation, places where memory is used inefficiently, bunches of small leaks, leaks that only happen under specific circumstances, leaks in extensions, leaks triggered by combination of extensions, etc.—not one single leak that can be fixed. And then there was the unfortunate post in which one Mozilla developer (I’m too lazy to look up who) pointed out that 1.5 stored more information in memory, and that probably had a bigger impact on total memory size than actual leaks, which many people on the Internet jumped on as “It’s not a bug, it’s a feature.” (Why should they bother to read what was actually stated, when they can just read a misleading but sensational summary?)
A lot of the small leaks were patched in bugfix releases for 1.5 and 2.0, but really big changes are coming in Firefox 3. Mozilla’s Pavlov has written a detailed post on Firefox 3 Memory Usage, describing the different categories of memory improvements that have been made in the Firefox 3 development cycle.
I wouldn’t be surprised to find that this is one of the big reasons Firefox 3 has taken so much longer than previous releases. I suspect it’s time well spent, though, and users will be happier with a later, lighter Firefox than with one that shipped earlier, but used just as much memory.
