3 ms·

It sounds like you have never worked in at a place like ${BIG_CORP}, which is totally fair. Let me break it down for you: > -Simple license management (what's

It sounds like you have never worked in at a place like ${BIG_CORP}, which is totally fair. Let me break it down for you: > -Simple license management (what's simpler than reimbursing personal expenses?) Try doing that x100,000, every month. It gets annoying fast > -Organization-wide policy management (huh?) Only group X is allowed to use these features, and only group Y is allowed to use code licensed in that way, etc. > -Industry-leading privacy (no idea what this means, how is this better than personal Copilot per person) This sounds like mostly marketing BS, but likely still better than personal copilot. Have you read to copliot EULA? I haven't. I would guess they are using code you write to re-train their AI. You know who has read the EULA? Corporate lawyers. They don't want Github reading their internal code, so I'm sure the license for Enterprise does not involve sending data back to Github. -Corporate proxy support (what even is this) If you work at any large company (not even a super big FAANG or something) you will have this. You don't want random employees being able to access any random site. E.g. in general devs should not be able to access their personal drop box account because its an easy way to steal data without the company knowing. So all their network will be behind a proxy and everything has to be whitelisted. This proxy support is basically integrating with that system.

icelancer 4y ago
I worked for a billion dollar company prior to running my own. >> Try doing that x100,000, every month. It gets annoying fast We didn't. Accounting did. Our company had a reimbursements-only policy, no corp cards. It was great, especially those of us who flew a lot and banked tons of airline, hotel, and credit card points. The other stuff, sure. Doubling the price? I don't buy it. Are large corps really stopping people from buying Copilot on their own and using the personal license, BTW? Definitely not.
- TeMPOraL 4y ago
  > Are large corps really stopping people from buying Copilot on their own and using the personal license, BTW? Definitely not. I would imagine so, just because of the EULA difference. Personally I never used and wouldn't dare to use Copilot at work, specifically out of concern for leaking company IP. (EDIT: That, and exports control. Regulations governing what can be sold to who around the world are complex, and come with huge fines and prison sentences for non-compliance. Large corporations take this very seriously. For software devs this, in practice, means that someone will be going over the dependency trees of your projects with a fine-tooth comb. I'm sure exports control people will be interested in your use of Copilot, though what they'd think of it I am not sure.) My experiences with personal licenses in two different corporate environments so far were: - A large multinational - they had an internal "app store" through which you could request specific software products. Licensing issues were handled behind the scenes and invisible to the user. If the software required a one-time payment or a paid subscription, you were informed how much money will be charged to what cost centre, and how often (in less corporate language: how much $ will be deducted from your salary, and when). I never tried to run software on personal licenses while there, but if I did, I imagine it would've been flagged by the same auditing system that occasionally pestered me about old JRE versions that need to be uninstalled. - A mid-sized manufacturer with highly corporate culture - they had IT install software to do automated auditing, and flagged any unauthorized software being run. They made a huge stink about people using unlicensed IrfanView. I actually bought an IrfanView license for my work machine using my own money, just so I could keep telling IT to tell whoever was driving those audits to leave me alone, as the license explicitly allowed using the software in commercial / corporate contexts. They weren't happy, but they also didn't tell me to remove it, so ¯\_(ツ)_/¯ - but had I asked, they'd just say "no".

icelancer 4y ago

I worked for a billion dollar company prior to running my own. >> Try doing that x100,000, every month. It gets annoying fast We didn't. Accounting did. Our company had a reimbursements-only policy, no corp cards. It was great, especially those of us who flew a lot and banked tons of airline, hotel, and credit card points. The other stuff, sure. Doubling the price? I don't buy it. Are large corps really stopping people from buying Copilot on their own and using the personal license, BTW? Definitely not.

TeMPOraL 4y ago
> Are large corps really stopping people from buying Copilot on their own and using the personal license, BTW? Definitely not. I would imagine so, just because of the EULA difference. Personally I never used and wouldn't dare to use Copilot at work, specifically out of concern for leaking company IP. (EDIT: That, and exports control. Regulations governing what can be sold to who around the world are complex, and come with huge fines and prison sentences for non-compliance. Large corporations take this very seriously. For software devs this, in practice, means that someone will be going over the dependency trees of your projects with a fine-tooth comb. I'm sure exports control people will be interested in your use of Copilot, though what they'd think of it I am not sure.) My experiences with personal licenses in two different corporate environments so far were: - A large multinational - they had an internal "app store" through which you could request specific software products. Licensing issues were handled behind the scenes and invisible to the user. If the software required a one-time payment or a paid subscription, you were informed how much money will be charged to what cost centre, and how often (in less corporate language: how much $ will be deducted from your salary, and when). I never tried to run software on personal licenses while there, but if I did, I imagine it would've been flagged by the same auditing system that occasionally pestered me about old JRE versions that need to be uninstalled. - A mid-sized manufacturer with highly corporate culture - they had IT install software to do automated auditing, and flagged any unauthorized software being run. They made a huge stink about people using unlicensed IrfanView. I actually bought an IrfanView license for my work machine using my own money, just so I could keep telling IT to tell whoever was driving those audits to leave me alone, as the license explicitly allowed using the software in commercial / corporate contexts. They weren't happy, but they also didn't tell me to remove it, so ¯\_(ツ)_/¯ - but had I asked, they'd just say "no".