Vendor Lock In - ce este, cum îl putem evita?

[anon30058683 (Ex. Dakull)]

@flavius cred ca am venit cu argumente clare in alt thread ca folosesti incorect anti-corruption layer:

What I Learned from Working in Failed Platforms

@flavius Anti-Corruption Layer pentru un framework/librarie? really? Direct din DDD de Evans: a) argumentul principal ce reiese de mai jos este ca utilitatea pattern-ului este pt. legacy systems When a new system is being built that must have a large interface with another, the difficulty of relating the two models can eventually overwhelm the intent of the new model altogether, causing it to be modified to resemble the other system’s model, in an ad hoc fashion. The models of legacy system…

tl;dr:

vendor lock-in != legacy code

EDIT:

on topic - cum ziceam depinde de context:

• Delegation - cam ce s-a prezentat deja
• Adapter: JavaScript Adapter Design Pattern
• Facade: JavaScript Facade Design Pattern
• Factory
• if you want to go nuts: Coming Soon – Alistair Cockburn
  etc.

EDIT2:

vendor lock-in - in final este doar a highly leaky abstraction avand in vedere ca toate exemplele au in spate cate un anume pattern si sunt dependente de context. Numarul de exceptii este atat de mare incat expresia in sine este vaporware.