3 ms·
Microsoft hasn't had any problems with their development tools that support rather archaic languages. The problem is solvable; it's just that making a decent d
by kstenerud 15y ago
Microsoft hasn't had any problems with their development tools that support rather archaic languages.
The problem is solvable; it's just that making a decent developer product is not a priority at Apple. Provisioning is another example of terrible UI. And then there's their crappy command line/scripting support (for integration into a CI server), and their horrible developer portal web interface. The entire developer UI and usability experience is downright embarrassing. And to cap it off you have the typical Apple unhelpful or misleading error messages, including the most common and my personal favorite "An unknown error has occurred".
Ugh... my blood is boiling already, and I still have another 10 hours today with this shitty tool to look forward to...
- frou_dh 15y agoI used VS up to VS2008 and didn't find it for C++ particularly good either. The IntelliSense didn't work half the time and, apart from the debugger, about the only thing I used was Go-To-Definition/Declaration. The C# context was enormously more helpful and reliable.