Hacker News Reader

Comment by lovelyviking | Hacker News Reader

And when I just have bought M1 machine and shared my impressions here I was heavily downvoted because I've stated: "It's the buggiest machine I ever had" If such basic functionality as bluetooth support is not working what is wrong with such statement?

People were claiming (without any proof) that I simply stumble on malfunctioning hardware ... The hardware is still ok till this very day according to all tests and all problems were and are software related. I have discovered that many of them are well known too.

So, no dears, it's not hardware. I've just seen better quality before. I should repeat: This is the buggiest machine I ever had and I am going to repeat it untill it is fixed. But looks like they have something more important to do then care about quality and customers. For instance downvoting what real people experience. Downvote reality as mush as you wish. Good luck with that.

View on HN

The thunderbolt issues follow to the Intel based machines too, not just M1. Hellacious issues if you need to hot unplug a thunderbolt display and take a laptop somewhere; something about USBC not picking back up the thunderbolt assignments when reconnected. The display functions/reasserts itself, but none of the peripheral ports function until after the OS restarts. From this state, if I wake up the device twice from sleep with a Bluetooth mouse the OS will immediately reboot on the second wakeup(kernel panic message).

After reboot the tbolt display functions until the next hot unplug. Rinse, repeat.

All first party gear.

Is there any operating system left now that isn't riddled with bugs? I blame Agile.

This probably isn't everyone's experience but I have Windows 10 Enterprise and it runs for months at a time whilst staying very stable. Can't fault it really.

And you'd be wrong.

First, I am not aware of any operating systems that are developed using agile methods, and second the empirical evidence is in that agile improves quality, so it would be better if they were.

https://www.amazon.com/Accelerate-Software-Performing-Techno...

It was joke. Your position looks rather like the true Scottmans fallacy to me.

1. The fallacy is called the "No true Scotsman". The "No" is rather important. :-)

https://en.wikipedia.org/wiki/No_true_Scotsman

2. And no, my position has nothing whatsoever to do with the "no true scotsman". I am not saying that they couldn't possibly be using agile because they have bad quality. I am saying that I am not aware of any of them using agile, and I was closely associated with at least one of them for a while.

And I also separately cite the evidence that has now been produced that agile improves quality, and conclude that if there are quality problems as you claim, a more agile approach would likely help, at least according to the empirical evidence.

¯\_(ツ)_/¯

Given your rather patronising replies, I suspect the original joke was lost on you. The issue is not Agile per se, it is organisations assuming that "Agile" will solve all their problems, where "Agile" usually means vendor products, forced rituals and tick boxes. Yet more Agile evangelism does not address this problem.

What organisations need more than anything is open minded individuals that are not slaves to established dogma. The Agile manifesto actually says that all methods should be constantly re-evaluated to see if they fit the particular organisation/team. Your empirical "evidence" likely comes with a lot of context and is unlikely to be applicable to all organisations and/or domains.

And all that was supposed to be read into

> Is there any operating system left now that isn't riddled with bugs? I blame Agile.

I think not.

If anything, that deserved even more patronizing replies.

> And all that was supposed to be read into.

Of course not, I am however attempting to explain in detail why such sacrilegious "blame Agile" comments might be made.

> If anything, that deserved even more patronizing replies.

I am highly suspicious of anyone who is so certain of their position, we should all be riven by doubt!

The interesting thing is that, for me, my Intel Macs with Catalina were, by far, the buggiest Macs I've used: my general experience of Big Sur is that it's probably the best release since High Sierra.

I intentionally avoided Catalina completely.

I did for a long time, but I installed it 3 months ago and it’s been fine. The problem with contingent bugs that only occur in rare circumstances is most people will never see them at all, but the few people that regularly do that thin will encounter the bug all the time, so individual anecdotes can be misleading.

With all respect I have experience in QA and I am not talking about individual anecdotes. I am talking about well known problems that are easy to reproduce if you wish to look for them. It took me 10 minutes to discover few of them. Then I've googled and found that many people found them. If I did find it during 10 minutes what makes it impossible for Apple to find it? It wasn't that hard at all for me ... I wasn't even trying hard ... So it's not about individual misleading anecdotes, it's about tendency of poor quality in my opinion.

May be we have different standards for quality?

Could you give any examples? The only bug I've found so far in my m1 macbook pro is an annoying flash of white color on the menu bar when using dark themes. Other than that it's been really smooth

Kernel panics when Bluetooth and thunderbolt are involved.

taking it from here: https://news.ycombinator.com/item?id=27708576

" One of them : My machine just didn't even boot after update ... It didn't boot without 'another' mac. What genius decided that to revive my machine I should have another machine? But even during this process it barely worked after ~10 tries because ... well bugs even there. With all my huge experience I couldn't figure out the scenario that was working for sure ... just pure luck. This is horrible experience I think. "

But honestly back then I was giving concrete examples and was heavily downvoted for the facts. In my opinion Apple people do it on purpose here. Back then easily reproducable bug was with setting internal mic for screen video recording as audio input source. Then you get delay 2 seconds with each screen shot even when you do not record video. I don't know if it's fixed now. Another one was related to 'do not disturb' mode untill you put moon icon near the clock. Few bugs in disk utility. Bug in textedit . It simply stuck with certain font size. Honesly I've stopped counting. Why should I make tests for them? The do not pay me for that. Let them enjoy it especially since they downvote reporting about it as you can see here again. Good luck with that.

Thanks for the examples. I'll pay closer attention. I've definitely noticed the long delay while taking screenshots, but because this is my first mac I thought it was just the usual delay or something

Maybe your another device is the source of the bluetooth issue. I'm pairing iPhone and Jabra headset every day with m1 Air without any issues (BigSur).

OP has bluetooth problems. I had many other problems and after some googling I've found that all of them were well known and were not fixed. You can digg in my comments for more details. One of them : My machine just didn't even boot after update ... It didn't boot without 'another' mac. What genius decided that to revive my machine I should have another machine? But even during this process it barely worked after ~10 tries because ... well bugs even there. With all my huge experience I couldn't figure out the scenario that was working for sure ... just pure luck. This is horrible experience I think.

For me there is no sense anymore to discuss each and every problem specifically when I sense tendency. I wouldn't make noise about few unfixed bugs but it's scary to see the tendency toward poor quality when your workflow and your sw project depends on MacOS.

How I suppose to make perfect file manager if underlying OS is not functioning properly?

Sorry to hear about such awful experience with M1 Mac. Hope you'll be able to replace it using "trade in" this autumn.

Reply on news.ycombinator.com