|
|
|
|
|
|
by berdario
4245 days ago
|
|
|
I'm afraid to say that I haven't had a positive experience either, but I was just interested in CoApp out of curiosity: I tried to see if it was doable to use it to package pure Python (or other interpreters) libraries. Obviously it was not ready yet, but I wasn't really let down: I seldom use Windows, so I don't have any real need for it, and my perception was that with some more months/years it would get there. But CoApp and OneGet are worthwhile endeavors, so I'm cautiously optimistic that they'll eventually build something that can make software installation on Windows less painful PS: uh, I just realized that you're a Microsoft developer as well (just like Garret Serack)... is it so difficult to get hold of him even inside the same company? (I don't know... maybe you're actually on different sides of the ocean, and this would make the matter quite a bit more complicated) |
|
|
I hope my criticisms of CoApp / Native Nuget did not transfer to a criticism of OneGet - my suspicion is that CoApp is abandoned simply because Garrett doesn't have time to both work one CoApp and OneGet. (It's also possible that OneGet deprecates CoApp.)
Certainly I understand all these problems - as you note, I am a Microsoftie as well, so I'm very familiar with having too much to do and not enough time to do it - and I've abandoned a few projects myself. But I'm not happy about that.
As for your question about being at Microsoft: I'm not across the ocean but I do happen to be on the other side of the country. I suspect I could have gotten a reply if I sent an email from my microsoft.com account (even if that reply was "sorry, don't have time") but I sort of hate throwing that around since it feels unfair to the rest of the community trying to use it.