experimental

Possibly disable hardware acceleration.

Disable: Google Updater Google Toolbar FlashBlock if you have NoScript

I wish they'd concentrate on making a browser that can start scrolling before all the Javascript on the page has finished running.

That's weird, that's what happens to me in Chrome, not Firefox.

On the article - What Mozilla are doing first with Electrolysis is like WebKit2, rather than like Chrome which is almost-but-not-there-yet process per-domain which will come later. There was also some original research which went into Firefox 4 with per-compartment garbage collection.

They're also looking at a multi-threaded DOM in Rust.

In case anyone hasn't been keeping up with it, Flash was already sandboxed months ago, before Chrome implemented it (this is different from Out Of Process Plug-ins).

I recommend you disable the Google Updater plug-in which takes up memory and doesn't really do much of value considering it shouldn't be in Firefox in the first place. NoScript has a click-to-play for Flash built-in so if you're using Flashblock get rid of it because it conflicts with NoScript.

A reminder: you can use Alt to bring up the menu bar if you hide it.

If you're using TabMixPlus, there may be an add-on that gives you better performance.

You could help out coding Haiku OS (www.haiku-os.org) which is an x86 clean-room open source continuation of the once commercial BeOS being developed by a committed team. The emphasis is on native code, fast, lightweight and being super-responsive. You can have 10 videos playing at once (I don't know how much, but it's designed to never block a user's actions) and it doesn't bat an eye. It has binary compatibility with BeOS and new apps are being created for it all the time (avoiding the chicken-and-egg problem). There is a variety of them (some open sourced professional apps). It is not UNIX-like, but it has POSIX compatibility. Haiku has a journaling-file system which is fast and supports user-definable attributes (Be engineers brought a subset of it to Apple with them developing Spotlight and Microsoft had been working on a similar feature). Stack and Tile (haikuos.info/video/stack-and-tile.html) is a cool windows management feature unique because of tabs for window titles. The OS API is said to be the simplest and a joy to use.

Some of the languages available: C, C++, Python, Ruby, Perl, Lua, Haskell, Scheme, Squirrel, Yabasic, bash (comes with a bash shell), zsh

Some of the developer tools available: Paladin (its own IDE), Git, Hg (Mercurial), GNU Compiler Collection, Vim, QEMU, Bochs

Some of the technologies used: Multi-process WebKit browser, OpenGL, OpenAL, SDL and Qt libraries, Gutenprint and CUPS for printing, FreeBSD network drivers, Haiku Vector Icon Format

On the way: An ARM port, Clang with the already working LLVM, OpenJDK, Gallium3D, package management, more language bindings for the API

Included below is ways to contact, lessons and software sources:

freelists.org/list/haiku

freelists.org/list/haiku-development

haiku-inc.org

haiku-screencasts.blogspot.com

www.haiku-os.org/blog/darkwyrm

www.osnews.com/story/24945/A_Programmer_s_Introduction_to_the_Haiku_OS

haikuware.com (back online shortly)

bebits.com

There's also a wallpaper contest going on. I am not affiliated but I'd love to see more people get involved in this great OS! :)

That sounds like a really cool idea. :) Do you have plans to release it? This combined with Ruby on Arduino (http://news.ycombinator.com/item?id=2774170) could make a nice combination. Anyway good luck on your project.

App Tabs, In-content UI (like preferences in a tab), HTML/CSS/JS extension model and about:labs (proof on Aza Raskin's blog)

These are just a few things Google has copied from Mozilla. I don't go around complaining about all the thing Google has copied from Mozilla, but the record has to be set straight, Mozilla is not following Google, they are going there own way. They implemented sandboxed Flash first and compartments which Chrome is missing.

Funny that Google haven't updated the Google toolbar.

"It doesn't take a conscious effort to make software incompatible. All you have to do is not work too hard at fixing bugs—which, if you're a big company, you produce in copious quantities. The situation is analogous to the writing of "literary theorists." Most don't try to be obscure; they just don't make an effort to be clear. It wouldn't pay." - Paul Graham http://paulgraham.com/microsoft.html

Embrace, Extend, Extinguish.

There is no politics. Simply put, the developer who first wrote it worked at Mozilla, Firefox's tools aren't designed to replace Firebug and Mozilla coordinated releases with the Firebug team. So many negatives assumptions and unsupported claims when it comes to Firefox, if people wouldn't be so insular they would know what they are talking about.

TechCrunch isn't really a good indication of browser market share, the type of user is more likely to use Chrome (usually sticks with the defaults even if they use extensions).

Also I'm not sure early adopters is a good description, Firefox users are more likely to care about usability, security, privacy, extensions that aren't possible with Chrome or that Google considers not important or don't want it (something like NoScript or RefControl) and open source (which Chrome is not, sure Chromium is but the distinction is important because of real world implications and other reasons). These things do tend to be more important for some early adopters, I'm not sure I'd grant "technical proficiency" to mere "tech enthusiast".

It's also true that users have moved to Firefox from Chrome, being that for example depending on the metric Firefox is faster, but mostly the same speed. QEMU in javascript is a good example of a real world example where Firefox's javascript engine doubled Chrome's speed or thereabouts.

I believe you should use the http link to lessen the strain on the server.

This seems a little premature. It's the first build.

The problem with these grids or "tests" (like the Acid3) is that they are being used to prove a point - but they fall short of the real goal - showing what is agreed to be implemented and has been implemented (the Acid3 test written by Google's Ian Hickson hasn't removed the W3C non-recommended SVG fonts).

- The W3C chose IndexedDB over Web SQL so it's no wonder IE10 doesn't support it.

- Mozilla has been working on WebGL for years now (piece by piece?), and Chrome just got it very recently (is it complete?).

- Web Sockets, wasn't that disabled for security reasons until a fix is found?

- Chrome is considered the pinnacle in this blog post and yet there's no mention of ECMAScript 5.

Chrome's development started in secret and took some Mozilla engineers in the process and even though Chrome is mostly developed out in the open, Crankshaft (new V8 engine) and WebM were not. I'm not going to say IE hasn't been marketed a little bit unfairly, but I think a little transparency should be welcomed no matter who it is. Remember all businesses present incorrect facts to benefit (I'm merely stating, not excusing), an example being Chrome never actually downloading the web page in the promotional video a while back, it rendered from a local file.

You're welcome to correct me if I'm wrong.

"* Use triggers and condition yourself to concentrate on the triggers. For me it's original-flavor Trident gum + rainymood.com + somafm.com/play/groovesalad."

Can you elaborate on this/reword?

I'm on the fence with them supporting XP. One comparison to take into account is Safari's releases have dropped support for an older OS, much less than 10 years, they did change processor architecture though and have less business users to support. Also Microsoft offer free support.

I have no idea.

Cool thanks for the information.

Can somebody explain how this doesn't contribute to the discussion? I was trying not to tell nikcub something they may already know, and trying to be helpful for anyone else while not making assumptions on the knowledge of anyone else.

They remove the moz (and possibly change something else) from the name when a vendor-neutral syntax has been reached. I think we have to wait a while for the final syntax.

"Nginx uses an asynchronous event-driven approach to handling requests which provides more predictable performance under load, in contrast to the Apache HTTP server model that uses a threaded or process-oriented approach to handling requests."

Does this mean if a crash occurs, the whole process of nginx will crash? Whereas Apache's processes can be restarted?

/Genuinely curious

Linus Torvalds said in 2001 he didn't use a bug tracker for the Linux kernel so I'm not sure if I should be worried.

Apache, nginx and Cherokee also work on Haiku as well as a bunch of other native ones (e.g. PoorMan http://en.wikipedia.org/wiki/PoorMan and RobinHood). nginx fits well with it because Haiku performs well under heavy load for responsiveness, is lightweight and fast.

They collect a lot of personal information and considering Marc Andreessen is on the board of Facebook I won't trust a browser that has questionable practises like Facebook. Regardless there are addons which do what RockMelt does. The UI also is off, even if someone doesn't realise it. It is behind in updates so not good for security reasons.

I don't use OS X, but I thought I'd share a few bits of information. Also this page demonstrates why native local software is so great - no redundancy (exposing a dictionary to all apps), low memory footprint etc.

- In 10.6 Snow Leopard, hold Space to zoom in on a window in Exposé.

- Not a hint exactly, but there exists at least one unnecessary dissatisfaction people have of Finder. In real life, you cut text and paste it in a scrapbook, but you don't cut an object like a folder with scissors in order to move it. You usually use a hand or two. Therefore the inability to "move" an object using "cut" (Cmd+X) is the correct behavior. Secondly it prevents you from accidentally pasting a file elsewhere, then needing to remember if you meant to do that, or undo. Adding visibility in some way is not enough, and you can still move by dragging the object to the desktop or wherever else.

Note: Edited for spacing.

I know you didn't claim Apple invented it, but I thought it would be informative to say Apple have added their own ideas but the main idea comes from BeOS, a once commercially viable operating system. These days it lives on in an open source recreation that has improved on BeOS, called Haiku. It uses a 64-bit journaling file system which has been improved now called HaikuFS that can hold 80,000 petabytes, caches so is fast and has user-definable attributes, like for contacts, music or anything you can think of really which can help you find things fast. There's a reimplementation of Dashboard called Corkboard written by a fan so it goes both ways - good ideas are used elsewhere. :)

"Windows goes even further: you can click through a link or button on a non-focused window."

This is a interaction design mistake. On Windows, if you click inside an unfocused window you can perform an action otherwise unintended, Mac OS X's way and Haiku's (www.haiku-os.org) is correct. Interestingly Firefox follows the Mac way, but on at least Windows Chrome does not, and if you happen to unintentionally select the close tab button, you're tab close and if you're in Incognito mode, you lose that tab because there is no history.

I trust you know what you are doing. I'd like to warn others to be careful of what is removed, especially if you didn't put it there. The price is stability.

In the sense of using the platforms' libraries and APIs, then Chrome is not native (especially some of the UI as Javascript is not native in any sense) because it comes bundled with its own runtime as well as the WebKit runtime. But in terms of systems languages they are using yes that is native.

Or NativeClient. Ironically it contains several runtimes although "Native" in this case means non-web programming languages for the client-side. Remember the HTML component is a runtime.