Browsersphere

To borrow from Pink Floyd, is there anybody out there?

Ironically enough, Browsersphere has been neglecting the browsersphere a little like Microsoft neglected Internet Explorer earlier this decade.  After all, my last post was way back in June.  However, unlike Microsoft, it isn’t the competition that has jolted this site back to life.  On the contrary, sites like Avencius and Twitter accounts like @AltBrowser have actually made me feel a little bit better about the whole ordeal, knowing that at least someone is out there covering the browsersphere in my absence.  Truth is, the site went dark out of pure laziness on my part.  Well, that and the fact that I’ve been pretty consumed by another project.  Nevertheless, I’m back, and after catching up a bit on what’s been going on, my first order of business is to share a little bit about what’s been tweeted in the browsersphere lately.  So let’s get to it.

• Looks like @ryan45419 is working on his own web browser named iSurfWeb.
• @humancell points out that Firefox and Safari accounted for 79% of all web vulnerabilities in the first half of this year.
• @ByteEye appears to be working on its own web browser as well.
• @erichthewebguy is happy to be seeing Firefox used more and more on TV these days.
• As someone who appears to have given up on Firefox for Chrome on the Mac, @lee_cummings may have coined a new term: “nozilla.”
• @UKTJPR wonders if anyone is willing to give up their web browser for a week.
• @DevJonny points out SRWare Iron, a browser created with the Chromium source code that apparently doesn’t have all the privacy concerns of Chrome.
• @BemusedWolf, who has come up with some colorful names for Firefox and Internet Explorer, might be interested in SRWare Iron.
• @SuperDuperCam had some colorful words to share about Firefox as well.
• @BrowserNews, the creator of the Dolphin3D browser, is touting it as “a better web browser.”
• @mrtech points us to a blog entry about what the Firefox team is doing about crashes and startup time.
• @usingpond wonders if Blackbird, which sells itself as an African American browser, is for real.
• @msacks makes reference to the Lobo browser, which is all-Java and uses a rendering engine called Cobra.
• @waynehastings and @deanq appear to be pleased with Chrome for Mac OS X, with the later giving a parting shot to both Firefox and Safari.
• @chrispy2004 appears to be displeased, however, claiming that Chrome for Mac OS X is the slowest browser he’s used in a long time.
• @GameFreak4321 doesn’t seem all that pleased either.
• @JasonTselentis thanks the “Facebook browser” for finally taking away Internet Explorer’s market share.
• @KileyG wonders what the threshold is for the number of open tabs before someone becomes unproductive.
• @muhanov discovers and shares the fact that the Android web browser doesn’t support FTP.
• @ganetsky wonders how it’s possible that no one has created a web browser named “Bowser.”  Good question!  Though to be fair, some people have referred to IE as the “Bowser” browser.
• @Andrew_James claims to be in “web browser heaven.”  I wonder if Netscape’s there.
• Both @jamienguyenle and @jinkhet refer to Chrome using sexual terms.
• @nicnab asserts that Firefox’s remembering of per-site zoom levels is enough to keep him hooked on said browser.
• @ConduitYourSite wonders what the best Twitter lists for browsers and web-related tools are.
• As I often have, @alex_crawshaw finds it ironic that you need to use a web browser in order to download an alternative one.
• @propstm wonders if IE6 users even realize what they’re missing out on, using such an out-of-date web browser.
• @derickthemacguy says Google Chrome looks like “a Fisher Price version of a web browser.”
• @souravghosh says that Mosaic “is considered the first browser to make the Internet easily accessible to non-techies.”
• @C_Hernandez_ heard that Camino is the fastest browser for Macs and apparently is going to check it out.
• @omegatron laments, as do many I’m sure, the fact that his mom doesn’t know the difference between a web browser and a web page.
• @Allyssen points us to a split-screen browser for the iPhone called iNetDual.
• @ericylai recommends the Bolt browser, which also happens to support a split-screen mode (check out the demo), for those tired of the default Blackberry browser.
• @IHtherapies finds KidZui, a web browser targeted at kids, very cool.
• Even if it’s “a bit slow,” Firefox is still @flyfiddlesticks‘ favorite browser.
• @abhishek tweeted about the Facebooker browser, which is currently available as a release candidate.
• @juandelpozo makes reference to Infinity Web Browser, a web browser for Android.
• @va3stl gave Midori a try.
• @wordtree likes the idea of trying a text-based web browser like Lynx.
• @tr4st recommends Lunascape, the “world’s first and only triple engine browser,” to web developers.
• @sphereinabox wants to know what mobile web browsers, other than Safari, support offline storage.  If geek.com is to believed, it looks like Fennec does, too.
• And finally, @rodhilton loves that Ubuntu lets him use a web browser while the operating system is still installing.

That’s it for Twitter Watch #3.  Believe it or not, Twitter Watch #2 was so long ago that I was still using Summize to search for tweets.

Before I end this post, since we’re on the subject of Twitter, I should mention that Browsersphere is now on Twitter as well.  Just follow @Browsersphere for real-time updates, links to new site content, etc.

Tags: Android, Avencius, Blackberry, Blackbird, Bolt, Chrome, Chromium, Cobra, Dolphin3D, Facebook, Facebooker, Fennec, Firefox, Google Chrome, iNetDual, Infinity, Internet Explorer, iPhone, iSurfWeb, KidZui, Lobo, Lunascape, Lynx, Mac, Microsoft, Midori, Mosaic, Netscape, Performance, Privacy, Rendering, Rendering Engines, Safari, Split-screen, SRWare Iron, Summize, Tabs, TV, Twitter, Ubuntu, Vul, Vulnerabilities

I always get a kick out of reading the Maxthon Blog because some of the claims made about either Maxthon or its competitor web browsers are so outlandish.  This time around, a press release was posted claiming the following:

Maxthon’s engineers redesigned the browser’s framework so that each tab associated with a Web site works independent of each other. With that new architecture, if a tab becomes unresponsive for any reason, the other tabs and the browser are unaffected. The computer user can continue to browse normally and can refresh, reopen, or close the tab that is creating problems.

“Basically, our technology separates the tab and the browser,” said Jeff Chen, CEO of Maxthon. “That [sic] why the tab’s problem will not affect the browser’s performance, and so the browser can be a better environment to run Web application in tabs.

“As far as I know, no other major browser has such a feature,” Chen said.

I can understand making a claim like that last one in a press release, since you’re trying to set yourself apart from the competition.  Plus, Jeff Chen said “as far as I know,” which at least keeps the claim from being matter-of-fact.  However, I think it’s pretty inexcusable to make such matter-of-fact claims directly on your product’s blog when common knowledge suggests the opposite.

Before posting the aforelinked press release, the following was posted to the Maxthon Blog:

“…other browsers without [Maxthon's new feature] The Isolator – which would be, let’s see…. All of them. – can’t protect their tabs the way Max does.”

When an astute (or at least, non-delusional) commenter mentioned Google Chrome as a browser already supporting this feature, MaxthonGuy, the persona behind the madness that is Maxthon Blog, had this to say:

“Chrome does have a feature, Crash Control, that has a purpose similar to that of The Isolator. But the two technologies work differently, and Crash Control can’t save you from the Flash-inspired crashes that The Isolator blocks.”

So I guess if a feature has been implemented differently, then it doesn’t actually exist in any other browser.  Using that logic, I suppose Internet Explorer was the first web browser to support tabbed browsing.  But don’t worry, Firefox and Safari fans, your browsers were, too – despite what Opera or NetCaptor might have to say about it!

I just had to get this absurdity out of the way before I post a more in-depth look at multi-process architectures in web browsers.

Tags: Architecture, Chrome, Crash Control, Features, History, Maxthon, Maxthon Blog, MaxthonGuy, Multi-process, NetCaptor, Tabs, The Isolator