91–100 of 282 posts
Earlier quoted context omitted.
This appears to go far beyond that though. The policy and maintenance pieces in IE/Edge were one of the biggest reasons for some of the larger companies I've worked with that they had for staying off of other browsers. This looks to fix that.
It'll be interesting to see if this causes some "no open source, even if a support contract can be purchased" policies to get changed.
Earlier quoted context omitted.
Bingo. One might say the economic system in whole really pushes monopolies or oligopolies.
One might say that if one were completely ignorant of economics and economic history. There are no examples of long running monopolies unsupported by state power.
For me Chrome is already the new IE: good enough to saturate the market to the point where devs stops caring about standards compliance. Personally I have tried to like it, multiple times but I always get annoyed and go back to FF. But then again I prefer Linux over Mac and Netbeans over IntelliJ so maybe it's just me.
Earlier quoted context omitted.
I'd just be happy to be able to use it at all at work. Our organisation blocks it because, apparently, 'it sends a lot of data back to Google.' I have no idea if this is true or not.
Why would they change their reasoning with this new enterprise version?
Is this about replacing one monopoly with another? It is slowly starting too look like in the early 00's, most developers are starting to support only chrome, with no testing in Firefox or latest IE. On Android it is even worse, no one is testing with Firefox Mobile (Fennec) - this is WinXP-IE6 all over again.
Is anyone else concerned that this means IT can choose to hold back the version of Chrome in their organizations? Auto-updating Chrome has been low key one of the best solutions to the pain of backwards compatibility with older browsers. In the past we not only had to worry about compatibility between browsers, we had to worry about compatibility between browser versions. Further, auto-updating Chrome as dramatically…
Companies have far too much internal plumbing to permit browsers to auto-update themselves. Being feature-compatible with the latest SV-poster-child website is insignificant compared to maintaining stability for the tax-management team's internal web app. I was once involved in an IE6 -> IE8 upgrade for a Fortune 100 corporation. It took nine months to analyze all the possible impacts and implement mitigations before…
Earlier quoted context omitted.
It's amusing how we see web apps as the solution to deployment woes. I miss proper custom desktop apps with horrible looking cluttered interfaces. Soo productive compared to any web based interface for almost all tasks.
>I miss proper custom desktop apps with horrible looking cluttered interfaces. Soo productive compared to any web based interface for almost all tasks. You mean where everything runs on the UI thread? Gotta pass on that. :)
Earlier quoted context omitted.
I completely agree. It's re-enforced with Chrome's supplied dev tools which are really, really nice (I always found them far better than Firefox's built-in or Firebug). It's going to be harder to unseat Chrome. IE 6 wasn't so difficult due to an increase in competition who offered features that IE wasn't even working on (standards, tabs, etc). How would you even unseat Chrome?
Safari and nowadays Chrome DevTools are great. I miss the "DOM" tab, that Firebug for Firefox had features had, and I haven't found anywhere else. You can browse the DOM tree state and edit - similar to Smalltalk and Windows Registry - very useful & powerful. Sadly, they just killed Firebug, broke the addon, deactivated it with an update and replaced it with a still not feature-complete (at the moment sub-par) soluti…
It's in the Fx DevTools sinve v48 [1]. You may need to enable it though in the DevTools settings.
> Sadly, they just killed Firebug, broke the addon, deactivated it with an update and replaced it with a still not feature-complete (at the moment sub-par) solution.
Who's they? The Firebug Team works with the DevTools team since forever to port all functionality to the internal tools. The Firebug Team decided it was not worth to maintain the standalone version beyond v2 (also related to architectural changes to Fx, see project e10s) since they almost achieved feature parity by now and are working on the last remaining pieces [3]. Firebug v3 is Fx DevTools + a lot of extra features that Firebug never had. If you miss a feature in the DevTools, try Fx DevEdition [3].
[1] https://developer.mozilla.org/en-US/docs/Tools/DOM_Property_...
[2] https://hacks.mozilla.org/2016/12/firebug-lives-on-in-firefo...
Earlier quoted context omitted.
I completely agree. It's re-enforced with Chrome's supplied dev tools which are really, really nice (I always found them far better than Firefox's built-in or Firebug). It's going to be harder to unseat Chrome. IE 6 wasn't so difficult due to an increase in competition who offered features that IE wasn't even working on (standards, tabs, etc). How would you even unseat Chrome?
Firefox dev tools are sometimes painful to use and lacks some important features which Chrome's has. Some examples: - debugging with source maps: it doesn't work properly (I can set breakpoints and debug variables content on typescript files in Chrome, but not in FF) - JS exceptions: clicking on the filename inside the stack opens a new window with the source of the JS file, not the debugger (ugh) - doesn't support t…
[1] https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&c...