psychology dector

Electrolysis (e10s) [1] is a project to add a one-process-per-tab architecture (similar to Google Chrome’s) to Firefox. It was put on hold [2] in early 2012 and is now being resumed. Quoting a post on the mozilla.dev.platform Google Group: e10s is a priority for Mozilla’s engineering management and they are dedicating more help to make it happen. We’ve picked up some Firefox Metro engineers looking for new homes, new engineering manager, a Google Summer of Code student, and a gfx contractor. So expect to see more progress and more review requests. You can check out recent improvements in Firefox Nightly: You can test e10s in its own window, like Private Browsing, using the Nightly channel’s "File > New e10s Window" menu item. References: Electrolysis - MozillaWiki Firefox Electrolysis project put on hold

If there are a lot of tabs open in Google Chrome, it tends to become slow. Killing tabs by hand, via the Task Manager helps, but is tedious. The following bash script (by Sindre Sorhus ) lets you conveniently kill all open tabs from the shell (OS X only): #!/bin/bash ps ux | \ grep '[C]hrome Helper --type=renderer' | \ grep -v extension-process | \ tr -s ' ' | \ cut -d ' ' -f2 | \ xargs kill # [C] explained: http://www.commandlinefu.com/commands/view/402/exclude-grep-from-your-grepped-output-of-ps-alias-included-in-description That is, all tabs are still open, but they don’t display any content. You can reload any tab to get the content back. I’d love Chrome to have a mode where all background tabs are stopped completely and only the frontmost tab is active. Kind of like processes are managed on iOS.

This blog post explains how to search several websites (not just a single search engine!) from the omnibox (address bar) in Google Chrome. Managing search engines The default is simple: If you enter something in the omnibox and hit return, Chrome uses your input as a search query for Google. Via “Settings → Search”, you have the option of choosing a different search engine for this operation (my Chrome has the defaults Google, Yahoo, Bing). Next to the drop-down list with the defaults, there is the button “Manage search engines...”, which is where things get interesting. First there is a list with “default search engines” (the ones in the drop-down list), then there is a list with “other search engines”. You can add new search engines to the latter and then move them to the former by clicking the “Make default” button that appears when you hover over an appropriate item. A search engine entry has three fields: A name, a keyword and a URL. The keyword is an abbreviation for the URL, the...

With Blink , Google has created a permanent fork of the WebKit HTML engine. This blog post mentions a few interesting facts that provide context for that decision. How much did each company contribute to WebKit? There are several interesting diagrams and numbers in the article “ Reviewers and companies in the WebKit project ” (by Daniel Izquierdo Cortázar for Bitergia). It’s remarkable how much Google has recently contributed to WebKit. Obviously, not all contributions are created equal: some benefit everyone, others only the contributor. We don’t know what the ratio between the two kinds is for Apple, Google, etc. Why didn’t WebKit2 adopt Chrome’s multiprocess architecture? Here is an Apple employee’s explanation of why WebKit2 has a multiprocess architecture that is different from Chrome’s: Before we wrote a single line of what would become WebKit2 we directly asked Google folks if they would be willing to contribute their multiprocess support back to WebKit, so that we could bu...

People are posting Internet Explorer usage statistics on Twitter, tagged with #postyourIEstats (link works without being logged in). Summary: IE6 is mostly dead, as it should be. IE7 and IE8 still see considerable usage, but it’s on the decline. IE9 is currently most popular. As of 2012-11-15, it is the oldest Internet Explorer still supported by Google. IE10 usage is still low.