3 ms·

Companies also want their employees to be as productive as possible, which are likely already using Chrome at home because it has the best usability and quality

by meibo 6y ago

Companies also want their employees to be as productive as possible, which are likely already using Chrome at home because it has the best usability and quality of life for non-technical users. I don't think any IT department worth their while would ban worthwhile software because of some agenda that frankly just doesn't matter too much to most regular users, at least in an US context. In the EU this might be a bit different, as they would have an interest in getting Google out of their ecosystems - but we've seen that that just doesn't really work too well, with pilots in various governments. People aren't as productive and complain about not having the same Excel and the same Internet as they have at home.

zelon88 6y ago
How is expecting things to work "having an agenda?" For the longest time Chrome would search google first before local DNS for FQDNs. When I reported that years ago they labelled it "wontfix." In Chrome 69 they started single-sign-on and didn't get around to adding an option to disable until 71. And this autocomplete bug has been a problem for years also. There are valid reasons to switch. I'm not here to make users feel at home. I'm here to make sure the stack runs on their machine. I find that is easier to accomplish with Firefox.
pwdisswordfish0 6y ago
> Companies also want their employees to be as productive as possible[...] I don't think any IT department worth their while would ban worthwhile software This shows a disconnect / bubble. Lots of IT departments require permission to install any software, i.e., a whitelist, rather than the blacklist being proposed (and which is fine in this instance). Granted, many of those places don't care about their employees being as productive as possible (even if they tell themselves they do), and their IT departments aren't worth their salt, and this tends to be norm, unfortunately.

by meibo 6y ago

zelon88 6y ago

How is expecting things to work "having an agenda?" For the longest time Chrome would search google first before local DNS for FQDNs. When I reported that years ago they labelled it "wontfix." In Chrome 69 they started single-sign-on and didn't get around to adding an option to disable until 71. And this autocomplete bug has been a problem for years also. There are valid reasons to switch. I'm not here to make users feel at home. I'm here to make sure the stack runs on their machine. I find that is easier to accomplish with Firefox.

pwdisswordfish0 6y ago

> Companies also want their employees to be as productive as possible[...] I don't think any IT department worth their while would ban worthwhile software This shows a disconnect / bubble. Lots of IT departments require permission to install any software, i.e., a whitelist, rather than the blacklist being proposed (and which is fine in this instance). Granted, many of those places don't care about their employees being as productive as possible (even if they tell themselves they do), and their IT departments aren't worth their salt, and this tends to be norm, unfortunately.