Live data from Hacker News

Firefox 28 Release Notes

mozilla.org

61–70 of 164 posts

Re: Firefox 28 Release Notes

#61
post #8
post #6

Well, there's also stuff that you can't see in the "release notes". I found that Firefox 27 had huge speed improvements in canvas 2D compared to Firefox 26, at least in Linux without hardware accelerated canvas. I couldn't find anything related to that in 27's release notes, sooo (still happy though!).

In case you're curious: http://arewefastyet.com/ https://areweslimyet.com/

Anyone have a good breakdown of the differences in these benchmarks? i.e. Why does Chrome dramatically lead the(ir) Octane benchmark?

Re: Firefox 28 Release Notes

#62
post #49

Interesting to see that now the current stable versions of Chrome and Firefox have dropped spdy/2, which is the only version of spdy supported by the current stable version of nginx. And nginx is the server used by more than 90% of hosts supporting spdy[1]. I presume this means it is mostly a Google/Twitter/Cloudflare thing for now since they seem to all be running spdy/3.1 in production. [1] http://w3techs.com/techn…

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.

Re: Firefox 28 Release Notes

#63
post #49

Interesting to see that now the current stable versions of Chrome and Firefox have dropped spdy/2, which is the only version of spdy supported by the current stable version of nginx. And nginx is the server used by more than 90% of hosts supporting spdy[1]. I presume this means it is mostly a Google/Twitter/Cloudflare thing for now since they seem to all be running spdy/3.1 in production. [1] http://w3techs.com/techn…

Chrome has also dropped support for SPDY/2 https://en.wikipedia.org/wiki/SPDY#Protocol_versions

Re: Firefox 28 Release Notes

#64
post #5

Firefox 29 hits the beta, that means MacOs users get tabs in title line, finally!

That makes me wiling to try Firefox again, since amongst the Safari/Chrome/Firefox it was the browser that consumed most vertical space, which is an issue on mobile (less than 15") laptops - at least for me.

Re: Firefox 28 Release Notes

#65
post #20

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?

There is, yes.

You have three somewhat simple options for the search/url thing:

1) Have a single box, do not offer search suggestions. 2) Have a single box, offer search suggestions for the stuff users type in it. 3) Have separate boxes; offer search suggestions for the stuff typed in the search box but not the stuff typed in the url box.

#2 involves sending everything the user types in the url bar to the search suggestion provider to check for suggestions

Firefox does #3, because #2 is not considered acceptable from a user privacy perspective.

There are probably more complicated options here like only offering search suggestions if the string typed so far doesn't look like a URL or something that might protect user privacy better than a straight up #2. But it gets easy to screw it up and leak private user data to the search provider....

Re: Firefox 28 Release Notes

#66
post #49

Interesting to see that now the current stable versions of Chrome and Firefox have dropped spdy/2, which is the only version of spdy supported by the current stable version of nginx. And nginx is the server used by more than 90% of hosts supporting spdy[1]. I presume this means it is mostly a Google/Twitter/Cloudflare thing for now since they seem to all be running spdy/3.1 in production. [1] http://w3techs.com/techn…

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)

Re: Firefox 28 Release Notes

#67
post #20

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.

What problems do you have with the current firefox UI?

Chrome feels lighter & perceptually faster (mostly psychological) because of a flatter UI (specifically the tabs, scrollbars). Although after updating Firefox today, I can notice that there's improvement in it.

Re: Firefox 28 Release Notes

#68
post #20

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.

I switched from Chrome to Fx this week. So far the only annoyance really is that flash elements on a webpage can takeover keyboard focus. I'm used to KB navigation and opening a youtube tab can really mess with your flow.

Re: Firefox 28 Release Notes

#69
post #67

Earlier quoted context omitted.

What problems do you have with the current firefox UI?

Chrome feels lighter & perceptually faster (mostly psychological) because of a flatter UI (specifically the tabs, scrollbars). Although after updating Firefox today, I can notice that there's improvement in it.

https://addons.mozilla.org/en-US/firefox/addon/fxchrome/

Re: Firefox 28 Release Notes

#70
post #49

Interesting to see that now the current stable versions of Chrome and Firefox have dropped spdy/2, which is the only version of spdy supported by the current stable version of nginx. And nginx is the server used by more than 90% of hosts supporting spdy[1]. I presume this means it is mostly a Google/Twitter/Cloudflare thing for now since they seem to all be running spdy/3.1 in production. [1] http://w3techs.com/techn…

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.

These days you just have compile it with --with-http_spdy_module in configure step. (for the current 1.4.6-stable). We were about to go into production but will hold it off.

Also the current mainline 1.5 version has implementation of spdy/3.

Post reply on HN