I can't seem to make the switch away from Chromium devtools. I don't know whether it's because I am habituated to the Chromium ones or whether there is something klunky about the Firefox devtools that I can't put my finger on.
I tried FF dev edition with Angular, it was getting randomly slow. Weird issues popping while debuging typescript code. In the end I have to use Chrome for my work, even though I would like to drop Chrome personaly. That said, I sometimes have to debug Angular applications on IE11 which is worst nightmare...
Firefox 70 released for Firefox Quantum: Developer Edition
41–50 of 116 posts
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#42Earlier quoted context omitted.
They are not, apparently the reasoning was not to make Firefox bigger with needless features not requires by non-techie users. At least this is how I recall it, please anyone correct me if I am mistaken.
It's a beta with special features for developers. right now dev edition for me is 70.0b1 regular is firefox 68.0.2 It also has the new logo and I suppose there's new stuff on the dev tools. "What's new" page is broken so not absolutely sure.
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#43[0] - https://blog.mozilla.org/blog/2017/09/26/firefox-quantum-bet...
[1] - https://en.wikipedia.org/wiki/Firefox_version_history#Firefo...
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#44Can anyone explain exactly what's different about this? Are all these features not in normal Firefox? Is this like a beta of normal firefox, set of extensions, or a significant fork?
Special features: kind of like an IDE on top of Firefox, meant to be used by web developers. Comes with its own config profile, so you can fuck around and not break stuff in stable/beta that you are supposed to have concurrently installed. Kind of like beta: all of the new APIs and features related to web development are there three months before they hit stable.
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#45Has there been a significant update to the devtools recently? I've been a devedition user for years, odd to see it on the front page of HN just linking to the homepage..
This is why I dislike these software posts without context. It's never clear if there's been an update or if the submitter just discovered them for the first time.
Why is this interesting? For Wikipedia articles about people this is doubly important because the title is inevitably just the person's name - unless you already know who that person is there's no hint as to why they are significant.
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#46Did they fix the memory bloat on Mac OS? It’s pretty much useless to me on MacOS.
I saw a tweet recently about macOS power consumption fixes: https://mobile.twitter.com/pcwalton/status/11661937700160798... Haven't noticed any memory bloat myself though (= it consumes a lot of memory, like any browsers). It's somewhere between Safari and Chrome.
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#47Earlier quoted context omitted.
Other than the web socket support in Chrome, the FF dev tools are a billion times better than Chrome now. I cannot work without the css layout overlays from FF dev tools. Makes working with grid layouts insanely easy.
how many production websites you work on use Grids? just curious.
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#48I can't seem to make the switch away from Chromium devtools. I don't know whether it's because I am habituated to the Chromium ones or whether there is something klunky about the Firefox devtools that I can't put my finger on.
Chromium for web dev.
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#49I can't seem to make the switch away from Chromium devtools. I don't know whether it's because I am habituated to the Chromium ones or whether there is something klunky about the Firefox devtools that I can't put my finger on.
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#50I can't seem to make the switch away from Chromium devtools. I don't know whether it's because I am habituated to the Chromium ones or whether there is something klunky about the Firefox devtools that I can't put my finger on.
Having recently switched to Edge Dev after having used Firefox for roughly a year (and Chrome before that), I'd say Firefox devtools' strongest point are the style editing stuff. Somehow Firefox devtools feel a bit clunkier when working on JS projects but they offer a lot of neat gimmicks if you dig into the depths of CSS. I also find the guidelines when highlighting an element more helpful than in Chromium for align…