EEE refers to formats and later standards, where an MS product would Embrace a format/standard (e.g. Lotus 1-2-3's macros or HTML) so that people who use compet

EEE refers to formats and later standards, where an MS product would Embrace a format/standard (e.g. Lotus 1-2-3's macros or HTML) so that people who use competitor products will also be able to use their data with the MS product and then Extend it so that people will come to rely on MS-specific extensions - the Extinguish part comes passively from competitors not being able to keep up with Microsoft's changes, Microsoft doesn't actively try to extinguish something (otherwise they'd do that at the beginning) but it happens from people switching to their stuff. Obviously for this to work it needs two elements: 1. A format or standard that multiple vendors provide and Microsoft implements 2. The other vendors being unable to keep up with any Microsoft extensions None of the above apply to GitHub. The first part could apply to Git itself, but Microsoft has nothing to gain by doing that as the second part would be very difficult. EEE worked largely because Microsoft's competitors were companies with limited resources and programmers, but it doesn't work when any programmer and company can help keep up with them - see how they failed to apply it with HTML despite trying very hard. Also EEE really relies on network effects (the last E comes because people flock to MS products) and they already have a better network effect with GitHub's social aspect, they do not need to try and manufacture one.