> probably with partnerships like Pocket
Mozilla has repeatedly stated that they're not receiving any money from bundling Pocket, and I see no reason why they would lie about this considering that they're actively seeking to diversify revenue sources. And even if you think Mozilla is lying, there's no way that Pocket is putting up the hundreds of millions of dollars necessary to make their hypothethical contribution to Mozilla's coffers anything more than a rounding error. > I never mentioned that someone is lying!?
Sorry, when I said "even if you think" I meant "you" in the generic third-person sense, not you specifically. :)There's a lot of hate around pocket, and it provides a cool, but simple feature. Yet I haven't heard anyone who loves it and actively wants it. The best I've heard is "yeah, it's OK", even online. I don't know why they would push so hard for a product that there's so much hatred for, and nobody rooting for, whey they could just say "Wow, OK. Guess you guys don't want it. We're scrapping it". It's far from a killer feature, so who's it for?
Even if there isn't some sort of payola deal going on to feed that money back to Mozilla, this is clearly being done for profit. Maybe it's some sort of indirect benefit, maybe it's someone doing a favor for a friend.
The alternative isn't any better: if there isn't any benefit for Mozilla, they are letting for-profit businesses insert themselves as a feature dependency.
No it isn't.
The reason behind Pocket integration was thus:
Firefox wanted a similar "temporary bookmark" feature to augment Reader mode and other things. Instead of coding it themselves, they decided on using an existing addon that gave the same functionality.
There's no indirect benefit (aside from having a new feature). There's a very clear and logical reason behind the integration. In retrospect, they should have consulted with the community first perhaps, but it's false that Mozilla did this for some direct or indirect benefit.
Also the Developer Edition, which is the alpha channel, is multi-process as you'd expect it to be. But speaking of hundreds of tabs, try doing that in Chrome, do that in Firefox, and compare.
At least in my experience, bad example. Chrome works with ~300 Tabs, Firefox freezes or crashes regularly with way less then that. And this machine only has 8 GB RAM. Let's hope the current changes in Firefox stabilize it.
Ah yes. The infamous "16GB ram in a laptop is not enough because I use a web-browser called Chrome"-syndrome.
And then someone turns around and says Firefox has memory leaks. You'd think they were joking, but they're not.
Not according to Mozilla: http://venturebeat.com/2015/11/12/mozilla-has-no-plans-to-of...
pocket is moving out of the main tree back to being an add-onSorry but no, unless it has catched up with Chrome Developer Tools (back into native since the last 3 years so I don't know the actual differences).
EDIT: Made the content between parenthesis clearer.
The right way to look at this is to go back to what we used to suffer through and recognize that it's awesome that we have two sharp dev teams putting at lot of effort into making life easier for web developers. Using the “worst” one is still far ahead of the best two years ago.
As I mentioned, this goes back to approximately three years ago.
The developer tools console could do:
- completion while typing
- display JavaScript data structures in more visual way
- breakpoints on DOM changes, events and Ajax requests
- profile network, memory and cpu usage
- navigate cookies, indexdb and websql databases
- reformat JavaScript code
- CSS editor
- work as IDE
- debugger API to work together with IDEs like Netbeans
- profile 2D and 3D performance
Basically, even though I prefer native to web, while using Chrome Developer Tools I had the feeling I was kind of back to Smalltalk.
Additionally their website was better than MDN in terms of information, specially thanks to the many sessions on Google conferences.
https://developer.chrome.com/devtools
That said, maybe Firefox is now on par.
It's there.
> - display JavaScript data structures in more visual way
Sort of? Is the existence of the 'inspect' function enough?
> - breakpoints on DOM changes, events and Ajax requests
I'm not sure about this. I mean, you can set the breakpoints in code per usual but I expect you mean setting them on the nodes themselves and perhaps global breakpoints in the net panel?
> - profile network, memory and cpu usage
This sort of profiling?
https://developer.mozilla.org/en-US/docs/Tools/Performance
https://developer.mozilla.org/en-US/docs/Tools/Network_Monit...
> - navigate cookies, indexdb and websql databases
https://developer.mozilla.org/en-US/docs/Tools/Storage_Inspe...
By the by, WebSQL isn't part of any standardization track and will not be implemented in Firefox as it stands, and neither will IE it looks like.
> - reformat JavaScript code
You mean "prettify source"? If so, yes.
> - CSS editor
There's the Style Editor, and the side pane of the Inspector.
https://developer.mozilla.org/en-US/docs/Tools/Style_Editor
https://developer.mozilla.org/en-US/docs/Tools/Page_Inspecto...
> - work as IDE
I guess the Scratchpad is the closest thing to that. So technically, no. As a side note, there is the WebIDE for Firefox OS development.
https://developer.mozilla.org/en/docs/Tools/Scratchpad
https://developer.mozilla.org/en/docs/Tools/WebIDE
> - debugger API to work together with IDEs like Netbeans
It's possible with the remote debugging protocol but the only implementation I know of is the proof of concept that Paul Rouget put together two years ago, although I don't think he released any code.
http://paulrouget.com/e/devtoolsnext/
> - profile 2D and 3D performance
You mean FPS and such? If so see the profiling tools linked previously.
Mozilla's work on Firefox, Rust and Servo is great. Thunderbird and a real multi-process browser could get a bit more love. The later probably can only be achieved with a Servo based engine (probably not not with Gecko and its XCOM, XUL legacy code - the current multi process work uses just two processes (sandbox plugins) and doesn't scale - opening hundreds tabs won't spawn dozens of processes as we know from IE and Chrome (with all its downsides but even more upsides (stability, usability, UI latency)). Firefox with Firebug and all its plugins is the best web development browser, Chrome with its ever changing DevTools (UI changes) comes second (for me).
Mozilla's browser is very important for the open Web.