271–280 of 372 posts
Earlier quoted context omitted.
Engineers couldn't see the bug because the code was displayed in Narrow Light font weight, color grey
Their only mistake was not making it an ever lighter grey.
How did Disk Utility.app go from being one of the great built-in OS X utilities to the embarrassing amateurish shit show that it is today? Perhaps the same people responsible for the file system engineering are also responsible for developing this user-facing application. They might excel at low level system engineering, but they are utterly unqualified to develop a high level GUI application. Spend 5 minutes with th…
The iOS-using products are Apple's cash cow. It does make sense that they'd prioritize working on iOS. However, what doesn't make sense is that Apple certainly has enough resources to work on both OSes. It's not like they don't have enough money to hire good developers.
That is the complaint, however. It makes some sense, except that Apple could easily afford to invest in both macOS and iOS.
Earlier quoted context omitted.
I have a Dell Precision laptop running Linux at home and a MacBook Pro from work. On a weekly basis, the Mac won't wake from sleep and requires a hard reboot. The Time Machine backups get corrupted at least every other month and require a full backup from scratch. Sometimes the audio just quits working when I wake from sleep. The App Store is some horribly wrapped, unresponsive web app. Disk Utility is useless. Etc,…
My mid-2011 MacBook Air with 4 GB memory has been running really well. Occasionally Safari (the Metal version in High Sierra) gets slow, but it's still faster than Chrome. I've been using it for general casual computing and machine learning development with Jupyter Notebooks and haven't run into anything that would make me want to switch. I'll probably upgrade to a 2018 MacBook Pro with 8 GB memory when those come ou…
Must be working with very small datasets given so little RAM.
Earlier quoted context omitted.
Is there a reason that the macOS CLI can't be intended as a general power-user feature, not just a developer feature? Consider: Terminal.app comes with macOS, not with Xcode. If the BSD environment was just there for developers, would this be true? Today's Microsoft seems to increasingly think sysadmins would rather use PowerShell than MMC snap-ins; I'm inclined to think that today's Apple is similar. And there's not…
> And there's nothing inherently hard about CLI interfaces; "regular people" used MS-DOS PCs for ~two decades. CLIs are opaque by definition. With a GUI you can click around menus until you find what you're looking for; with a CLI you can't even begin unless you already know what you're doing. Man pages are no help to newbies; they're either uselessly terse, impenetrably jargon-packed, or both. It's probably possible…
Earlier quoted context omitted.
My mid-2011 MacBook Air with 4 GB memory has been running really well. Occasionally Safari (the Metal version in High Sierra) gets slow, but it's still faster than Chrome. I've been using it for general casual computing and machine learning development with Jupyter Notebooks and haven't run into anything that would make me want to switch. I'll probably upgrade to a 2018 MacBook Pro with 8 GB memory when those come ou…
> I've been using it for general casual computing and machine learning development with Jupyter Notebooks Must be working with very small datasets given so little RAM.
Earlier quoted context omitted.
There have been a few cases like this. Presumably the original was created/maintained by just one person, they move on, and then when the next person comes along they decide it's easier to re-write than modify the old code. But they don't have sufficient time and the new version is inferior to the old. Bear in mind the old version did need to be updated (new CoreStorage features, has to handle Fusion drives, now APFS…
1. dont have the same depth of dev talent they used to 2. mgmt that isnt as sensitive-to and focussed-on quality. (this is 75% speculation on my part and 25% confirmed by conversations with 2 ex-apple engineers.)
You know the sort of thing that happens to developers: Every. Single. Day.
Earlier quoted context omitted.
> And there's nothing inherently hard about CLI interfaces; "regular people" used MS-DOS PCs for ~two decades. CLIs are opaque by definition. With a GUI you can click around menus until you find what you're looking for; with a CLI you can't even begin unless you already know what you're doing. Man pages are no help to newbies; they're either uselessly terse, impenetrably jargon-packed, or both. It's probably possible…
I would argue that small command-line tools "the unix way" combined with a competently written -h help page is quite discoverable. Maybe not for a general computer newbie, but certainly for people used to /other/ cli tools.
In contrast, even features in pretty poor GUI apps are by default generally discoverable.
Earlier quoted context omitted.
1. dont have the same depth of dev talent they used to 2. mgmt that isnt as sensitive-to and focussed-on quality. (this is 75% speculation on my part and 25% confirmed by conversations with 2 ex-apple engineers.)
I've always thought of Apple as one of those black holes that absorbs devs: people land there, and then—if they can hack the culture—tend to stay for their careers. Is this not true any more? Where does ex-Apple dev talent tend to go? (Microsoft? Indie app development?)
I know lots of people who have spent their entire careers there because the work is challenging and interesting. I also know teams that handle anonymous backend infrastructure e.g. AppleID or ADC where there was higher turnover.
No different to any other company.
Why isn't this a 10.13.1 update?
Earlier quoted context omitted.
I've always thought of Apple as one of those black holes that absorbs devs: people land there, and then—if they can hack the culture—tend to stay for their careers. Is this not true any more? Where does ex-Apple dev talent tend to go? (Microsoft? Indie app development?)
Honestly all the great apple devs from the early 2ks have either moved into consulting or entrepreneurial activity or, more likely and worryingly, they've been promoted into management roles at apple where they're managing a team of engineers not quite as good as they were. You see this everywhere, at every company. That's my guess.