r/programming • • Oct 24 '17

Next Visual Studio Code update will bring blue icon back

https://code.visualstudio.com/blogs/2017/10/24/theicon
2.0k Upvotes

280 comments sorted by

View all comments

Show parent comments

5

u/jugalator Oct 25 '17 edited Oct 25 '17

It's crazy to me how Apple with the budget of a fucking nation can't properly QA control an IDE for stability as well as UX. :| One that is essential to their mobile platform, in turn their most essential platform bar none. It's weird because Apple ought to be eating their own dogfood with Xcode as well, like Microsoft has done with Visual Studio. Xcode ought to be market leading, something developers dream of working with and hate working on competing platforms after having used it.

It has to be an organizational issue where they either don't even realize the problem (unlikely), how to best solve it, or how to communicate it with management, or bureaucracy leading to glacial decisions even if they realize the problem (I know at least Microsoft of old had this problem). A human rather than a financial issue.

0

u/aazav Oct 26 '17 edited Oct 26 '17

I was Macromedia's (now Adobe) first QA Architect before I was a developer.

How this team treats developers as their beta team and then asks us to report bugs into a closed system after we lose time because their stuff does not work clearly tells me that the Director of the team only wants his $50,000 bonus every time the product ships a major release.

Well, that and ex Xcode team members who were tired of the bullshit.

We have more animated bullshit - that we have to beg to ask them to let us turn off - than actual well designed features that solve our problems.

Honestly. Take this problem example. We have storyboards that are all the scenes and UI flow in one file, when a TEAM is expected to be editing multiple screens at once. Git conflicts are expected. Honestly, I delete the top level view of all scenes and replace it with an XIB that is the SAME NAME as the view controller on the scene. Apple's UIViewController docs have said since at least 2009 that they will search for a nib or XIB that is the same name as the View Controller of the scene if the top level view is missing or nil!!! Really!

Apple had a solution RIGHT THERE. Express storyboards as 1 file for the overview of the structure and skeleton of the scenes and use a separate XIB for each scene's top level view. This fixes SO MANY merge issues and if it doesn't, it limits the scope of the problem to ONE FILE that only deals with that screen while leaving the entire rest of the storyboard nor fucked up. It's fucking simple. It's following their own damn documentation in the header files!

I remember wasting days on XIB merge conflict issues because of this.

The simple fact that when the iOS color scheme changed from recognizable items to abstract minimalist meaningless crap with a color scheme of glaring pure white against glaring painful pastel light blue and that the executive staff thought that this was a GOOD IDEA speaks volumes about what Apple has lost. It has lost its common sense.