4 ms·

And I have to say that the Microsoft team was amazing. They were very supportive, and helpful, and it was clear that they really wanted VC++ 2015 to be as good

by stinos 11y ago

And I have to say that the Microsoft team was amazing. They were very supportive, and helpful, and it was clear that they really wanted VC++ 2015 to be as good as possible Rather anecdotical of course, but I had the same impression. File a proper bug report and you get a reply in the next couple of days, typically starting with thanks for the excellent bug report ... will try to get the fix in the next update. Found a couple of bugs in VS2012 and VS2013 and they were resolved in either the next update or in the next version. Practically speaking it usually took somwhere between 1 - 3 months, which isn't too bad all things considered. Like, I've also had much worse experiences with some competitors where I'd file a report including a possible fix (something like 'change <= to <' in soure x line y), and 6 months later there even hasn't ben a reply let alone a fix.. Anyway with VS2015 it even seems like they cranked it up a notch beacuse the bugs I encountered already had a fix in the update I didn't manage to install yet :]

RyJones 11y ago
Apple, by comparison, is a black hole. I filed a bug in July 2014 [0] against xcodebuild that we still get bit by every once in a while. Never got a response. The repro is trivial. [0] http://blog.ryjones.org/2015/01/06/xcode-is-killing-me/ http://blog.ryjones.org/2015/01/06/xcode-is-killing-me/
- nikanj 11y ago
  I think whoever holds the platform with the biggest earning potential has the worst bug situation. I remember MS in the last decade, with their "reinstall and don't call us back"-support attitude. Now that iOS is the key to unicorn valuations, MS has had to fix their developer support.
jobu 11y ago
> Like, I've also had much worse experiences with some competitors where I'd file a report including a possible fix (something like 'change <= to <' in soure x line y), and 6 months later there even hasn't ben a reply let alone a fix. cough Apple cough ... A few years ago I reported an issue for iOS that _never_ got a response. When I made it to WWDC 6 months after reporting it, I went the support session and ended up running into the guy that wrote the bug. He was aware of the issue, it had been reported a few times, and he gave me a workaround until they released the fix. It was nice to finally get a resolution, but the whole process was seriously fucked up. After the fix was released in the next version of iOS they closed my bug report without a single comment.
- Alupis 11y ago
  Sounds like they're using an internal tracker not publically accessible... making the public one more of a pony show than anything. Sadly, this is common for a lot of places (they're afraid internal discussions would get negative attention if made public in some tracker).
  - jobu 11y ago
    > they're afraid internal discussions would get negative attention if made public in some tracker That's understandable for a company like Apple. It just pissed me off that they had a workaround, possibly for months, and never bothered to respond to my report.
  - AceJohnny2 11y ago
    > (they're afraid internal discussions would get negative attention if made public in some tracker) Mostly, they're afraid internal discussion would leak super-seekrit info about their product pipeline. You know how anal they can be about their product announcements. I mean, they get worked up about leaks like this: http://arstechnica.com/apple/2016/03/unreleased-12-inch-macbook-early-2016-shows-up-in-os-x-server-update/ http://arstechnica.com/apple/2016/03/unreleased-12-inch-macb...
  - dyoo1979 11y ago
    You may be underestimating the overwhelming power of spam. That is, you're attributing a fear of negative attention. That might be true, but I suspect the concern has more to do with abuse. Don't underestimate the power of abusive users who have disproportionate power.
- VonGuard 11y ago
  Back in the day, you could escalate a bug to the next patch by emailing steve@mac.com claiming you lost work, or can't get something done. I did this twice, and got a patch both times. Once, they literally patched iMovie over a weekend after I emailed Steve. I'd bet the teams were quite unhappy...
  - 11y ago

by stinos 11y ago

RyJones 11y ago

Apple, by comparison, is a black hole. I filed a bug in July 2014 [0] against xcodebuild that we still get bit by every once in a while. Never got a response. The repro is trivial. [0] http://blog.ryjones.org/2015/01/06/xcode-is-killing-me/ http://blog.ryjones.org/2015/01/06/xcode-is-killing-me/

nikanj 11y ago
I think whoever holds the platform with the biggest earning potential has the worst bug situation. I remember MS in the last decade, with their "reinstall and don't call us back"-support attitude. Now that iOS is the key to unicorn valuations, MS has had to fix their developer support.

jobu 11y ago

> Like, I've also had much worse experiences with some competitors where I'd file a report including a possible fix (something like 'change <= to <' in soure x line y), and 6 months later there even hasn't ben a reply let alone a fix. cough Apple cough ... A few years ago I reported an issue for iOS that _never_ got a response. When I made it to WWDC 6 months after reporting it, I went the support session and ended up running into the guy that wrote the bug. He was aware of the issue, it had been reported a few times, and he gave me a workaround until they released the fix. It was nice to finally get a resolution, but the whole process was seriously fucked up. After the fix was released in the next version of iOS they closed my bug report without a single comment.

Alupis 11y ago
Sounds like they're using an internal tracker not publically accessible... making the public one more of a pony show than anything. Sadly, this is common for a lot of places (they're afraid internal discussions would get negative attention if made public in some tracker).
- jobu 11y ago
  > they're afraid internal discussions would get negative attention if made public in some tracker That's understandable for a company like Apple. It just pissed me off that they had a workaround, possibly for months, and never bothered to respond to my report.
- AceJohnny2 11y ago
  > (they're afraid internal discussions would get negative attention if made public in some tracker) Mostly, they're afraid internal discussion would leak super-seekrit info about their product pipeline. You know how anal they can be about their product announcements. I mean, they get worked up about leaks like this: http://arstechnica.com/apple/2016/03/unreleased-12-inch-macbook-early-2016-shows-up-in-os-x-server-update/ http://arstechnica.com/apple/2016/03/unreleased-12-inch-macb...
- dyoo1979 11y ago
  You may be underestimating the overwhelming power of spam. That is, you're attributing a fear of negative attention. That might be true, but I suspect the concern has more to do with abuse. Don't underestimate the power of abusive users who have disproportionate power.
VonGuard 11y ago
Back in the day, you could escalate a bug to the next patch by emailing steve@mac.com claiming you lost work, or can't get something done. I did this twice, and got a patch both times. Once, they literally patched iMovie over a weekend after I emailed Steve. I'd bet the teams were quite unhappy...
- 11y ago