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

Chrome browser for businesses

enterprise.google.com

Post reply on HN
Print view View original

81–90 of 282 posts

Re: Chrome browser for businesses

#81

Post by mSparks »

TwoBit wrote: post #45
notgood wrote: post #21

Earlier quoted context omitted.

Yeah, no; most times when you test in Firefox it works just fine with no changes; specially when you already tried on mobile, because if it works in mobile it works on desktop Firefox. The other thing is that major libraries (CSS, JS: jQuery, bootstrap, React) make sure they work on all browsers so you don't have to worry about that part. The winXP-IE6 was hell because that never happened, you always had to changes t…

I use Firefox on Android and often run into web sites that don't work right because they are dependent on some Chrome or Webkit behaviour, and I need to switch the browser to desktop mode to resolve the problem.

i often run into google web sites that render and behave terribly in android chrome (usually floating windows with the close hidden or extending outside the screen).

most web problems are now bugs either by the site developer or in a specific browser.

thats a long way from ie6 problems where either you needed a unique site configuration for every browser or supported ie6 only.

Re: Chrome browser for businesses

#82

Post by Freak_NL »

roblev wrote: post #67
jpochtar wrote: post #61

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…

For many organisations there is a real risk that a browser update will unexpectedly break a key internal application, which could have a catastrophic impact on operations. The vast majority of large companies will control and test key software updates, balancing the various risks (security patches, obsolescence, operational incidents..). Not allowing auto-updating to be controlled basically means that the software is…

I prefer Firefox Extended Support Release (ESR)¹ for this though. Every year (currently in March) the current normal Firefox version (that does auto-update) is forked for a new ESR support cycle and made available for acceptance. Three months later if all is stable, it replaces the previous ESR release series, and for a year corporate IT gets a browser that will only be updated with critical (security) updates; no new features, no removal of features. At the end of that year the cycle repeats itself, and you can roll out the new ESR series when you've confirmed everything works as it should.

1: https://www.mozilla.org/en-US/firefox/organizations/

Re: Chrome browser for businesses

#84

Post by alkonaut »

dingaling wrote: post #73
jpochtar wrote: post #61

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…

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.

Re: Chrome browser for businesses

#85

Post by alkonaut »

roblev wrote: post #67
jpochtar wrote: post #61

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…

For many organisations there is a real risk that a browser update will unexpectedly break a key internal application, which could have a catastrophic impact on operations. The vast majority of large companies will control and test key software updates, balancing the various risks (security patches, obsolescence, operational incidents..). Not allowing auto-updating to be controlled basically means that the software is…

Couldn't orgs just use multiple browsers to reduce risk? With some monitoring of which clients are used, one could remove e.g ie8 support once it's established that every internal product has been used long enough with ie10

Re: Chrome browser for businesses

#86

Post by saw-lau »

jpochtar wrote: post #61

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…

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.

Re: Chrome browser for businesses

#87

Post by Pica_soO »

alkonaut wrote: post #84
dingaling wrote: post #73

Earlier quoted context omitted.

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…

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.

Eh, yes, and the yells of "Over budget, we can not afford new machines for the whole team, just because your app is not 386 backwards compatible."

And the partial rollouts, with teams being split into and stuck- and demanding you hack together tooling on the fly to allow for work to continue anyway.

And the horrible cross-application databases, which would went inconsistent if you didn't include basically a reduced data version controlling in every of your applications.

And those proto-typed tools, made by some intern in obscure languages, that would in secrecy fester into the "Main-Tool" of a department. And all hell would break loose, if some virtual environment update would break those env-dependcies.

You know what- it was bad back then. Real bad. And today is better. And even nostalgia cant save it.

Re: Chrome browser for businesses

#88

Post by FLUX-YOU »

alkonaut wrote: post #84
dingaling wrote: post #73

Earlier quoted context omitted.

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…

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. :)

Re: Chrome browser for businesses

#89

Post by Quenz »

saw-lau wrote: post #86
jpochtar wrote: post #61

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…

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?

Re: Chrome browser for businesses

#90

Post by Quenz »

technion wrote: post #78
whateveracct wrote: post #40

Earlier quoted context omitted.

IETab - now that's a blast from the past o.O

I've got a medical application that only works in Firefox running IETab. Interestingly, it doesn't work in any version of IE. It's an odd product.

How the hell did this app manage to get developed?
Post reply on HN