I completely agree that we want to view what our users are seeing, but as a counterpoint, that isn't even necessarily possible in any mainstream browser. We still have to do the majority of our development in our primary browser of choice and then load up Chrome, Firefox, IE, Opera, etc to see what the rest of the world sees.

I think it would be a mistake to completely remove the developer tools from the non-developer version of Firefox, but I'd also be fine using a different developer-centric browser for the majority of my development understanding that there may be small differences and edge cases that need to be tested on numerous other browsers.

You can't compare that. Chrome, Firefox, IE, Opera, etc all try to do the same stuff, they have the same goal and want to do the same. A developer version of a browser won't have that goal, it's goal is to do something else... it will do it differently.

One of the PM did a comment and gave as an example that they will block self-xss on Firefox, which won't be blocked on the developer version. It won't affect much but you can already see how it's affected. You will be able to run something on a browser but won't be able to do the same on another.

I seriously don't see why we need a developer version of a browser, except removing developer stuff from the real browser and/or adding different support (which will give you issue when you will move to a real browser).

> Having an entirely different developer browsers makes the debugging experience less realistic. It puts you in a position where you don't truly experience what the user does but what you feel more comfortable experiencing.

I don't really agree with this part; it's going to be using the same rendering and JavaScript engine so I wouldn't expect the experience to be different at all it'll just have far better access to developer tools.

Having said that, Mozilla didn't exactly put much of any content into their blog post so I could end up being wrong.

That's a valid point. However, my point is that it's simply a different browser that'll be built on different software, considering it is different.

This speaks to the general low quality of web specifications and/or inability of browser developers to create robust implementations of those specs.

In the vast majority of scenarios we don't think about using the same processor to experience the same thing a user does. (Certainly driver developers and other low level h/w people will occasionally run into h/w bugs but they're in a very niche field).

The web platform is a lot more complicated than any ISA. The right comparison is having the same operating system version as the user, and anyone that develops native apps does have to care about that.

>The web platform is a lot more complicated than any ISA.

Talk to intel engineers and you'll soon be disabused of that notion ;)