Live data from Hacker News

macOS Tahoe brings a new disk image format

eclecticlight.co

111–120 of 152 posts

Re: macOS Tahoe brings a new disk image format

#111

Earlier quoted context omitted.

I have an unusual way of communicating sometimes that used to be quirky and fun. Now I simply get accused of being a bot. Before LLMs I never got accused of being a robot. I think the idea of good writing is soon going to morph with writing that doesn’t feel like it was made with AI.

It drives me crazy that em-dashes are supposedly a smell for AI now. The em-dash is a great and underused bit of punctuation. I am just glad I am not in college dealing with all the AI and faulty AI detection crap happening. Ridiculous false accusations of plagiarism were already awful enough before this.

> It drives me crazy that em-dashes are supposedly a smell for AI now.

They're an excellent tell for comments written on places like HN, Reddit, and other forms of social media. The average person (myself included) simply does not write very well and I would wager the majority of English speakers are not able to properly use an em-dash.

I expect them in books and suspect that's where the AI models are getting them from, but those are being written largely by professionals.

It's at a point where the moment I see an em-dash on a social media post I cease reading it and move on to the next.

Re: macOS Tahoe brings a new disk image format

#112
post #110
post #2

My kingdom for a documented disk image format.

I'll take your kingdom! ISO 9660. https://www.iso.org/iso-9660-images-for-computer-files.html VMDK https://en.wikipedia.org/wiki/VMDK Amiga https://en.wikipedia.org/wiki/Amiga_Disk_File UDF https://en.wikipedia.org/wiki/Universal_Disk_Format Apple Disk Image https://en.wikipedia.org/wiki/Apple_Disk_Image

VMDK isn't documented there, and is a container for multiple partially documented - and some only reverse engineered - subformats.

Re: macOS Tahoe brings a new disk image format

#113

Nice. But I would like it better if the effort was to support ext4, BtrFS, NTFS and other popular filesystems from the Linux and Windows world...

Does anybody else think that it would make sense for Apple and Microsoft to just get in a room and horse trade a few things like this, if they cared about user experience? Cross-license both APFS and NTFS, and share any internal documentation under NDA so that external drives can use modern formats with safety features like journaling without locking users in.

Oh wait, I just answered my question.

Re: macOS Tahoe brings a new disk image format

#114
post #74

[flagged]

I think this is actually a human struggle - I add Conclusions to my blog posts / dev guides because it feels awkward to just end with the last step. But it also always feels like I am just awkwardly restating things I just said. It's not a thesis, an article generally not complicated enough to need a re-synthesizing of main points at the end.

I used to love em dashes. But now I can't use them anymore — people will think it's written by AI.

Re: macOS Tahoe brings a new disk image format

#116

Earlier quoted context omitted.

3rd party supporting a file system would be one of the last things on a list of all software I’d ever want a 3rd party writing instead of the OS maker. Nightmare to evaluate the options, pure stress testing the options, difficult to know if it didn’t mess something up.

That being said: FSKit is a userspace API. In that respect, it's a lot better than filesystem code running in the kernel - it can't crash your computer or corrupt data on other filesystems, and it's much more tightly sandboxed if it gets exploited.

Exactly! Third party file systems support in user space is exactly what I want to see. It seems to me that third party kernel code has always caused me problems. By moving the FSKit to user-space, I’m quite happy to try something, knowing that it won’t affect the rest of my system.

Re: macOS Tahoe brings a new disk image format

#117
post #58
post #52

I have a meta question not directly related to the article but more about HN itself. I posted this exact link 9h before this submission was posted[1]. How is it possible that there is a new entry for the submission given the link is the same? [1] https://news.ycombinator.com/from?site=eclecticlight.co

Dupes are allowed after some number of hours.

It seems like, if the link is the same, submitting a dupe should just raise the original.

Re: macOS Tahoe brings a new disk image format

#118
post #7

Earlier quoted context omitted.

Apple recently made FSKit a supported/documented API, which should allow third-parties to add support for other filesystems: https://developer.apple.com/documentation/fskit?language=obj...

3rd party supporting a file system would be one of the last things on a list of all software I’d ever want a 3rd party writing instead of the OS maker. Nightmare to evaluate the options, pure stress testing the options, difficult to know if it didn’t mess something up.

I'd be happy for VeraCrypt not to have to rely on MacFuse which requires I go turn off some very low-level protection to even use. It sounds like this makes that possible.

I don't really understand your objection to be honest. Drivers for storage are common on other platforms

Re: macOS Tahoe brings a new disk image format

#120
post #101
post #10

Earlier quoted context omitted.

This article describes a new disk image format (on which a filesystem can be put, APFS in the article), not a filesystem, or did I misunderstand? edit: added the word "image", which I apparently forgot to type. Mentioning the edition because otherwise it would make an answer to this comment difficult to understand.

Yeah and OP was asking, why was effort spent on a disk image format rather than a file system. Seems like a reasonable question to ask.

Not any more reasonable than asking why they added new transparency effects instead of btrfs support
Post reply on HN