Re:Retiring Chrome Frame
by bambax on Thursday June 13, 2013 @04:39PM
(#5876408)
I don't understand the problem; Chrome can be installed on XP without administrator privileges, isn't that enough for Entreprise users?
[ Parent
| on HN ]
99% of monolithic web intranet application only works in IE 7 (8&9 in compatibility mode), you cant expect your user to have a separate browser for one subsection of a web app, and IE for the rest of it.
Re:Retiring Chrome Frame
by dragonwriter on Thursday June 13, 2013 @07:07PM
(#5877219)
Chrome in managed environments supports this via Legacy Browser Support, which allows administrators to select (specifically down to port and URL, if necessary, or just by hostname) which sites to open with IE with the rest defaulting to Chrome (or vice versa, as is most convenient for the particular environment.)
Re:Retiring Chrome Frame
by snowpalmer on Thursday June 13, 2013 @05:36PM
(#5876756)
Some organizations don't allow it by company policy, regardless of whether it can be installed.
Re:Retiring Chrome Frame
by fuzzywalrus on Thursday June 13, 2013 @05:49PM
(#5876822)
I've still yet to wrap my mind around the Chrome frame from an IT perspective. Even with thin clients, you could install FireFox or Chrome on your XP VM, and it'd result in less CPU overhead. I'll admit, IT is not my specialty nor is mega corporate politics, but I'd would venture to guess the cost of IE6-8 in IT overhead would negate any cost of deployment of Chrome or FireFox ESR.
Anyone care to enlighten me as to why?
Chrome Frame was brilliant: users still click on the blue e, all of the horrible enterprise loathware apps continue to work but pages which opt-in are suddenly much better looking and faster.
Large organizations, particularly those which train non-IT workers to follow consistent workflows like to avoid any changes. Chrome Frame was great because it was a minimally disruptive opt-in for a better web; Chrome for Business requires you to switch to Chrome for everything and whitelist legacy apps/sites – that might happen if someone at the C level is really scared about security but it's way more risk and the shops in question are among the most risk averse.
Sadly, it's not about logic in a lot of these cases.
Some I.T. policies also disallow chrome frame. Google had provided a policy loop hole which helped ie6 look like a legitimate option. Its not anymore...
I think its time enterprise I.T managgers update their thinking, and I think the less comfortable backwards compatible tools that exist, the better.