3 ms·

Of course that's "extending." It's a very clever attack on open source generally.

• Dylan16807 4y ago
  But it's not open source specific. Not in creation and definitely not in use. And the idea of the extend of EEE applying to all of open source at once, the way you could apply to a product or a standard or a protocol, doesn't really make sense.
  • jrm4 4y ago
    You're thinking way too narrowly. EEE doesn't require a specific plan -- if you look at the history of Microsoft engaging in EEE, you can see it's been much more experimental than you're suggesting. It's basically Microsoft saying "Here is a thing that looks like it might in some way eventually be a threat to our business model and/or we can make some money off of it -- let's get our hooks in now and see what happens, we have the money to do it."
    • Dylan16807 4y ago
      But again, copilot does not get their hooks into open source any more than it gets their hooks into code in general. And they're not doing EEE against "code". EEE doesn't need a specific plan but it does need some kind of target standard. Getting into an emerging market, without specific kinds of integration or malfeasance, is just competition.