191–200 of 206 posts
This seems to reinforce the mindset that the web should be experienced and built using different tools for users vs. developers, and aside from thinking that's fundamentally condescending, I don't see why new tools couldn't simply be extended from FF's 'web developer' menu into a different mode of operation or even extensions. I think we're better off in a world where kids don't have to install ScaryFox on their tabl…
I'm still on the fence about having separate browsers for developers. It sounds nice as a concept but when I think about it more it seems like a disaster waiting to happen. For instance, when I want to debug my website I go to the dev tools within the browser I'm viewing because I know that my users are viewing the same browser (typically). Having an entirely different developer browsers makes the debugging experienc…
> 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…
This seems to reinforce the mindset that the web should be experienced and built using different tools for users vs. developers, and aside from thinking that's fundamentally condescending, I don't see why new tools couldn't simply be extended from FF's 'web developer' menu into a different mode of operation or even extensions. I think we're better off in a world where kids don't have to install ScaryFox on their tabl…
I understand the point, but I think there is a reality where developing and actually experiencing the product can be fundamentally different. For instance the security model for a browser should be ultra tight and protect the user from the site, but as a developer I'd want to access and modify my files directly through the inspector panel. Another example would be the use of cache, where I want the minimum possible r…
[1] https://code.google.com/p/chromium/issues/detail?id=337734
Earlier quoted context omitted.
I understand the point, but I think there is a reality where developing and actually experiencing the product can be fundamentally different. For instance the security model for a browser should be ultra tight and protect the user from the site, but as a developer I'd want to access and modify my files directly through the inspector panel. Another example would be the use of cache, where I want the minimum possible r…
A live example: If you are developing a chrome extension on Windows, everytime you open Chrome you'd be bugged with a popup which suggests "Disable Developer Mode Extensions". [1] Although developers are annoyed as hell, the Chrome team insisted this decision on the ground of protecting users. [1] https://code.google.com/p/chromium/issues/detail?id=337734
This appears to be a simple rebrand of Aurora with some extra features[1]. [1] - https://bugzilla.mozilla.org/show_bug.cgi?id=1076914
This seems to reinforce the mindset that the web should be experienced and built using different tools for users vs. developers, and aside from thinking that's fundamentally condescending, I don't see why new tools couldn't simply be extended from FF's 'web developer' menu into a different mode of operation or even extensions. I think we're better off in a world where kids don't have to install ScaryFox on their tabl…
Why is there this arrogant idea in the development world that everybody has to get into programming. If a kid wants to program (great!) she can easily download the development version. Calling it scary fox is just scaremongering. If anything getting the special development version might make her feel empowered.
Earlier quoted context omitted.
Why would any browser vendor have an incentive to remove or restrict developer features in released browsers?
It seems like it’d be beneficial to many web publishers if browser users couldn’t easily access underlying resources, and those companies could incentivize popular vendors to go in that direction (and every decent browser auto-updates, of course). Suddenly bypassing Flickr’s spaceball becomes too complicated for regular user. On the other hand, no one would bother with that in a world where non-mobile computers are i…
With FFOS, Android/Chrome, and MS there's a conscious effort to eliminate the difference in development between desktop, tablet and phone. With more people using computers, not as many people need or want desktop apps and those features on all of their desktop apps. If I suddenly need to edit an image, I don't need PS or even Gimp, I'm often fine with a web app.
Earlier quoted context omitted.
A fellow developer in my office uses Incognito mode, and it seems to work fine for him.
That reminds me: It would be nice if you could open several different incognito windows, each with their own session. That way one can debug user interactions without needing as many browsers as users in the interaction (or half of it because each browser has it's own incognito session in addition to the normal session).