Firefox 4 Will Push Edges of Browser Definition

Chris Blanc writes "Mozilla Lab's push is to blur the edges of the browser, to make it both more tightly integrated with the computer it's running on, and also more hooked into Web services. So extended, the browser becomes an even more powerful and pervasive platform for all kinds of applications. 'Beard wants the new online/offline, browser/service to be more intelligent on behalf of its users. Early examples of this intelligence include the "awesome bar," which is what Mozilla calls the new smart address bar in Firefox 3. It offers users smart URL suggestions as they type based on Web searches and their prior Web browsing history. He's looking to extend on this with a "linguistic user interface" that lets users type plain English commands into the browser bar. Beard pointed me towards Quicksilver and Enso as products he's cribbing from.'"

"Blur the edges of the browser"

Cleartype fonts will clear that right up.

I hope they implement this as plugins

Because I would like my browser to interact with my machine as little as possible && and I am not at all into social networking.

Re:I hope they implement this as plugins

Ditto. Integration with the OS is the last thing I want. That's exactly what gets IE into so much trouble.

Re:I hope they implement this as plugins

The summary does sound quite bad, but if you read the article, it sounds actually much better.

"At the moment, these are two separate projects Mozilla is running to push out the edges of the browser: Prism and Weave."

"Prism
Prism is Mozilla's shot at busting apps out of the browser. Part of the Prism project is making the browsing core available to apps developers so they can build products like Zimbra Desktop (review) that are essentially Web apps, but that don't look like it. "

"Weave
Weave extends the browser in the other direction: Not toward the desktop, but instead into the Internet. Mozilla wants an individual's browsing experience to stay with them no matter what machine they are on."

Re:I hope they implement this as plugins

"Weave extends the browser in the other direction: Not toward the desktop, but instead into the Internet. Mozilla wants an individual's browsing experience to stay with them no matter what machine they are on."

Screw that! My employer doesn't need to know I read slashfiction or what kind of porn I browse at home. Now, the porn I browse at work, that's different!

Re:I hope they implement this as plugins

You're not the "average" user. You know how I know?
a) you're on slashdot
b) you used && in your comment, perhaps by mistake
c) "I am not at all into social networking."

On the plus side you definitely belong here!

is it just me?

I really dont want mozilla suggesting anything in my address bar

Re:is it just me?

Usually these features can be disabled quite easily from the about:config.

Re:is it just me?

Oh yea it is easy type about:config (like that is a common way to change preferences in application of the 21 centory) Then hunt down for some feature name that is probable more reference to a Varable Name and less of what it actually does and then figure out what the value should be... A piece of Cake, I have no Idea why people say Open Source Software is hard to use.

Re:is it just me?

Oh, yeah, sure. I'm going to go and... read, whatchamacallit .. *instructions about how to do the thing that I want to do.

Not likely. Firefox doesn't behave how I like by default because it's, um, open source software I guess.

-PseudoJello

Re:is it just me?

gp is right...You shouldn't have to look up instructions on how to change a basic setting. It irritates the hell out of me when FF does crap like this. You can add an "Advanced Configuration Options" button that will provide this sort of functionality without forcing the user to remember a piece of command syntax.

Active Desktop?

Didn't we try this 10 years ago, and it sucked? I want more separation between my browser and OS, not less.

This is all wrong!!!

Surely Firefox is going in the wrong direction! IMHO, blurring the edges of the browser should be the job of the Window Manager.

I'll get my coat..

Beard...

From his picture in TFA, Chris Beard, VP of Labs for Mozilla, has no beard, despite his high-up position within the open source movement.

Does open source play by ZZ-top rules now?

SeaMonkey

Odd that Firefox was spun off from Mozilla because Mozilla was too bloated and heavy, and now we're back around where Firefox is going to be (is?) the bloated one -- and the new Mozilla, SeaMonkey, is actually light and simple compared to Firefox.

So I've switched to SeaMonkey. So long, Firefox. I've used you since the early days when you were known as Phoenix. I shan't be using you any more, given the direction you're heading.
 

Penultimate stage of the browser life cycle

Lemme break it down for you:

• Gestation: Initial release of totally awesome browser is developed.
• Infancy: A few people start using the browser and see how totally awesome it is. Word spreads.
• Childhood: User base grows explosively. People start complaining that totally awesome browser doesn't have feature X.
• Adolescence: More and more features get tacked on to browser. Side effects of bloat become noticable. Users start to ask for a lite version.
• Maturity: Browser starts performing tasks entirely unrelated to web browsing. Browser becomes hefty and clumsy (FireFox is somewhere in this stage)
• Entrenchment: Browser has enough of a user base to establish its own nonstandard rules for web content, essentially branching the web. Alienation and hostility ensue.
• Death:: User base dwindles becuase the browser doesn't play nice with the rest of the world anymore.

Those of us who think the new vision is a bad thing aren't necessarily curmudgeons who don't want anything to change. We know a lot of very specific things about how we want to interact with a computer, and we don't want the same organization that produces our web browser of choice to dictate the rest of that interaction. It doesn't really matter whether they get it right or not.

Firefox development should fork

The whole original premise of Firefox was that it was lightweight, fast, and actually worked. Because of this, I think they should keep the firefox brand as-is... make it smaller, faster and more lightweight, but no reason to go fill it up with these features.

I think they should fork development into a new product. Basically going in the direction that they are discussing with version 4. These features look like they could be a great idea. A lot of really progressive and great things look stupid on paper, but once you see them and use them, they can surprise you, at times.

Personally, I think they need to make firefox even moreminimalistic. Something that will have the absolute smallest memory footprint after being launched and be snappy and responsive. Modern websites have a TON of code ([x]html/css/javascript) and graphics so it's understandable that the footprint would grow when you have 30 tabs open; but on slower hardware such as the eeepc or older laptops, I'd like the browser to not impact the system quite as much in the memory department.

It's EMACS all over again.

Firefox will be a great OS. The only thing it lacks is a decent browser.

What we need is the browser equivalent of vi [the-little...d-girl.org]. And it actually exists. How wierd is that?

Weave is a good idea, but dangerous

I like the idea of Weave. I log into 3 different Firefox browsers each day. None have the same bookmarks or history. My last attempt at synchronizing them over the internet resulted in Google deleting the vast majority of my bookmarks. I wasn't about to try that again. That said, I really don't want my cookies, passwords or favorites ending up on a desktop in Thailand unauthorized, for any reason whatsoever.

I also like Prism. I know people like to complain about the bloat of Firefox. It's not like FF has been getting any slower. In fact, through the last 3 beta versions of FF3, it's been getting faster, and the memory usage has actually gone down. What's the big deal?

The primary roadblock at this point is network access. Sometimes I don't have network access on my MacBook, depending where I am (Alaska comes to mind). The ability to continue working on web-based applications, absent of a network, is tantalizing, to say the least. Imagine writing a whole bunch of emails on Gmail, and synchronizing once you get network access. (Like all the stability of Outlook (ha!) and all the continuous service updates of Gmail, rolled into one.)

What is it with everyone and HTTP / XML?

It seems that the world is moving back to a thin client setup; but instead of a client having a network connection to a server, its communication is via several abstraction and generic transport layers (HTTP / AJAX); instead of using a relevant protocol, everything is translated into XML-based RPC; and instead of using a useful widget set, everyone is bastardising HTML (eg, the hundreds of javascript-based calendar widgets; when all GUI toolkits I know of have one built in).

Is it just me, or is this hideously inefficient, ugly, and Wrong(tm)?

Didn't Microsoft already try this?

integrated with the computer it's running on, and also more hooked into Web services

So Firefox 4 is going to have Active X?

Re:Sounds Scarry.

At this point, I'd take a browser with half the awesome and none of the bloat.

Maybe FireFox needs a "lite" version.

Re:AwesomeBar

I vote we tag this awesome article "AWESOMEBAR"

Until now, I just thought the AwesomeBar was what Chuck Norris ate for breakfast!

Re:Some recommended commands

Score: 5, Confused

Re:Some recommended commands

There are no nutrients in [rock]. Dragon kills you. You are dead. [Restart?]