Live data from Hacker News

Lightspeed – A Browser Experiment

blog.mozilla.org

81–90 of 184 posts

Re: Lightspeed – A Browser Experiment

#81

I was surprised to see this rise on the front page. Am I the only one who didn't get excited at all by this? When I see a post titled "a browser experiment" from mozilla.org I tend to think I'm going to get more than some wireframes and talk about "busybees". It will be an experiment once some (any) of it has been built. In any case from what I did see in the video I would say: 1) Bookmarks are broken, but removing t…

To nitpick, in the suggested experiment - bookmarks aren't removed. Although I guess you could compare the solution to "completely remove" them since they work a lot different, I guess you wouldn't "Love"-click something to read later or go back to, but their main site (Like NYT.com, BigBank.com etc). They'd be integrated into the ""amazebar"", but they'd still be there.

As has been mentioned in other threads to this discussions, tabs aren't all that important for the thought of userbase. They are people who sometimes uses tabs or never uses tabs.

Also, I, as a "Wizard/Enthusiast" user - got somewhat excited by the suggested experiment and think it kind of make sense. I wouldn't prefer using this myself, but I can certainly see benefits to a significant user share.

Re: Lightspeed – A Browser Experiment

#82
post #43
post #33

The design choices really look interesting. But shouldn't Mozilla focus more on eliminating the ever persistent memory leak bug that has plagued it since forever? I can't even use Firefox on a netbook. I end up installing Midori.

Mozilla is comprised of a lot of different people working on a lot of different things. There are people focusing on various memory and speed issues, but they can't (and shouldn't) allocate all their resources to focusing on just a few issues.

yarou obviously didn't say that they should focus everyone only on reducing Firefox's memory usage and performance problems. I'm not sure how you mistakenly got that impression, because that's clearly not what that comments suggests.

The main issue here is that we've been hearing that these problems will be fixed, or even that they supposedly have been fixed, yet they're still present years later.

Whatever work is being done clearly isn't having much of an impact. Users are still reporting problems with Firefox's performance and memory usage, even if those within the Mozilla community wish to deny these problems exist, or claim that they'll be fixed "soon".

Users can only take so much of this. With Chrome and Firefox offering UIs that are pretty much identical these days, but Chrome offering significantly better performance and significantly lower memory usage, any reasonable user will obviously consider switching from Firefox to Chrome. Many have done so already, and many will continue to do so as time goes on.

Re: Lightspeed – A Browser Experiment

#83
Hi, I'm one of the people who worked on this and I wanted to provide a little background and a few clarifications.

Lightspeed is currently not a product. It's a collection of sketches and thoughts. It is also NOT the next version of Firefox. While some ideas might find their way into mainline Firefox at some point, many of the assumptions on which Lightspeed is based are the exact opposites of Firefox core values (e.g. no settings or customization in Lightspeed).

More than anything else, Lightspeed helps us think outside the box that Firefox is. It's a place where we can dare to explore more radical thoughts like not having any settings or or even menus. Having constraints like these stimulates creativity much like, for example, the character limit on tweets forces you to make your message more concise.

Ideas are worthless when they just exist in your head. Sketching out Lightspeed has helped us to make make lots of ideas more tangible, so they can be evaluated.

That being said, just reading through this thread has sparked some interesting new thoughts – we'll keep experimenting :)

Re: Lightspeed – A Browser Experiment

#84
post #71
post #25

Earlier quoted context omitted.

I agree with not defaulting to saving downloads in the "downloads" folder. Many people don't really know how to use their file manager. (For years, my mom would open Microsoft Word and organize files there.) Why not default to saving downloads on the Desktop? Where did that file get saved? Oh, there it is!

What happened to just asking the user where they want to save it? To download a file I now have to download it, then open Finder, navigate to Downloads and copy the file, navigate to the folder I want to place the download, paste the file. Then navigate back to the folder and delete the file from Downloads .. because Macs don't give you a Cut option.

You make a very good point.

That sensible and effective approach has become yet another victim of the failed quest to "improve the user experience" by throwing away or changing stuff that was working perfectly fine before. The new approach is almost always far worse than whatever minor flaws might have existed with the earlier approach.

And allowing the old, working approach to be toggled back on through some preferences dialog, through about:config or through some extension doesn't justify the bad change. If anything, it's actually somewhat offensive, because it now requires users to engage in yet more fixing of things that just shouldn't be broken to begin with.

When I start using a fresh installation of Firefox, I have to spend at least a good 10 minutes installing various extensions and reconfiguring it just to get a minimally usable experience out of it. That's not acceptable, and it's not justifiable.

Re: Lightspeed – A Browser Experiment

#85
post #33

The design choices really look interesting. But shouldn't Mozilla focus more on eliminating the ever persistent memory leak bug that has plagued it since forever? I can't even use Firefox on a netbook. I end up installing Midori.

All complex programs written in languages like C++ have memory leaks of some kind or another. If you really want to get rid of memory leaks, having Servo mature, and hopefully building a browser out of it would be a good start.

Re: Lightspeed – A Browser Experiment

#86
post #62

> Auto-updates are always on I really hope this isn't going to become a standard thing. There are still plenty of people like me who are stuck with something like satellite internet, which forces us to micromanage our data usage. I can't afford to just have things auto-updating whenever they want.

If you're connected to the Internet you have to update your browser all the time just to stay minimally secure.

Are you suggesting that the updates themselves never introduce new security flaws?

Re: Lightspeed – A Browser Experiment

#87
post #71
post #25

Earlier quoted context omitted.

I agree with not defaulting to saving downloads in the "downloads" folder. Many people don't really know how to use their file manager. (For years, my mom would open Microsoft Word and organize files there.) Why not default to saving downloads on the Desktop? Where did that file get saved? Oh, there it is!

What happened to just asking the user where they want to save it? To download a file I now have to download it, then open Finder, navigate to Downloads and copy the file, navigate to the folder I want to place the download, paste the file. Then navigate back to the folder and delete the file from Downloads .. because Macs don't give you a Cut option.

There's the move command though. Cmd+Opt+v will move a file (cut it) rather than copy it.

Re: Lightspeed – A Browser Experiment

#88
post #25
post #9

At first I thought "oh no, another distraction for Mozilla", but then I sat through the presentation and thought there was some really cool ideas (amazebar!). In fact, I think it can be simplified and paired down even more. Even better, some of the assumptions here even make the software portable (as in doesn't really need to be installed and could just run off a usb drive/out of my dropbox). Automatically being in a…

I agree with not defaulting to saving downloads in the "downloads" folder. Many people don't really know how to use their file manager. (For years, my mom would open Microsoft Word and organize files there.) Why not default to saving downloads on the Desktop? Where did that file get saved? Oh, there it is!

Not understanding the file manager is exactly why not asking for a location is a good idea. You just download it, and when you want to find it later, you just search, and there it is.

Re: Lightspeed – A Browser Experiment

#89
This is a great concept. Getting rid of settings, add-ons and plugins for people that "just want their browser to work" is a good thing, especially when this is paired with good privacy defaults.

However, I see the auto suggestion features of the Awesome Bar at odds with the goal of protecting the user's privacy. This essentially means that all search terms that you enter into the search field will be sent to to all web services that were integrated by Mozilla, including Google, Yahoo, Microsoft, Bing, Wikipedia, Amazon etc.

Just imagine using the Awesome Bar to search your inbox for a (business) "proposal". Then, a little while later, your partner uses your laptop for online shopping and Amazon helpfully reminds him or her that you recently searched for "proposal". Depending on your relationship status, this could become very interesting...

Re: Lightspeed – A Browser Experiment

#90
post #87
post #71

Earlier quoted context omitted.

What happened to just asking the user where they want to save it? To download a file I now have to download it, then open Finder, navigate to Downloads and copy the file, navigate to the folder I want to place the download, paste the file. Then navigate back to the folder and delete the file from Downloads .. because Macs don't give you a Cut option.

There's the move command though. Cmd+Opt+v will move a file (cut it) rather than copy it.

Ok. That's life changing!
Post reply on HN