Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Retiring Chrome Frame

blog.chromium.org

Post reply on HN
Print view View original

51–60 of 102 posts

Re: Retiring Chrome Frame

#51

Post by epmatsw »

atesti wrote: post #44

Currently all those XP users can easily run Firefox or Chrome and are therefore not stuck to IE7, but I really wonder how long that will be possible. Will it be 1 or 2 years until Chrome won't run anymore on Windows XP? (Firefox has problems with the linker of older visual studio compilers already and any software compiled with a newer microsoft compiler will need the msvcrt update, unless you use http://kobyk.wordpr…

If you're relying on more than 6 months of support (or any support really) from a free product in an enterprise environment, you're doing it wrong.

Re: Retiring Chrome Frame

#52

Post by omh »

apalmer wrote: post #25
timothya wrote: post #24

Earlier quoted context omitted.

What were you paying for Chrome Frame? Sometimes, it makes sense to retire products. And if you're not making money on the product, then it can be expensive to keep supporting it. I think six months is still a reasonable amount of advanced notice. No matter what, a small minority will be unhappy. I think the real lesson here is: don't build something serious on top of a product you don't pay for and you don't have an…

I understand this completely. But moves like this is why you see Internet Explorer 6 still in the wild. Because C-levels can be confident that Microsoft will continue to provide baseline support, security patches, and forever. My boss didn't even get annoyed, he just said 'too funny' and reminded me of when he was telling me to just build on IE7 baseline. 6 Months in the Enterprise world is a barely time enough to sn…

Microsoft will continue to provide baseline support, security patches, and forever

Actually they're going to stop providing IE6/7 support and patches in a little under a year.

Re: Retiring Chrome Frame

#53

Post by daemonl »

snowpalmer wrote: post #42
bambax wrote: post #33

I don't understand the problem; Chrome can be installed on XP without administrator privileges, isn't that enough for Entreprise users?

Some organizations don't allow it by company policy, regardless of whether it can be installed.

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.

Re: Retiring Chrome Frame

#54

Post by atesti »

illyism wrote: post #50
atesti wrote: post #44

Currently all those XP users can easily run Firefox or Chrome and are therefore not stuck to IE7, but I really wonder how long that will be possible. Will it be 1 or 2 years until Chrome won't run anymore on Windows XP? (Firefox has problems with the linker of older visual studio compilers already and any software compiled with a newer microsoft compiler will need the msvcrt update, unless you use http://kobyk.wordpr…

Those XP machines can download an older version of Chrome if it ever comes to that. And if Google Chrome no longer provides support I'm sure Chromium will. XP is 10 years old. It's remarkable that Google does still support it (unlike Microsoft supporting their own software) so let's praise them on that.

That older version wouldn't get security updates. And if it were to get them, but no new features, future web devs would forever be stuck with that old legacy webgl ;-)

But you are right that they should be praised for the past work.

Re: Retiring Chrome Frame

#55

Post by guiambros »

hughw wrote: post #48
RobAtticus wrote: post #28

Earlier quoted context omitted.

Chrome Frame will still work after January, just it won't be updated anymore. I assume that means you can still rely on it for your product, no?

No IT manager would permit an unsupported browser plugin to remain deployed. Who's going to fix newly discovered exploits?

No IT manager worth its salt should be relying on a free, unsupported, 'as-is' version of a hack in the first place.

And even less something that was always intended to be a quick workaround for users under very strict (or lazy) IT organizations that didn't upgrade to a decent browser in years.

Kudos to Google for creating and supporting it, until now. Time to take off the training wheels.

Re: Retiring Chrome Frame

#56

Post by camus »

hughw wrote: post #48
RobAtticus wrote: post #28

Earlier quoted context omitted.

Chrome Frame will still work after January, just it won't be updated anymore. I assume that means you can still rely on it for your product, no?

No IT manager would permit an unsupported browser plugin to remain deployed. Who's going to fix newly discovered exploits?

the same IT managers that are "supporting" deprecated browsers and os that will never be updated anymore ? Who's going to fix newly discovered exploited ?

Re: Retiring Chrome Frame

#57

Post by tomkarlo »

apalmer wrote: post #38
tomkarlo wrote: post #30

This seems more like Google is retiring support for users of old Microsoft products... considering they're offering both a newer browser, and a newer option for running web sites that requires an old browser... you're only boxed out if you insist on continuing to run an old IE, rather than the newer options available from either company. How often does Microsoft create products to support other companies' legacy user…

hahahahahahahaaa you have no idea the vast amount of windows code that is emulation layers to ensure that other companies legacy users can continue to use programs designed for dos, windows 98 etc. Google doesnt have to do it, but like i said thats why the c levels insist on microsoft even when their products arent anywhere near the most elegant, feature rich, or performant.

That's supporting their own legacy products, not other companies'.

Re: Retiring Chrome Frame

#58

Post by scott_s »

I'm surprised by the negativity - I wasn't aware that Chrome Frame existed, but after reading about it, I would classify it as a neat hack. It's basically a way of shimmying in an entirely different browser. That sort of thing is, to me, clearly a stop-gap solution. I wouldn't want to support such a thing in perpetuity either.

Re: Retiring Chrome Frame

#59

Post by scott_s »

apalmer wrote: post #25
timothya wrote: post #24

Earlier quoted context omitted.

What were you paying for Chrome Frame? Sometimes, it makes sense to retire products. And if you're not making money on the product, then it can be expensive to keep supporting it. I think six months is still a reasonable amount of advanced notice. No matter what, a small minority will be unhappy. I think the real lesson here is: don't build something serious on top of a product you don't pay for and you don't have an…

I understand this completely. But moves like this is why you see Internet Explorer 6 still in the wild. Because C-levels can be confident that Microsoft will continue to provide baseline support, security patches, and forever. My boss didn't even get annoyed, he just said 'too funny' and reminded me of when he was telling me to just build on IE7 baseline. 6 Months in the Enterprise world is a barely time enough to sn…

Will Microsoft continue providing baseline support for IE6 indefinitely? I doubt it. The top Google hit for "ie6" is http://www.ie6countdown.com, which is Microsoft's own site for tracking and celebrating the death of IE6. I imagine that once those numbers get low enough around the world, they'll stop supporting it.

Re: Retiring Chrome Frame

#60

Post by dragonwriter »

atesti wrote: post #46
timothya wrote: post #24

Earlier quoted context omitted.

What were you paying for Chrome Frame? Sometimes, it makes sense to retire products. And if you're not making money on the product, then it can be expensive to keep supporting it. I think six months is still a reasonable amount of advanced notice. No matter what, a small minority will be unhappy. I think the real lesson here is: don't build something serious on top of a product you don't pay for and you don't have an…

One wasn't "paying" with money. But Google wants to move all of IT in a certain direction (where cloud and web based technology is acceptable). Therefore Google provided the illusion that it's possible to mix ancient IE6-IT with modern Chrome web apps. Developers could feel save that it's okay to use modern technology and still be able to reach old shops. And old shops might have started to adopt modern web apps, als…

> Now they are forced to think again how to keep the old IE6-intranet running next to some Google Docs stuff they bought...

The Chrome Frame retirement announcement points them to a solution for that, Google Chrome for Business [1] with Legacy Browser Support [2].

[1] https://www.google.com/intl/en/chrome/business/browser/

[2] https://www.google.com/intl/en/chrome/business/browser/lbs.h...

Post reply on HN