Live data from Hacker News

Firefox Bugzilla: Remove Pocket Integration

bugzilla.mozilla.org

41–50 of 196 posts

Re: Firefox Bugzilla: Remove Pocket Integration

#41
post #10
post #7

Earlier quoted context omitted.

Is there a practical difference between disabling the features and just ignoring them?

Memory and CPU utilization for starters

Firefox makes extensive use of lazy initialization for a lot of its code. You typically don't pay the price for those features unless you actually use them.

Re: Firefox Bugzilla: Remove Pocket Integration

#42
post #10
post #7

Earlier quoted context omitted.

Is there a practical difference between disabling the features and just ignoring them?

Memory and CPU utilization for starters

A button that does an API call consumes very less resources until clicked.

Re: Firefox Bugzilla: Remove Pocket Integration

#43

Add yourself to the CC list to endorse this ticket, without cluttering up the thread with needless "I agree" posts! :-)

Done, thanks for the tip. I wasn't sure the best way to show that I agree with the bug. I also voted for the bug.

When you add yourself to a bug's CC list, every other person CC'd on the bug is sent a "bugmail" notification that you are now CC'd. If you just vote for the bug, you can receive bugmail notification without spamming all the other CCs. That's what I do. :)

Re: Firefox Bugzilla: Remove Pocket Integration

#44
post #11

What I don't understand is that Firefox also include its own read later service that sync to Firefox users account. Are they planning to drop its own implementation and partner with Pocket?

I answered this on reddit: http://www.reddit.com/r/firefox/comments/388ryl/pocket_and_h...

Re: Firefox Bugzilla: Remove Pocket Integration

#45
post #30
post #26

Earlier quoted context omitted.

You really start to wonder what pot they are smoking over there at Mozilla. Standard things you would expect from a browser, like a way to easily disabling javascript are apparently left to third-party extensions, because oh you don't want to bloat the browser. But hey, video conferencing on the other hand is such an essential part of the browsing experience.

They don't let users easily disable JS because that breaks so many webpages, and they didn't want to deal with supporting users who complained that Firefox wasn't working. http://limi.net/checkboxes-that-kill/

Good read, thanks for linking. Some points I'd never considered.

Re: Firefox Bugzilla: Remove Pocket Integration

#46
post #18

This trend of Firefox increasingly bundling more services and features is an interesting paradox considering that Firefox started as a quiet project to make a slimmed down, no frills browser in comparison to the main Mozilla browser. I’ve recently resumed using Firefox as my main browser partly driven by support of the project but also because Chrome was taking too much RAM and causing performance issues. Of course,…

Phoenix/Firefox was Mozilla's own lightweight alternative to SeaMonkey. Then Chrome was the lightweight alternative to a memory-hogging Firefox. Now Chrome is seen as sluggish and a memory hog. Where do we go next?

Re: Firefox Bugzilla: Remove Pocket Integration

#48
post #40

It is so unlike Mozilla to introduce something like that, I ran a virus scan and checked what programs had been installed recently -- I assumed it had been put there in the same way that IE users used to get the Ask Toolbar installed. Exactly how I felt. What the hell were they thinking? I'm generally very supportive of Mozilla, I even supported their initiative to put advertisements on Firefox's start page. But bund…

Hello is just a thin wrapper around WebRTC. That's why Chrome can receive Hello calls without an extension. There's barely anything to add on in that case.

[deleted]

Re: Firefox Bugzilla: Remove Pocket Integration

#49
post #18

This trend of Firefox increasingly bundling more services and features is an interesting paradox considering that Firefox started as a quiet project to make a slimmed down, no frills browser in comparison to the main Mozilla browser. I’ve recently resumed using Firefox as my main browser partly driven by support of the project but also because Chrome was taking too much RAM and causing performance issues. Of course,…

Phoenix/Firefox was Mozilla's own lightweight alternative to SeaMonkey. Then Chrome was the lightweight alternative to a memory-hogging Firefox. Now Chrome is seen as sluggish and a memory hog. Where do we go next?

Servo, when it's done. And from there, who knows!

Re: Firefox Bugzilla: Remove Pocket Integration

#50
post #18

This trend of Firefox increasingly bundling more services and features is an interesting paradox considering that Firefox started as a quiet project to make a slimmed down, no frills browser in comparison to the main Mozilla browser. I’ve recently resumed using Firefox as my main browser partly driven by support of the project but also because Chrome was taking too much RAM and causing performance issues. Of course,…

Phoenix/Firefox was Mozilla's own lightweight alternative to SeaMonkey. Then Chrome was the lightweight alternative to a memory-hogging Firefox. Now Chrome is seen as sluggish and a memory hog. Where do we go next?

I suppose, as far as the web platform is concerned, we aren't really going to replace HTML/CSS/JS so increasing the speed and memory management of javascript rendering is the clear way forward, e.g. with Servo https://www.mozilla.org/en-US/research/projects/
Post reply on HN