Live data from Hacker News

Chrome browser for businesses

enterprise.google.com

151–160 of 282 posts

Re: Chrome browser for businesses

#151

Earlier quoted context omitted.

I think it became harder to write true desktop apps once VB6 was killed off in favor of .Net with its higher learning curve. As bad as a real language VB6 and it's GUI builder were, it did allow even amateurs to write a decent working crud app in minimal time.

I still think VB6 was the pinnacle for writing line of business CRUD apps. I've been told there are still some VB6 apps I wrote ~15 years ago running at a big enterprise I once worked for.

Delphi was the pinnacle. But VB had definitely set the trend.

Re: Chrome browser for businesses

#152

For me Chrome is already the new IE: good enough to saturate the market to the point where devs stops caring about standards compliance. Personally I have tried to like it, multiple times but I always get annoyed and go back to FF. But then again I prefer Linux over Mac and Netbeans over IntelliJ so maybe it's just me.

What standards do they not follow?

The biggest issue is the experimental features webmasters use and then force rest to use Chrome. I'm not so sure Chrome themselves not caring about standards.

Re: Chrome browser for businesses

#153
post #107

Earlier quoted context omitted.

You wouldn't have to use antiquated tools and practices just to use desktop apps. I'm not arguing to use the old apps, I'm arguing that a lot of new development should be desktop when it's often made as web apps without thought. We threw all the good stuff with desktop out at the same time as we moved to intranets. You can still have centralized deployment, thin clients etc, but have the niceties of proper native app…

> A clean understandable web UI is good for a seldom used app, but a lot of the intranet apps are "constant use" and were faster to use in their legacy dos implementation than the newer web version. Browser hell just makes the problem worse. This. Click, wait, click, wait, click, wait is in no way better than how quickly you can fly with a well memorized set of keyboard shortcuts in a native app.

I use keyboard shortcuts extensively in gmail, jira, stash, and a bunch of other apps.

There's no problem implementing it. The designer should just think about it.

Re: Chrome browser for businesses

#155

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…

IE6 was an exception though... It it's day websites were specifically made to run on IE6, which was highly non-standard, and nothing else. Nothing is made to run on only Chrome 38 now. We aren't in the world of and anymore.

Most companies I know of (customers) let browsers auto upgrade now or they vet upgrades and they get pushed to client machines in a few days.

Re: Chrome browser for businesses

#157
post #134

Earlier quoted context omitted.

I think this is a weak argument. The problem here is that companies think that software can exist in some sort of "done" state, where no further updates or development is required. That has never been true. The hardware and software changes. The infrastructure it connects to changes. But most importantly, your workflows must evolve if you are to remain efficient. If you roll your own software, you either commit to co…

I question if you've worked with large enterprises. They freeze everything for a decade or more. Think about a bank with 500 offices, a dozen tellers at each office. Having their internal web app that everyone uses go down because of an auto upgrade could cost them hundreds of millions. They have a very different risk appetite.

They used to, this is no longer the norm though. The norm is moving to patching systems regularly.

Re: Chrome browser for businesses

#158

For me Chrome is already the new IE: good enough to saturate the market to the point where devs stops caring about standards compliance. Personally I have tried to like it, multiple times but I always get annoyed and go back to FF. But then again I prefer Linux over Mac and Netbeans over IntelliJ so maybe it's just me.

What the hell are you talking about? Chrome's support for standards is stellar. It's actually better than FF's.

https://kangax.github.io/compat-table/es6/

https://kangax.github.io/compat-table/es2016plus/

http://caniuse.com/#feat=async-functions

http://caniuse.com/#compare=ie+11,edge+14,firefox+50,chrome+...

Re: Chrome browser for businesses

#159
post #86

Earlier quoted context omitted.

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.

It's true, but you can turn that stuff off. You want to turn off things under Privacy like "Use a web service to help resolve navigation errors", "Use a prediction service to help complete searches and URLs typed in the address bar", "Automatically report details of possible security incidents to Google", "Use a web service to help resolve spelling errors", and "Automatically send usage statistics and crash reports t…

Are you sure those can't be configured via group policy? Maintaining a fork seems like an absurdly overcomplicated and expensive approach.

Re: Chrome browser for businesses

#160

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…

It's already possible to disable Chrome auto-update, and enterprises that wish to already do it. I've worked in an environment that did, years ago. My personal preference remains to allow silent auto-updates for software that auto-updates silently like Adobe Reader or Google Chrome to continue to do so... as long as they have yet to break the environment. (And it saves on management headache for a piece of software we don't really support the use of heavily in our environment.)
Post reply on HN