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

81–90 of 102 posts

Re: Retiring Chrome Frame

#81

Post by greghinch »

omh wrote: post #52
apalmer wrote: post #25

Earlier quoted context omitted.

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.

The sad problem is, if you want to build a product for large corporates, a lot of folks are still stuck on old XP workstations with the default software installed (IE7 if you're lucky), and likely will be well beyond the MS support window. This is just part of doing business in that sector, but I think we can all agree that having to build for IE6/7 compatibility stifles a lot of innovation.

Re: Retiring Chrome Frame

#82

Post by dubcanada »

robertshield wrote: post #43
dubcanada wrote: post #41

Earlier quoted context omitted.

Because they made it nearly impossible by only releasing half the code, not releasing any installer build, and only releasing parts of the build system.

All of the code necessary to build a working Chrome Frame and an installer binary is present in the open source repository. The code for the MSI isn't there, but that's just a very thin wrapper around the Chrome Frame and Google Update exe installers.

Yup it certainly is... too bad that the build is not usable without extensive knowledge of how to integrate it into IE. Something which a very limited subset of people know.

Re: Retiring Chrome Frame

#83

Post by Pxtl »

apalmer wrote: post #21

Google may be continuing with the 'Don't Be Evil' motto but they sure ain't standing by a 'Don't Be Dicks' motto. What major software company announces a deprecation with 6 months of support. I have something going out relying on chrome frame plugin going out next week, now I have to go with my tail between my legs. Well lesson learned, can't rely on Google in the enterprise.

Your lesson should have been made loud and clear by Google App Engine.

Re: Retiring Chrome Frame

#84

Post by fpgeek »

tanzam75 wrote: post #78
jordanthoms wrote: post #37

Earlier quoted context omitted.

... and then these big enterprises are surprised when they get outmaneuvered by a startup using technology which less than 10 years old.

A cruise line is not going to get "outmaneuvered by a startup using technology which less than 10 year old. Nor an insurance company. Nor a bank. Nor large agrobusiness. The tech industry is not the only industry that exists in the world. There are many industries where software does not form the basis of competitive advantage. In those cases, IT is not the most efficient use of capital.

Who says the cruise line, insurance company, bank, agrobusiness and so on are going to get outmaneuvered by a startup? They're going to get outmaneuvered by another big company in their line of business with less-stupid IT policies.

Getting these sorts of issues (and bigger ones) right is something big companies call "IT strategy" and they'll often pay consultants real money for it. That's because, done well, IT can be the foundation of significant competitive advantages. Is using a more modern browser going to create an advantage all by itself? Almost certainly not. But the kind of IT organization that can't even handle something that simple is going to struggle mightily with the bigger fish.

Re: Retiring Chrome Frame

#85

Post by zmmmmm »

oomkiller wrote: post #10

This is a huge deal for enterprise app developers. We've been able to develop on a modern web platform, but have our customers use our app with IE 6, 7 and 8 (via ChromeFrame). Now we're going to have to add support for at the very least IE8, since XP (still over 50% market share in business) isn't going anywhere anytime soon, despite Microsoft EOLing it. Most IT admins I've dealt with refuse to install any other bro…

> Now we're going to have to add support for at the very least IE8 ....

> Most IT admins I've dealt with refuse to install any other

> browsers on their systems, but don't have a problem

> with browser plugins for some reason

Why don't you just deploy Chrome itself? Google has made a version of Chrome that can install without admin rights.

I have a feeling this was Google's plan all along: 1) get everybody dependent on Chrome with Chrome Frame, 2) make version of Chrome that installs without admin 3) remove support for Chrome Frame 4) $$$ profit from massive switchover to Chrome inside the enterprise as developers make an end run around IT by using the non-admin install.

Re: Retiring Chrome Frame

#86

Post by jfoster »

Pxtl wrote: post #83
apalmer wrote: post #21

Google may be continuing with the 'Don't Be Evil' motto but they sure ain't standing by a 'Don't Be Dicks' motto. What major software company announces a deprecation with 6 months of support. I have something going out relying on chrome frame plugin going out next week, now I have to go with my tail between my legs. Well lesson learned, can't rely on Google in the enterprise.

Your lesson should have been made loud and clear by Google App Engine.

What do you mean? Google App Engine is business as usual.

Re: Retiring Chrome Frame

#87

Post by zaius »

robomartin wrote: post #71

Sometimes HN discussions are really funny. People are up in arms about a free product from a company with an established track record of killing products, having nearly zero customer service and not caring about financially hurting businesses who use their tools (no-recourse account cancellations, etc.). That's just too funny. What, you didn't know this could happen?

I know my parents are going to die, but I'm still going to be sad when it happens.

Re: Retiring Chrome Frame

#88

Post by fpgeek »

threeseed wrote: post #32
guelo wrote: post #22

Earlier quoted context omitted.

Another great opportunity to pressure IT to switch to Firefox as the standard.

There is still a ridiculous amount of enterprise web apps that are built for IE. Just saying "switch to Firefox" or "change products" is simply not an option.

So? Old, poorly-maintained systems have all sorts of issues. Not working with newer browsers is just one of them. Consider these possibilities:

- Maintenance and support costs are notably higher than they would be with a newer system. It is worth noting that, technically speaking, Microsoft hasn't stopped supporting Windows XP. They're just raising the price and requiring a bespoke service agreement for XP support.

- Not working with newer browsers means not working with smartphones and tablets. A company could be passing up opportunities to improve productivity with mobile devices.

- It may be difficult or (practically) impossible to scale an old, brittle system with the needs of the business, especially if the old system has issues with newer hardware.

- It may not interoperate well with newer systems in the organization, foreclosing opportunities to offer valuable products and/or services.

And so on. Letting parts of your IT infrastructure bitrot has long-term consequences and companies should realize that when they make IT decisions.

Re: Retiring Chrome Frame

#89

Post by dpedigo »

robertshield wrote: post #43
dubcanada wrote: post #41

Earlier quoted context omitted.

Because they made it nearly impossible by only releasing half the code, not releasing any installer build, and only releasing parts of the build system.

All of the code necessary to build a working Chrome Frame and an installer binary is present in the open source repository. The code for the MSI isn't there, but that's just a very thin wrapper around the Chrome Frame and Google Update exe installers.

If you've got a copy of the MSI already, run it against Dark (the WiX decompiler) and you'll be pretty much handled a copy of the MSI source. Obviously you'll have some cleanup work, but it's a hell of a start. http://wix.sourceforge.net/manual-wix2/dark.htm

Re: Retiring Chrome Frame

#90

Post by stesch »

As a programmer this makes my decision easier if I should invest time in Google products like Go and Dart.

No, even if they are open source, it isn't the same if Google retreats from the project.

Post reply on HN