nachtigall

I switched from Firebug to DevTools one and a half years ago and - while I have huge respect to the innovations that came from Firebug's ideas - I'm not looking back as the native devtools have more features these days and a better UI in my option.

So thanks to the dev team and the volunteers picking up my and others bug reports at http://firefox-dev.tools/ (I just leave this to the crowd here on HN ;)

Same reason as why Google has buried open standards like RSS or XMPP based GTalk.

Seriously I do not think that the stakeholders' values of Google are the same as the ones by the Mozilla fundation (which also has a corporation but mainly due to taxing and employing reasons).

I'd even say: The moment Firefox would not exist anymore, we there would be not-so-user friendly changes to Chromium or Chrome in the interest of Google. http://robert.ocallahan.org/2014/08/choose-firefox-now-or-la...

Pretty sure the Chrome team will do so internally. But I am also pretty sure that they won't share with the rest of the world.

So kudos to mozilla for making this public.

Not a single radio station in Greenland?

Ok. I also had this "scrolling being faster than rendering" half a year ago or so, but switched to the Nightly version than which had the APZ feature (https://hacks.mozilla.org/2016/02/smoother-scrolling-in-fire...) integrated already on Android by then. And where this all worked pretty smooth. I thought this was already rolled out for stable, too...

I'm pretty happy with Firefox for Android with the AdBlock Plus add-on. What makes you want to switch?

Mind sharing a link to the app?

Interesting. Mind sharing a link to your add-on?

The Nightly branch of Firefox for Android (which I personally use day by day and find very stable) has an option for "Tracking Protection". Works like https://support.mozilla.org/en-US/kb/tracking-protection-fir... but also in non-private mode.

4. Organize with (some of) your co-workers, maybe join a union. Act together instead of fighting for higher wages on your own.

Seriously, the moment you are on a "secret" one-to-one with your boss you have already lost. There's reason why unions have always bargained collectively, and there's also reason why bosses have always tried to avoid this.

How is this better/worse than https://addons.mozilla.org/en-US/firefox/addon/easy-password... which claims that "No web servers involved, the data never leaves your computer."?

lol, fantastic catch :-D

For every one not familar with german laws: You must drive right unless you are overtaking a slower car that is in front of you. And you are only allowed to overtake on the left side of another car. So if everyone drives the left lane, there's no way of overtaking anybody - something that would drive (no pun intended) all the other drivers nuts and you start to honk like crazy (which you are not allowed actually) or to give signals with the lights (which you are also not allowed) to the car in front of you ;)

I don't understand your question.

> Would you say the Firefox debugger works equally well as the Chrome variant?

Are you talking about the native debugger. Not sure. I only use the Chrome debugger from time to time, but mostly use the Firefox debugger. So it's ok, but since I use it all the time, I know it has its warts...

Anyway, there are completely rebuilding it using react.js at the moment: https://hacks.mozilla.org/2016/09/introducing-debugger-html/

> (In terms of responsiveness, integration, overal experience).

As said I use it (firefox and vs code) all the time as a JS developer.

> I really fancy the JS debugger of VSCode but I'd hate to drop Firefox for that.

That's the part I really do not understand. I do use Firefox (and its native devtools), and I do use VSCode plus its Firefox extension. So no reason to drop Firefox ;)

Same here, but for Firefox (which I prefer for WebDev). Just switched to VSCode because it's the only editor[1] that has a working JS Debugger for it: https://github.com/hbenl/vscode-firefox-debug

[1] Though other editors might follow. Just saw that the Firefox Debugger team would be interested in integrating their new react/redux based debugger into Atom: https://twitter.com/clarkbw/status/783358566858010624

Same argument why Opera chose to base their browser on Blink. PDFium is 100% dependent on Google. I do not think it's a clever move to go down into this dependency.

Sure web > pdf > flash in terms of mozilla's focus, but I fear pdf will be part of the web for a long time to come.

Thanks. Your answer and your work even more so are very much appreciated! I hope you can keep it up. Maybe some of the other companies could also jump in with as financier (though I do not have too high hopes for this as taking is more common than giving...)

Investing in Rust is the best Mozilla can do for the long-term prospects of Firefox. The safety and speed of a modern language like Rust could be a real game changer when it comes to the competition with Chrome.

How many people are working on PDF.js that are paid by Mozilla? https://github.com/mozilla/pdf.js/graphs/contributors looks like there are only 2 main contributors (i.e. maintainers, in the sense of continuously and ongoing committing for longer time)

And I find this to be even more astonishing as OL3 uses Googles Closure compiler who's very advantage should have been better JS minification (not only minimizing/uglifying but actually removing JS parts that are not needed).

Even a custom OL3 build which only has the canvas renderer, a WMS layer for background and a Vector layer for POIs does not get smaller than 200k. I think leaflet is half the size.

Congrats. As a longterm and happy OpenLayers user (version 3), what are the main advantages of Leaflet over OpenLayers?

Then: Don't be evil.

Today: Google is the new MS. XMPP kicked out of Google Talk, RSS put on a hold. If there wasn't Firefox, Chromium would be burried. I'd even wish that Bing would be more successful, let alone DuckDuckGo.

btw, do you have a link? I wonder if this works with sass/less and uglify transpilers...

ok, I think that's not available with firefox devtools, but in case your SPA is react based, I think that the react devtools addon has hot (and state preserving) reloading: https://addons.mozilla.org/en-US/firefox/addon/react-devtool...

Is this feature natively built into the devtools of chrome or a chrome extension?

You might want to use wepack dev server or the live reload addon. That's what I use together with Firefox (Developer Edition).

> Also, it lacks drag-to-refresh as it does in Chrome. But I can tap the address bar and "enter" of course.

You can also "Menu" > "Reload".

> I want to be able to modify/add code

Yes, but I want to do that in my editor, not in the browser.

> try it out, then rewind, and try something else. Then save my changes once they work perfectly.

Certainly I do not want to copy'n'paste the code then back from browser to my editor.

Let me all do this in my editor of choice. The browser is only where I execute stuff, a debugger belongs into the editor/ide.

FWIW, I think it's planned by debugger.html project that the debugger can be used by different editors/IDEs. See the presentation at React Rally (relevant snippet is at https://www.youtube.com/watch?v=Fk--XUEorvc&feature=youtu.be...) showing the integration into emacs or even using debugger.html as CLI tool.

Session setup is a real showstopper if there are no builtin contacts. If I have to paste the talky.io URL first with <some-other-chat-program>, why not use <some-other-chat-program> in the first place?

I know I can email (where I have an adress book) the URL, but why use another communications channel for call setup.

I was about to use it as a OS-independent alternative to Skype (I'm on Linux). And I wanted to use this, also instead of facebook chat and the likes.

The moment they removed the contacts feature it was dead for me. Although, to be honest, it never really worked (sometimes no audio and stuff like that).

The idea, that I have to first email the chat URL and then I can make a conversation is like writing a letter first before doing a call. Fundamentally wrong conversation setup.