81–90 of 164 posts
Earlier quoted context omitted.
One major (okay maybe not that major but an important factor in my decision) issue for me with Australis is the separate boxes for URLs and search. Every other browser merged them and I don't know of any reason to keep them separate - is there one?
This is to protect user privacy as explained by a Mozilla dev: https://news.ycombinator.com/item?id=6756582 Otherwise every keystroke you made would be sent to Google.
Eagerly waiting to ditch Chrome & its forced notifications. Perhaps with Australis (Firefox 29), the UI would be at par. Edit : Chrome feels subtle, lighter & perceptually faster (specifically : tabs, scrollbars). Although after updating Firefox today, I can notice that there's improvement in Firefox.
One major (okay maybe not that major but an important factor in my decision) issue for me with Australis is the separate boxes for URLs and search. Every other browser merged them and I don't know of any reason to keep them separate - is there one?
Why Firefox removes spdy/2 support? They don't want to support spdy/2 servers? Why? PS: I'm not expert on servers :)
Earlier quoted context omitted.
One major (okay maybe not that major but an important factor in my decision) issue for me with Australis is the separate boxes for URLs and search. Every other browser merged them and I don't know of any reason to keep them separate - is there one?
This is to protect user privacy as explained by a Mozilla dev: https://news.ycombinator.com/item?id=6756582 Otherwise every keystroke you made would be sent to Google.
Earlier quoted context omitted.
In case you're curious: http://arewefastyet.com/ https://areweslimyet.com/
Any idea why the "slim" numbers are moving steadily in the wrong direction?
More generally, AWSY is useful for identifying some regressions, but it's one specific, unrealistic workload. You can't use it to judge Firefox's overall memory consumption.
For example, looking at AWSY you'd think Firefox 13 had the best memory consumption. But I guarantee you that Firefox 28 has better memory consumption. In particular, Firefox 28 has fewer bad cases where memory consumption spirals out of control, and those are the cases that really hurt performance and stability. Using 10 or 20% more memory at start-up, for example, isn't a big deal in comparison.
Earlier quoted context omitted.
Same there (try 10000 sites, click "Benchmark"): http://www.raymondhill.net/voronoi/rhill-voronoi-demo1.html The difference has narrowed though, FF used to be much, much slower than chromium.
I can definitely see a difference on this one, yes, about 30%. A question. Does "rendering not included" mean not including painting times, or not including the canvas API call times either? My profiler is showing a bunch of fill(), rect(), stroke(), moveTo() calls dominating the wall-clock time, but I'm not sure whether those are what's being measured here or not.
Earlier quoted context omitted.
I don't think people that are running Nginx with spdy are doing so with the stable version. I started using spdy back when it was a patch you had to manually apply, before compiling Nginx.
Count me as one of those people who doesn't like to have to work around backwards compatibility breaks when installing security patches on production servers. :-) (edit: clarified wording)
Anyway, doesn't spdy/2 have a huge security flaw in certificate management? I don't remember it well. If that's the case, it's good that they droped it.