3 ms·

This isn't a big deal really. However Microsoft wants the real secret sauce. They either want A: Apple to build a client in Windows with C#. Or possibly B: want

This isn't a big deal really. However Microsoft wants the real secret sauce. They either want A: Apple to build a client in Windows with C#. Or possibly B: wants to able to allow swift compilation on Windows thus opening the door wide open for app ecosystem. You think probably not but then again WSL.

dpark 8y ago
Microsoft has literally tens of thousands of engineers capable of building the client for Windows if Apple will let them. I am certain that no one on this integration project cares whether Apple actually does the work, only whether they allow it. Disclosure: Microsoft employee, but nowhere near this group.
- alexkavon 8y ago
  That's essentially what I'm saying. There is a longer game at play. I only state they probably want Apple to do it because they helped Apple port iTunes to the Windows Store. It's not a play for iMessage but a longer play.
  - dpark 8y ago
    I’m not sure what the longer play is or how it ties into Apple building in C# or Swift on Windows, neither of which are a prerequisite to iMessage on Windows.
    - alexkavon 8y ago
      Well, if Apple builds an app in C# then they would probably want to use their OS to do so. In order to do that they would need Visual Studio for Mac which would allow them to work with Apple to improve those tools and open doors for developing C# applications on MacOS as well as compiling those Applications for MacOS. If Apple were to write a client in Swift or ObjC then it would do the reverse and potentially open up applications to be compiled for and run on Windows. This allowing easier porting of apps from MacOS to Windows and helping eliminate their "lack of apps in the Windows store" problem. Cross functionality is Microsoft's current game. How many different ways they can achieve it is up to your imagination.
      - dpark 8y ago
        There’s pretty much zero chance that any of those build scenarios would happen. This is a hypothetical app for Windows, so it would be built on Windows, and it would use Windows tooling. No Swift, no Objective-C, no macOS. There is no reason that Apple would drag their entire ecosystem along to build this app, if they even built it themselves.
        alexkavon 8y ago
        eye roll
- BrentOzar 8y ago
  > Microsoft has literally tens of thousands of engineers capable of building the client for Windows if Apple will let them. One word: Skype.

dpark 8y ago

Microsoft has literally tens of thousands of engineers capable of building the client for Windows if Apple will let them. I am certain that no one on this integration project cares whether Apple actually does the work, only whether they allow it. Disclosure: Microsoft employee, but nowhere near this group.

alexkavon 8y ago
That's essentially what I'm saying. There is a longer game at play. I only state they probably want Apple to do it because they helped Apple port iTunes to the Windows Store. It's not a play for iMessage but a longer play.
- dpark 8y ago
  I’m not sure what the longer play is or how it ties into Apple building in C# or Swift on Windows, neither of which are a prerequisite to iMessage on Windows.
  - alexkavon 8y ago
    Well, if Apple builds an app in C# then they would probably want to use their OS to do so. In order to do that they would need Visual Studio for Mac which would allow them to work with Apple to improve those tools and open doors for developing C# applications on MacOS as well as compiling those Applications for MacOS. If Apple were to write a client in Swift or ObjC then it would do the reverse and potentially open up applications to be compiled for and run on Windows. This allowing easier porting of apps from MacOS to Windows and helping eliminate their "lack of apps in the Windows store" problem. Cross functionality is Microsoft's current game. How many different ways they can achieve it is up to your imagination.
    - dpark 8y ago
      There’s pretty much zero chance that any of those build scenarios would happen. This is a hypothetical app for Windows, so it would be built on Windows, and it would use Windows tooling. No Swift, no Objective-C, no macOS. There is no reason that Apple would drag their entire ecosystem along to build this app, if they even built it themselves.
      - alexkavon 8y ago
        eye roll
BrentOzar 8y ago
> Microsoft has literally tens of thousands of engineers capable of building the client for Windows if Apple will let them. One word: Skype.