Slashdot Mirror
Mozilla Reveals Firefox 4 Plans
Barence writes "Mozilla has given a breakdown of its plans for Firefox 4. Perhaps the most striking change to Firefox 4 is the user interface, which takes a great deal of inspiration from Google Chrome. 'Something UI designers have known for a long time is that the simpler an interface looks, the faster it will seem,' said director of Firefox Mike Beltzner during the presentation. Also mooted was the ability to give applications such as Gmail and Twitter their own permanent tabs for easy access, and the introduction of a 'switch to tab' button, allowing power users running hundreds of tabs to quickly find the one they want. Beltzner said Mozilla was also looking at replicating Chrome's tactic of silently updating the browser in the background, removing the annoying wait when Firefox first loads up."
You're probably thinking of "Fox Force Five", from Pulp Fiction
http://www.whysanity.net/monos/fox.html
Learning HOW to think is more important than learning WHAT to think.
h.264 and HTML5 aren't synonymous - HTML5 just provides a video container, the browser vendor decides what codecs to allow, so it's entirely possible to fully support HTML5 yet still have no h.264 support.
Seriously, what is the point of having Firefox then? The fact that I need to open new tab in Chrome in order to access some bookmark pisses me off and pretty much makes bookmarks pointless.
RTFGSR (google search results, for "chrome bookmark menu" and quit your whining.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
For those who don't want to rtfa, there's a video presentation on the director of firefox, Mike Beltzners blog: http://videos.mozilla.org/serv/air_mozilla/firefox4.ogg
Turn the bookmark toolbar on.
RIP America
July 4, 1776 - September 11, 2001
First, install the update when I shut down the browser. You're not wasting my time then because I'm done using it.
When you shut down the browser, you could be shutting down your computer.* Firefox doesn't want a SIGKILL from sudo shutdown -h now to make the updater leave the system in an inconsistent state. So if startup is unacceptable and shutdown is unacceptable, the only remaining solution is to do so in the background while the browser is in use.
* Not everybody is as lucky as you are to have proper driver support for hibernation. And some people apply security patches to their operating system kernels every month or two.
On any random day, I use the the print button under the file menu, the "save page as", preferences, zoom, history, bookmarks, in the tools menu I use the preferences for add-ons I've got. Occasional use include the "open file" in the file menu, view page source in the edit menu, and the about tab in the help menu. So maybe you don't use the menu bar but I do, just about every day. Removing it would really, really, really piss me off.
Gentlemen! You can't fight in here, this is the war room!
It doesn't help that the linked article is terrible. A whole pile of performance updates are being made in addition to the UI changes:
JagerMonkey
HTML5 Parser off main thread
64 bit support
Startup timeline optimizations
Reduced I/O operations on main thread
JS threads and GC
DOM Performance improvements
Layers for compositing, scrolling
+
Graphics compositing with Layers
Hardware acceleration using Direct3D
Multitouch support
Aero Peek integration
OSX integration
I'd suggest reading the actual presentation for more information:
http://beltzner.ca/mike/2010/05/10/firefox-4-fast-powerful-and-empowering/
My reasons for wanting to do so are:
1. Flash is a performance hog on platforms that aren't win32.
2. With H264 it will be easier to download youtube content for safekeeping.
3. H264 has hardware acceleration in a lot of portable devices.
Well, here it's much easier.
No problem is insoluble in all conceivable circumstances.
I had a friend using Chrome and one day he was at his networked printer and asked me to print out a webpage for him. I couldn't even figure out how to get Chrome to print. When I asked him, he admitted that he had memorized the hotkey combo for printing because he couldn't figure it out either. A default config where you can't even print without either reconfiguring the interface or hitting the right hotkey combo is a pretty piss-poor design, no matter how pretty it looks.
SJW: Someone who has run out of real oppression, and has to fake it.
Chrome's way of handling this is pretty clever. After the second alert box from a site, it gives you a "STFU" checkbox on the next ones.
You know, we at Mozilla have all these people working on this problem and amazingly enough, no-one thought of your idea of using the OS libraries yet! How dumb we suddenly all feel... Clearly, you have more brains than all of us put together.
http://weblogs.mozillazine.org/roc/archives/2009/06/directshow_and.html
Gerv
Surely they wouldn't need to physically decamp there, just re-incorporate themselves in that country (wherever you're talking about)?
If a company has a "nexus" on U.S. soil, it has to abide by U.S. patents.
http://openvideo.dailymotion.com/ as well
These people look deep within my soul and assign me a number based upon the order I joined. -Homer Simpson
More likely it's Adblock causing the problem. I've run a Firefox with Noscript only for the last 1.5 yr (Win7-64/RC>-Retail Win7-64) and have had no crashes due to any extensions. I have had crashes due to Plug-ins such as Flash/Quicktime/WMP but that's been endemic to the OS itself.
I personally gave up on Adblock since it was slowing FF down simply due to the number of blocks I had. After Entered most of them into the Hosts file, I was able to get rid of it and go discovered that NoScript configured to disable flash/silverlight and everything else worked as well if not better then the combo of Noscript/Ablock.
Mod me up/Mod me down: I wont frown as I've no crown
I don't know what you're talking about with https://./ I just browsed over to my banking site, and https:/// is in the address. It's even green, and the little padlock is on the right side.
My university has an open wireless system that uses a self-signed cert for a logon page. Chrome throws up a big warning. https:/// is in red and is crossed out, not to mention the big warning on the page itself.
I'd say that Chrome's alerts about https:/// are perfectly fine.
Version 5.0.375.38
Er, 25 years ago HTTP didn't exist. Let alone SSL.
Pretend that something especially witty is here. Thanks.