Live data from Hacker News

Firefox 36.0 released

mozilla.org

201–210 of 256 posts

Re: Firefox 36.0 released

#201

Earlier quoted context omitted.

Anyone know of a brief list of workarounds/schemes/optimizations that probably won't be needed (or will be less needed) with http2? (or just add to this list) - css sprites - monolith js/css-files - rotating through 'alias'-subdomains for resources - trimming cookies / cookie-less domains (for request-headers)

Sprites and concatenated js/css are still useful. HTTP/2 lets you make 100 requests over a single connection, and that's a lot better than making 100 requests over 100 connections, but it's still not going to beat one request over one connection.

One image with 100 icons also still compresses better than 100 files with 1 icon each.

Re: Firefox 36.0 released

#202

Earlier quoted context omitted.

speaking of zooming, and if any Moz devs are watching, please finally fix radio and checkbox control zooming. it's been 7.5 years . https://bugzilla.mozilla.org/show_bug.cgi?id=400364

What? You don't like the challenge of trying to click on a micron wide checkbox on your new 4k laptop screen? That's half the fun, I say.

On a 4k screen I find that setting layout.css.devPixelsPerPx to ~2 works better than zooming.

Re: Firefox 36.0 released

#203

Yay! Time for another firefox rant. I love the idea of firefox and I used to love it a lot. But not now. I keep trying it and always go back to chrome. It crashes. A lot. Like, at least once a day I have to ctrl+alt+del and restart it on my laptop. It freezes and the window stops responding, it doesn't even paint. In the inspector, the DOM breadcrumb area scrolls and moves around. It's like the blink tag, only worse.…

The speech bubble by the way is a way to video chat from the browser itself. It uses WebRTC which is already in modern browsers so its not like they've added a ton of code to get that feature baked into the browser. Not sure why you saw O2 but I saw Telefonica which is the company that works with Firefox to deliver their Firefox OS phones. I suppose Telefonica/O2 is needed because even though WebRTC is a real-time di…

>The speech bubble by the way is a way to video chat from the browser itself. //

You know there are a myriad of ways to use the browser to do video chat already - websites that offer WebRTC video chat. You follow a URL, maybe from a bookmark, and use the one you want (eg http://appear.in).

None of that requires modifying browser chrome nor forcing buttons on to established users toolbars.

This is a marketing deal disguised as browser development.

Re: Firefox 36.0 released

#204

Earlier quoted context omitted.

Anyone know of a brief list of workarounds/schemes/optimizations that probably won't be needed (or will be less needed) with http2? (or just add to this list) - css sprites - monolith js/css-files - rotating through 'alias'-subdomains for resources - trimming cookies / cookie-less domains (for request-headers)

Sprites and concatenated js/css are still useful. HTTP/2 lets you make 100 requests over a single connection, and that's a lot better than making 100 requests over 100 connections, but it's still not going to beat one request over one connection.

Sprites are way more demanding memory wise than smaller images.

Re: Firefox 36.0 released

#205

Earlier quoted context omitted.

It's pretty easy to create a blank profile. That isn't magic wand easy, but it's a low bar.

firefox.exe -p -new-instance Should open a new instance of Firefox in the profile dialog, where you can create a new profile. I'm not sure about "-new-instance". I've only used -no-remote but the release notes say remote commands have been removed. Some quick research turned up -new-instance as a substitute.

-no-remote is the same as -new-instance except that the instance won't listen to remote commands.

Re: Firefox 36.0 released

#207

Earlier quoted context omitted.

Sprites and concatenated js/css are still useful. HTTP/2 lets you make 100 requests over a single connection, and that's a lot better than making 100 requests over 100 connections, but it's still not going to beat one request over one connection.

Sprites are way more demanding memory wise than smaller images.

Performance on the Web isn't RAM-bound at this time, unless you're running on a Raspberry Pi or somethin. Network performance is a much stronger limiting factor, which is why protocols like HTTP/2 are being made in the first place.

I'm also skeptical that sprites must necessarily be significantly more demanding memory-wise than smaller images. Implementations may vary, but at least in current browsers, when you make an Image tag/object with the same source as one you've already loaded, the second one loads instantly. This at least makes it appear that both image tags are getting some kind of lightweight view into the same image data -maybe just a pointer to the same bucket of bits- as opposed to having to re-download and/or re-copy the image data for each instance.

Re: Firefox 36.0 released

#208

Earlier quoted context omitted.

Chrome SignIn is basically the same thing as Firefox Sync. It keeps your bookmarks, extensions, and stored passwords (all controllable) in sync between the different devices you use the browser on.

The key difference being that Firefox's implementation gives you all this without having to let Google rifle through the data you want to sync.

Not anymore: as I posted last night[1], Mozilla could choose to give themselves access to your password, when you create your account or when you change its password. Anyone who is able to successfully MITM you & Mozilla (say, someone with a Komodia cert if you're infested with Superfish, or any of the CAs in the world, or anyone who can compel them to certify a MITM cert) can do the same.

Google do allow you to use your own passphrase, so conceivably at this point Chrome is at least somewhat more secure than Mozilla.

It's a crying shame.

[1] https://news.ycombinator.com/item?id=9098459

Re: Firefox 36.0 released

#209
post #16
post #10

Earlier quoted context omitted.

Adding multi-process to a large project that was not designed for multi-process is an astronomical amount of work. And Firefox's approach has advantages over Chrome's, so they're not simply playing catch-up.

Chrome's first public release, which included multiprocess tabs, was on December 11, 2008. There has been more than enough time for Mozilla to catch up.

Note the words "first public release". Not to knock Chrome's achievements in this area, but it's an inescapable fact that they did not have any previous architecture to migrate from. Taking any nontrivial program that has had years to assume a single-process architecture, and updating it to work in a multiprocess manner, is hard. It takes time to do properly.

Re: Firefox 36.0 released

#210

Earlier quoted context omitted.

About time! I've been using it a lot on FF mobile where it's super useful. This feature was announced long time ago. I've been using the Enjoy Reading extension for a while and found no good replacement when it was abandoned.

For desktop I use the Readability Bookmarklet[1]. Gets the job done. [1] https://www.readability.com/bookmarklets/

Yes, plus you can send the extracted articles directly to the kindle.
Post reply on HN