Live data from Hacker News

Broken

tyler.io

141–150 of 571 posts

Re: Broken

#141
post #99

All the nightmares are nightmares until they're not nightmares. Weird launch day bugs like the I bug on iOS 11 are distant memories. Yeah, these bugs are bad, but to me articles like this really feel a lot like a broken record. Every September and October, when the major releases come out, there are bugs. And then by the time you're on 10.xx.2 or iOS xx.1.3 a month later they're just a bad memory. If you don't want b…

Someone get Apple marketing on the phone. They need to adjust their keynote messaging to: “It’s our best desktop OS ever! Oh and one more thing, don’t use it yet, it’s pretty fucked and we’ll hopefully fix it in a few months. It’s on you if you want to do our unpaid QA. And now, it’s my pleasure to welcome Bono to the stage to demonstrate the new animoji!”

Re: Broken

#142
post #90

Earlier quoted context omitted.

This reminds me of the fascinating NYT story about the lead up to the original iPhone announcement event: https://www.nytimes.com/2013/10/06/magazine/and-then-steve-s... . A choice excerpt: > The iPhone could play a section of a song or a video, but it couldn’t play an entire clip reliably without crashing. It worked fine if you sent an e-mail and then surfed the Web. If you did those things in reverse, however, it m…

Indeed. Apple's MO for a LONG time has been, "The way things have always worked should always be rethought, and we've come up with a better way for you". Many Apple users on forums like this tend to be Apple apologists until they introduce that one change that's too much, and then it's all "Apple's lost their way!" when the reality is it's just Apple being Apple.

That’s not what the parent comment is saying at all.

Re: Broken

#143

> The final (well, first) Catalina release along with the outright awful public beta makes me think one thing. And that is Apple’s insistence on their annual, big-splash release cycle is fundamentally breaking engineering. I know I’m not privy to their internal decision making and that software features that depend on hardware releases and vice-versa are planned and timed years (if not half-decades) in advance, but I…

"big-splash release cycle is fundamentally breaking engineering"

I strongly prefer Apple ship functionality incrementally. No more big bang.

Especially be more cautious with new kits (core libraries). Just one or two end user facing features on some fraction of hardware. Then expand over time.

With Apple's installed base, it's an engineering marvel there's so little drama. But I want no drama, which means waiting a bit longer. Which is fine.

Source: Ecstatically happy Apple fanatic.

Re: Broken

#144

Things are so broken here at Apple. I joined about 4 years ago. I am awed by the fact that we manage to release any software at all, let alone functional software. The biggest problem is communication. No one fucking communicates. - No communication between orgs. Tons of bureaucratic tape to cut through just to get a hand on someone working on a different product - Barely any communication between teams. Literally ev…

I should note that most developers here really do care, and that’s probably why products can be released in the first place. You have to have really dedicated people willing to cut through the organizational bullshit to get things done.

All of the engineers I’ve met here are smart and innovative. Only if we could organize, things would be much better.

Re: Broken

#145

Earlier quoted context omitted.

Huh, does that work? I didn't realize that one could actually revert mid install. Let us know. (:

you can't. once it finishes downloading and reboots into the update screen you can't go back. Catalina seems to at least have broken the ability to create symlinks in the root folder. So no more `cd /htdocs` on my laptop.

I believe you "merely" need to disable SIP, then remount the root partition as read/write.

Re: Broken

#146
post #49
post #18

Earlier quoted context omitted.

How would you choose to handle it?

Maybe Apple could have gone through all the apps on their own App Store, built a whitelist out of the privileges that each of those apps effectively needs to do its job at all (not optional features, just the “makes the app more than a paperweight” feature-set), and shipped Catalina with said whitelist. For example, if, when you upgraded to Catalina, the App Store version of Alfred was already installed on disk, then…

> if there’s malware on the App Store, then they should probably solve that by removing the app from the App Store and deauthorizing the developer’s code-signing cert

Apple has been spectacularly poor at spotting bad apps on the Mac App Store.

Re: Broken

#147

Earlier quoted context omitted.

I work for a big software corp in SV with a yearly conference where we announce all of our products. Managers give zero shits about product quality as long as we deliver on time for the "big show". Bugs, future maintenance burden, and other shortcomings be damned because they'll probably be long gone after they get their promotion (and probably at another company rinsing and repeating) and by then, these issues becom…

Counterpoint: I've worked at SV unicorns that were not public, and did not intend to go public in the near term. And they had a similar "damn the torpedoes! full speed ahead!" attitude. So I think it is more pervasive than just Wall Street.

Everybody reads the same management books as Wall Street.

Re: Broken

#148
post #90

> The final (well, first) Catalina release along with the outright awful public beta makes me think one thing. And that is Apple’s insistence on their annual, big-splash release cycle is fundamentally breaking engineering. I know I’m not privy to their internal decision making and that software features that depend on hardware releases and vice-versa are planned and timed years (if not half-decades) in advance, but I…

This reminds me of the fascinating NYT story about the lead up to the original iPhone announcement event: https://www.nytimes.com/2013/10/06/magazine/and-then-steve-s... . A choice excerpt: > The iPhone could play a section of a song or a video, but it couldn’t play an entire clip reliably without crashing. It worked fine if you sent an e-mail and then surfed the Web. If you did those things in reverse, however, it m…

Great read! Thanks for sharing. Highly encourage anyone who is on the fence about reading the whole thing to go for it.

Steve, and others like him, do make me wonder. On the one hand, I work four days a week, never stay late at work, and live a good, steady life. But on the other hand, I see these super-stars, these drive-people-to-the-edge, sleep-on-shop-floor types, and see how much change and drive they create, it makes me start to think that maybe I should work _much_ harder. But then again, I quite like all this time I have to think on things. And of course, we don't get all the details about how this style of work _really_ affects home life; I'm sure we'd have much less respect for these super-stars if we knew they _all_ had screwed up lives away from work.

Re: Broken

#149
post #74
post #18

Earlier quoted context omitted.

How would you choose to handle it?

What about coalescing the lists of applications requiring specific permissions, for instance, and presenting that to the user at the end of the setup process in a more structured step? I'm imagining a list of "here are XYZ applications requesting location services access, pick which ones you don't want to give location access to" and then a list of "here are ABC apps that want microphone and camera access". It's not…

> The more "Apple" solution would be to just have sensible defaults (deny) and only prompt the user when the app in question wants to access that specific item (the way iOS implements it).

This is how it works; it’s just that macOS applications are not used to delaying authorization prompts to the appropriate time so they ask for it on startup.

Re: Broken

#150
post #60

Earlier quoted context omitted.

Well, I'm not famed for my user-orientated designs and thinking! But there are numerous ways this could be handled. A few off the top of my head: 1. Do nothing - leave things the way they were pre-Catalina 2. Default all apps installed pre-Catalina to "Allow", so you only get the prompt for newly installed apps 3. Make it configurable at the OS level, so you can set the default you want, and then tweak individual app…

Honestly, I just want an off switch for TCC. (It can be in the Terminal-only.) I'm kind of surprised there isn't one—Apple is usually pretty good about providing this stuff on macOS (at least relative to that other platform). Even with SIP turned off, there's no way to just blanket dismiss the dialogues. (Although, I'm sure without SIP someone could use code injection, but no one has, and given the amount of work it…

With SIP disabled, it might be possible to directly modify the TCC database…maybe someone can write a script to do this so it includes all your applications already.
Post reply on HN