4 ms·
Going to be interesting seeing how they will figure out where to draw the line (in legal terms) between testing and production. Would health checks be considere
by oolongCat 10y ago
Going to be interesting seeing how they will figure out where to draw the line (in legal terms) between testing and production. Would health checks be considered as testing the system or production type work?
- phire 10y agoA simple test of "Can the intended end users access the system" would work. Would also be a great motivation for developers to not test things in production, as it's cheaper to test them in the development/testing environment.
- seanp2k2 10y agoHow can you accurately measure that via software though? What differentiates a developer from a user or a customer? IMO these are hard problems to solve and problems which are not worth the engineering effort to attempt solving.
- phire 10y agoIt's not a software issue, the licensee has access to the source code and can modify it in anyway they want, including removing any software-enforced licencing restrictions. It's the responsibility of the licensee to make sure they are in compliance with the licensing terms (buy enough licenses to cover the number of CPU cores they are running in production), otherwise the copyright holder will sue them. This idea of licencee self-compliance is not an innovative concept, it's how most licensing in large enterprise companies already works (and that's where this license is targeted), the company checks how many copies of the software they are running and pay that much. It's not quite an honer system. Companies conduct regular audits (done by an external company) to prove they have everything licensed correctly.