Live data from Hacker News

Reverse Engineering MacOS High Sierra Supplemental Update

cocoaengineering.com

91–100 of 135 posts

Re: Reverse Engineering MacOS High Sierra Supplemental Update

#91
post #82

Earlier quoted context omitted.

To be fair, it doesn't need to be spent in the US.

Yeah, they could build a giant Apple QA building somewhere in the EU and just have them file radars all day.

Not so far fetched ... http://uk.businessinsider.com/apples-growing-irish-empire-in...

Re: Reverse Engineering MacOS High Sierra Supplemental Update

#92
post #16

It's pretty insane this sort of bug either passed or didn't even go through code review and testing at Apple, a company which has approximately infinite resources and whose marketing pitch is making high-quality products. I loved Apple products and still do, but as both a user of and a developer for their systems, I feel the quality has been steadily going downhill the last few years.

> a company which has approximately infinite resources

The classic Apple problem is they they compatibility have much less corporate employees than other tech companies and they're stretched too thin, despite all their money.

Re: Reverse Engineering MacOS High Sierra Supplemental Update

#93
post #71

Earlier quoted context omitted.

I think you might be looking at the past through rose-colored glasses. Apple's always had horrible show-stopping bugs, in every single OS X / macOS release[1], from when simple operations like updating iTunes or enabling the OS's Guest Mode might delete your home directories, to this latest failure. I suspect one reason is that they like one-person teams so much. I like one-person projects too! But there is always pa…

> EDIT: except maybe Mac OS X 10.6? Does anybody remember any critical bugs in that one? I think that might be the unicorn. Google "10.6.0 font problems", this caused a major headache at my work

Also caused major issues for the rare users who had antivirus software installed.

Re: Reverse Engineering MacOS High Sierra Supplemental Update

#95

Earlier quoted context omitted.

I'm not sure why you say "has become". In the circles I've been it has been common practice to wait for the .2(but minimum .1) release before it goes onto real work machines. The early Mac OS X releases were even worse. Even if for some reason the OS itself was fine by itself, they almost always broke compat with a bunch of 3rd party applications. EDIT: typo

Exactly. "Never buy the first version of any new Apple product", whether hardware or OS, has been well-known for at least 10 years: https://www.engadget.com/2006/06/03/why-first-generation-app... (That said, I've found my first-gen Apple Watch to be a great product. First-gen iPad is a paperweight though...)

Never buy the first version of any new product

Re: Reverse Engineering MacOS High Sierra Supplemental Update

#96
post #62

I don't like the old style NSDictionary way of packing information that so many API's use. First of all they're lacking an enforcement for the type of the value they're expecting (sometimes leading to crashes if you get them wrong) and the discoverability of possibilities is less easy than with a struct or object. Still, passing in password twice would still be a possible mistake. The only thing that would help in my…

Yea I was thinking about this too! We can talk all day about static typing vs productivity but if they had a basic string type called PasswordHint and Password then maybe (maybe!) this wouldn’t happen.

I'd leave passwordHint as a string; but password... That might be an interesting type. Particularly if it zeroed out memory as a freebie in the destructor. Actually that was my take-away from this article, the "maybe in MY projects I should wrap passwords in a special type to stop me typo-ing the raw password to output."

Re: Reverse Engineering MacOS High Sierra Supplemental Update

#97
post #71
post #16

It's pretty insane this sort of bug either passed or didn't even go through code review and testing at Apple, a company which has approximately infinite resources and whose marketing pitch is making high-quality products. I loved Apple products and still do, but as both a user of and a developer for their systems, I feel the quality has been steadily going downhill the last few years.

I think you might be looking at the past through rose-colored glasses. Apple's always had horrible show-stopping bugs, in every single OS X / macOS release[1], from when simple operations like updating iTunes or enabling the OS's Guest Mode might delete your home directories, to this latest failure. I suspect one reason is that they like one-person teams so much. I like one-person projects too! But there is always pa…

except maybe Mac OS X 10.6

Snow Leopard. What a wonderful high-point in Desktop OSes that was. Seriously considering rolling back one or two of my old computers, even just to have a living breathing reference-point.

Re: Reverse Engineering MacOS High Sierra Supplemental Update

#98
post #85

Earlier quoted context omitted.

> can only be used as leverage for borrowing rather than being spent directly Or , they could pay the tax and use the money (crazy idea I know).

If they thought of doing that they could and probably should be sued. CEOs have a fiduciary duty meaning they are legally implored to do what is best for the company and bringing money back at a 40% tax is not in the financial interest of the company.

Any judge would rule that following the law of the land is not against the interest of the company.

Re: Reverse Engineering MacOS High Sierra Supplemental Update

#99

Installing a new Mac OS on a machine you care for has become an absolute no-go area. I wait for at least half a year and then only install in a place that I can trash in case I still see problems.

It's not only Mac OS, that can be said about pretty much all software. As a developer, I always try to avoid fresh software and wait some time while it settles, unless it's a security update.

Re: Reverse Engineering MacOS High Sierra Supplemental Update

#100
post #85
post #53

Earlier quoted context omitted.

> a company which has approximately infinite resources I believe the leadership insists in keeping up a pretension that this is not actually the case. To be fair, most of that "infinity" is sitting in offshore bank accounts and can only be used as leverage for borrowing rather than being spent directly.

> can only be used as leverage for borrowing rather than being spent directly Or , they could pay the tax and use the money (crazy idea I know).

> Or , they could pay the tax and use the money (crazy idea I know).

Or just use the super low interest rates and borrow against the money, which is exactly what they have been doing.

Post reply on HN