3 ms·
> The problem I see with vendor lock-in is when, after you're locked, the service provider exploit this to change their terms (price and/or else) in a dispropor
by pritambaral 5y ago
> The problem I see with vendor lock-in is when, after you're locked, the service provider exploit this to change their terms (price and/or else) in a disproportionate and unjustifiable way against your initial interests in the service.
> This never happened with AWS, to my knowledge (please correct if I'm wrong). Everyone knew the price when they subscribed. Little changed afterwards. AWS was able to meet a demand with quality enough products in an acceptable price to whoever decided to buy.
Vendor lock-in does not require any changes to terms, price, or any part of the service or product provided. In most classically studied cases of vendor lock-in (e.g., Microsoft Windows and Office binary formats, VHS vs. Beta), everyone knew the lack of interoperability when they bought the service/good, and nothing changed afterwards. That didn't stop those cases from becoming "vendor lock-in".
- rmbyrro 5y agoI totally agree that lock-in is there. What I'm disputing is that AWS has exploited it maliciously to screw their customers. More specifically, this statement: > AWS was fucking everyone on egress price and nobody could do anything about it I disagree because AWS has been transparent with their prices since day one. Everyone who subscribed was aware of how much it cost. AWS didn't screw anyone by increasing prices after they were locked-in.
- pritambaral 5y agoGood, we're in agreement.