If you are just looking at what's best to add to the browser itself, just look at the plugin market to see what's in wide use.
Unfortunately, reputations stick.
Google Chrome 25.0.1364.97
Private Shared Total
3,950,040k 12,805k 3,962,845k
4,728,936 k 937,320 k
We are also looking at existing extensions.
There are a lot of cool plugins, but new users don't always know what to get. But if if it was easy to fork Firefox and add some plugins and redistribute it in whatever forums or communities they prefer, that would be cool.
So there may end up being a Firefox for reddit, for image processing, for web design, for web dev, etc.
This has been considered and rejected as inferior to the current approach. The Android browser used this and it was rewritten to get rid of it.
Let's focus on doing things that improve the user experience rather than blindly copying features from other browsers without considering if they make sense.
Moreover, it has absolutely nothing to do with the question asked.
Didn't they ditch Electrolysis because of issues with many nsplugins? I am not aware of other reasons it was shitcanned.
Why not? I'd say 30 processes is a lot better than 1 process.
If I open two new tabs simultaneously, the whole browser can freeze for a bit.
But this is an end user experience, rather than a web dev experience.
How would you like to see the API for plugins/add-ons improved?
I don't think you need to add a more things for developers. The tools already present are good enough, I saw someone suggesting a built-in sFTP. That's just too much.
Tree tabs are the more conventional way of understanding lots of items (and tabs are hierarchical -- parent tabs are where you opened the current tab from).
Just curious because I rarely find FF creeping up towards a gig and RAM is so ridiculously cheap most of what I have just sits around doing nothing. (Edit: shouldn't have said nothing, but I'm not maxing out even with 4GB unless I am working in Photoshop/Illustrator)
I have this thread, HN home, espn, and techcrunch open in both FF and Chrome right now
a 30 meg difference is really _not_ a big deal.
Anywho I find myself using chrome for dev while FF is for browsing. The AngularJS and Speed Tracer addons are nice for Chrome. I browse with FF because they support tags with bookmarks, which I'm addicted to