Live data from Hacker News

Retiring Chrome Frame

blog.chromium.org

31–40 of 102 posts

Re: Retiring Chrome Frame

#31
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.

> can't rely on Google in the enterprise

  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
  EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES 
  OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
  NONINFRINGEMENT OF THIRD PARTY RIGHTS.
I think some people read that as "Hey, that's a nice software ya got there, buddy. It'd be a shame if your dependencies went away. Good thing I got this service contract right here..."

As much as I hate to admit it, sometimes the policy to never use 3rd party software without an explicit support agreement is quite sane. But this is also a good argument for why open source and minimal complexity are good choices.

Re: Retiring Chrome Frame

#32
post #22

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…

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.

Re: Retiring Chrome Frame

#34
If Chrome Frame is necessary for you, why not continue it as a separate open source project? Google has already helped you massively, it's not their job to manage your backwards compatibility issues for you...

Re: Retiring Chrome Frame

#35
post #26

Earlier quoted context omitted.

This is the opposite, this is just showing the c levels they were right all along, build on microsoft, 'no one every got fired for buying microsoft', because they will support their shit forever. I think i can get a supported visual fox pro environment if i want.

You can still buy a horse and buggy too. Does that make it the ideal option for transportation on the interstate?

I think you just come from a different perspective than me, i work in the enterprise for fortune 500 companies. The mindset and the process is just different. If the horse and buggy works, and is cheap, and doesn't have high maintenance costs, in the enterprise will gladly let the horse and buggy technology go until paste the day when we are flying spaceships to and from work.

I enjoy the witty snaps, but realistically, it just shows your out of touch with the enterprise space.

I am not talking client facing apps, all of those are cross browser up to date to ensure maximum visibility, i am talking intranet enterprise apps so hideous no one who isnt paid to use them ever would... these are the backroads that only the farmhands use. the overseers are like you want to throw an automatic carriage back here, but we pushed for it, and just as it rolls out i gotta tell em the automatic carriage company stopped selling gasoline, and they just look at me laugh, and say horses run on hay...

thats all it is aint the end of the world, aint even a big deal, i will write an active x control and embed it in the page to do what i need... horse and buggy style

Re: Retiring Chrome Frame

#36
post #33

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

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

#37
post #35

Earlier quoted context omitted.

You can still buy a horse and buggy too. Does that make it the ideal option for transportation on the interstate?

I think you just come from a different perspective than me, i work in the enterprise for fortune 500 companies. The mindset and the process is just different. If the horse and buggy works, and is cheap, and doesn't have high maintenance costs, in the enterprise will gladly let the horse and buggy technology go until paste the day when we are flying spaceships to and from work. I enjoy the witty snaps, but realistical…

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

Re: Retiring Chrome Frame

#38

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.

Re: Retiring Chrome Frame

#39
post #35

Earlier quoted context omitted.

You can still buy a horse and buggy too. Does that make it the ideal option for transportation on the interstate?

I think you just come from a different perspective than me, i work in the enterprise for fortune 500 companies. The mindset and the process is just different. If the horse and buggy works, and is cheap, and doesn't have high maintenance costs, in the enterprise will gladly let the horse and buggy technology go until paste the day when we are flying spaceships to and from work. I enjoy the witty snaps, but realistical…

Well... "enterprise" can sit still for as long as they want. I don't really care one way or another. Besides, eventually we'll be so far ahead that we won't even be able to hear them complain about the shrinking world they've built and refuse to leave. I've worked in government which traditionally is even worse than enterprise when it comes to things of this nature. But we had a pretty good IT department that didn't just dig in their heals and refuse to budge. Sure we weren't installing nightly builds or anything but we got fairly regular updates and stayed reasonably current. It is possible. Eventually it will catch up to you in terms of maintenance costs.

Re: Retiring Chrome Frame

#40

Anybody familiar with the architecture of Chrome Frame? In terms of how Chrome/Chromium is integrated, I'm wondering if it would be viable to maintain a fork of the Chrome Frame code or if there are "concessions" made for Chrome Frame in the Chrome/Chromium code that, if they go away, makes it impossible for Chrome Frame to function.

It would be a fair bit of work but it wouldn't be impossible. There are really only a couple of places in the main Chrome code base that are CF-specific - the automation interface and the external tab container.

Sounds like a business opportunity for someone. Even based on this thread there seem to be a few shops that would pay for support for it.
Post reply on HN