Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Nasty macOS flaw is bricking MacBooks: Don't install this update

tomsguide.com

Post reply on HN
Print view View original

171–180 of 440 posts

Re: Nasty macOS flaw is bricking MacBooks: Don't install this update

#171

Post by qqssccfftt »

C19is20 wrote: post #142
sv9 wrote: post #67

I'm consistently amazed by HN's ability to take the most meaningless, inconsequential part of an article (the scroll behavior, the whitespace, the usage of the word "bricked"), and nitpick it to hell and back instead of actually discussing the article. Bravo.

> I'm consistently amazed by HN's ability to take the most meaningless, inconsequential part of an article (the scroll behavior, the whitespace, the usage of the word "bricked"), and nitpick it to hell and back instead of actually discussing the article. > Bravo. 'Bravi', or 'brave'(f) would be the plural of that.

> 'Bravi', or 'brave'(f) would be the plural of that.

I have never heard anyone but you say this ergo it is wrong.

Re: Nasty macOS flaw is bricking MacBooks: Don't install this update

#172

Post by sakisv »

I think that Apple should take advantage of the lockdowns and focus just on fixing things.

They don't need to ship anything new and they have the perfect excuse to focus on improving both their OS and their processes that allowed such flawed things to reach their users.

Re: Nasty macOS flaw is bricking MacBooks: Don't install this update

#173

Post by shimfish »

trevyn wrote: post #153
andrekandre wrote: post #123

Earlier quoted context omitted.

> Xcode 11.4 your probably not missing much, there are some serious regressings in that release, for example [0] [0] https://forums.swift.org/t/swift-5-2-struct-property-wrapper... (for me, cant make release builds because the compiler crashes... sigh...)

You’re missing the ability to connect to and debug on iOS 13.4 devices, I believe: https://forums.developer.apple.com/thread/130988 So now I’m stuck on 10.14.6 and iOS 13.3.1, one of which is not getting security updates. Really hoping Fuschia or someone steps up and displaces Apple.

I managed to get round this by copying Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport/13.4 from the latest Xcode.xib into my installed Xcode package.

I can now debug 13.4 devices on Xcode 11.3.

Re: Nasty macOS flaw is bricking MacBooks: Don't install this update

#174

Post by ironmagma »

j4yav wrote: post #161
gregmac wrote: post #45

Earlier quoted context omitted.

"Bricked" is relative, depending on your skill level. For some consumers, if recovery mode doesn't work that might be the end of line. However, there are more advanced users that can access the storage via another system and fix it there, hook up via serial port or JTAG and flash new firmware, or even desolder and replace chips. On the far other end of the spectrum, there's going to be people that consider "doesn't s…

Is the power system in your house bricked if you don't know how to reset the fuse? Is your car bricked if your battery dies and you need help to replace it? Maybe, but this sounds really strange to my ears. I think for me the difference between bricked and non bricked is the expense of the repair, and maybe if it's more than the value of the device. If the wiring in your house is all melted after lightning strike the…

It’s not just money but time, research, and ease. If you are in the desert with no cell connection and your car encounters a failure condition, even though you can pay to have it fixed, for all intents and purposes, to you it is bricked.

Re: Nasty macOS flaw is bricking MacBooks: Don't install this update

#175

Post by tinus_hn »

ObsoleteNerd wrote: post #4

It's not "bricked" if you can fix it in Recovery Mode. Still bad that it's happening, but the term "bricked" is thrown around so flippantly these days. If a piece of tech is bricked, it's not recoverable at all.

But how are they going to get the clicks?

Re: Nasty macOS flaw is bricking MacBooks: Don't install this update

#176

Post by ozim »

mmcnl wrote: post #165
cygned wrote: post #148

Earlier quoted context omitted.

Brown M&Ms ( https://www.entrepreneur.com/article/232420 ). How am I supposed to assume your content is of any quality if you cannot get the details right?

Typical HN response, there is no multi-million dollar exchange going on here. How about filling in some of the blanks or correct the wrong parts yourself? This is such an unnecessary defensive response.

Great I love this response!

People go into Karen mode here, yes they bought expensive piece of hardware with expensive operating system. Though site is rather technically minded they still underestimate how complex are those things.

It just another "Dropbox? Who needs that I can do the same in an hour", but somehow they don't realize when you have a budget, timelines and as always not enough developers who understand this specific thing - it is different than sitting on your own and making perfect thing. (which then if scrutinized by some other dev would be labeled as crap :D)

Re: Nasty macOS flaw is bricking MacBooks: Don't install this update

#177

Post by m463 »

sakisv wrote: post #172

I think that Apple should take advantage of the lockdowns and focus just on fixing things. They don't need to ship anything new and they have the perfect excuse to focus on improving both their OS and their processes that allowed such flawed things to reach their users.

hmmm... I wonder if that will be easier or harder.

Usually fixing bugs requires access to specific repro machines, and bricking might require access to a lab with jtag style hardware.

makes me wonder what the realities of telecommuting really are.

Re: Nasty macOS flaw is bricking MacBooks: Don't install this update

#178

Post by yodsanklai »

sv9 wrote: post #67

I'm consistently amazed by HN's ability to take the most meaningless, inconsequential part of an article (the scroll behavior, the whitespace, the usage of the word "bricked"), and nitpick it to hell and back instead of actually discussing the article. Bravo.

> the usage of the word "bricked"

Well, this is not nitpicking. The word "bricked" has a meaning, and this is not what the article describes. From the title, I thought that this update was actually bricking the computer. Thanks to the commenters for pointing it wasn't the case.

Re: Nasty macOS flaw is bricking MacBooks: Don't install this update

#179

Post by jsjddbbwj »

encom wrote: post #118
diebeforei485 wrote: post #25

I think companies are pushing updates way too aggressively to those who have auto update on. Is there some reason why phased release isn't more common among OS/firmware updates? Auto update does not have to mean "update my device the day new versions are out". Edit: Is this related to public disclosure of security bugs? If so, the community should change their standard so that public disclosure doesn't happen until a…

What OS X and Windows, IOS, Android and probably lots of others need, is Long Term Support releases. I'm so sick and tired of my phone and computer switching up major features and UI every year, because some UX person wants to not get fired. Releasing a new major version of your OS yearly is insane.

Windows has LTSC

Re: Nasty macOS flaw is bricking MacBooks: Don't install this update

#180

Post by nikofeyn »

yodsanklai wrote: post #178
sv9 wrote: post #67

I'm consistently amazed by HN's ability to take the most meaningless, inconsequential part of an article (the scroll behavior, the whitespace, the usage of the word "bricked"), and nitpick it to hell and back instead of actually discussing the article. Bravo.

> the usage of the word "bricked" Well, this is not nitpicking. The word "bricked" has a meaning, and this is not what the article describes. From the title, I thought that this update was actually bricking the computer. Thanks to the commenters for pointing it wasn't the case.

and yet, there are responses here confirming that the bricking is indeed what happens in some cases. so yes, it is nitpicking.
Post reply on HN