I’ve always wondered: how does it feel to be an #Apple #macOS #dev?
You can’t isolate yourself from the ‘official’ #bug reports, the ‘unofficial’, but vocal and public grudges on Twitter, about the character / emojis palette random misbehavior since, when, 2014?
Or can you? 🤔
Each morning, you enter the magnificent ring-office of a company making ≈100 BILLION USD of income YEARLY… sit down in a super-ergonomic #office chair in front of a decked-out, all in-house, state-of-the-art #ARM hardware,
open a rather impressive suite of dev tools and languages like #Swift… and… the bug (and public outrage) persists.
The Music.app loses in functionality with each iteration (like, hide tracks by keyword?!), your users can’t listen to the audiobooks playing fine in Books.app on their fancy #AppleWatch,
the Finder.app still pales in comparison to #MacOS Classic spatial awareness.
How do feel? OK? Or #TimCook’s We’re So Excited™? Or do you Think Indifferent™?
Apple Music on #MacOS? A perfect illustration of Apple’s software products today. How anyone can ship code this bad, year in, year out, is beyond my comprehension.
I mean, really, if you’re afraid to start #programming… please don’t be. Why? Because I’m 90% confident you’ll write better code with #Apple’s own APIs’ in #Swift, than people paid x20 your current salary.
youtube.com/watch?v=gE8Zik…
The silent swoosh of a #swift slicing through the evening stillness at a 110 km/h and past my #Paris window… #SoundEngineer bliss!
| TWEETS | CATEGORIES | ARCHIVES | SEARCH | ABOUT PROSE |
TIP: To print images, enable “Print backgrounds” in your browser preferences.