(EDIT: corrected link to comment)
There was no good reason to add the year.
No, that's not the reason for the HN convention. Why would someone even submit an article with out of date information?
The reason for the convention is that "news" is generally expected to be new, so when it's not new, HN readers want to be informed of that fact, and they can react to the submission accordingly. It's a simple courtesy to readers.
The incredulous tone of this hypothetical worries me, because I think this actually happens with troubling regularity.
Anything that good hackers would find interesting is on topic.[1] This includes some history.
The submitted article is not an historical review. If there was an article written explaining how Disk Utility had a bug, but the bug is now fixed, that might be interesting. On the other hand, to submit an article about a bug that no longer exists, with no explanation, would simply be misleading, out-of-date information. In this case, however, the bug still exists presently, so it's not history either.
I also reported a bug in Safari HTTP proxy handling that prevents encryption. No reply.
I provided source code, and reproduction steps for both.
Fuck Apple
So I emailed AppleInsider who did a short article about it and within two weeks another .x.x release came out and the bug was fixed.
Sadly I think this is one of the only ways to get big tech companies to take action these days. Cant tell you how many times I have read about Comcast, Verizon, etc screwing someone over and being unreasonable about it until theres an article on ArsTechnica or some similar site about it.
Apple is the only company that makes such terrible file systems. I have resized partitions on NTFS and EXT3 and never lost any data. Apple is uniquely terrible in terms of file systems and data integrity in general.
It just never works. And just when you think it's finally reliable and has worked for a while, it breaks in new unexpected ways. Sometimes hanging the whole machine. This was with both macOS as a server and a Linux server (less issues with Linux, but still broken).
Samba isn't great on other OSs either, but not as broken as on macOS. At this point I've given up on Samba completely, and consider it something I won't use again.
So is this the actual bug then? Because I just used Disk Utility (in Tahoe) to check and repair an AFPS volume and it appeared to do the right thing, with the caveat that I had to "eject" it manually since Disk Utility complained that stuff was using it. Presumably, booting into macOS Recovery would've worked, too.
If the author's reading, is there a way we can help amplify any existing bug report(s)?
rahimnathwani•3h ago
The Asahi installer couldn't resize the partition due to some orphan inodes or something.
Rebooting into Recovery mode and using Disk Utility (GUI) and diskutil (CLI) didn't fix the issues.
But `fsck_apfs -y` did the trick. I had to first do `diskutil unlock volume -nomount` as it was an encrypted volume.
jokowueu•2h ago
Igrom•4m ago
mixmastamyk•57m ago