Apple definitely seems to have a larger software surface area than hardware, where they tend to discontinue more frequently. Keep in mind the companies Godin compares it to are focused on web services and only have one user-facing product. It's an unfair comparison. Apple provides some of the best developer tools and APIs. An essential software suite that just works is what I'm looking for, and for the most part it's delivered.
"Once you know about all the ways that skimmer thieves are coming up with to fleece the banks and consumers, it’s difficult not to go through life seeing every ATM as a potential zombie threat — banging and pulling on the poor machines and half expecting half hoping parts to come unglued. I’m always disappointed, but it hasn’t stopped me all the same."
And I currently practice this:
"Lastly but most importantly, covering the PIN pad with your hand defeats the hidden camera from capturing your PIN — and hidden cameras are used on the vast majority of the more than three dozen ATM skimming incidents that I’ve covered here."
If you look at NSHipster and other sources in the iOS community converting their code samples to Swift only months after its initial release in 2014, it says something about the pent-up demand for a nicer language than ObjC. Plus Swift seems to be designed for ObjC devs to have an easy transition, although slightly less dynamic (and unsafe).
Demand for iOS development could be tapering due to app market saturation; saw a post recently around here about that.
I wonder how restaurants factor into that, especially fast food. Any place that preemptively prepares food is very likely to waste a lot of it. Having worked at an am/pm for my first job, I was blown away by how much food is thrown out after 3 hrs from when it was cooked.
- No ability to store the tab size setting. While appending '?ts=2' to the url is ok, it's not convenient and usable on a daily basis. The same for omitting whitespace changes in a diff / pr ('?ws=1').
- No ability to step through history on a single file while in blob view, or blame view. In blame view, the commit link goes to the commit, not the blame of the file at that commit.
- Agree with OP that notifications need to be grouped / summarized better. Perhaps expandable summary items per repo per type. This is mostly useful for private, work-related repos. Pulse and notifications are basically the same thing.
- Stars cannot be tagged. This makes managing hundreds of stars difficult. There's apps like Astral, but even those are lacking.