Personal achivement: - I built my own OS and C compiler
Looks really impressive today, but perhaps it was the norm 3 or 4 decads ago. Anyway, I envy such people who can do that. Let me try that once again.... :)
>...faded lineprinter paper show that the bulk of the work on OMU dates from March/April/May 1984... by mid 1984 I had a perfectly usable O/S
It's impressive that Hosgood made what he did when he did. It's equally impressive for an entirely different set of reasons that modern CS students can burn through that in a semester. Or you could look it up on WikiHow.
Eventually I added a VGA frame buffer, PS/2 keyboard module and RS-232 support and made it work as a terminal. By connecting 2 of these 'computers' with a null-modem cable, we would have a little chat-box application to display during open days at my university.
Ironically, I was once rejected for a programming job because I studied electronics, not computers. So clearly I didn't know how computers worked.
And computer.
You said ‘indeed’ which makes it look like you are saying this is true?
I think you may be confusing the ignition switch or key, with the ignition of fuel in the engine.
The ignition of fuel is absolutely necessary for internal combustion engines, just as a full file system was always necessary for iOS.
There is nothing on the iOS experience that requires a file system with POSIX semantics.
In fact that isn't what app developers using directly, rather Objective-C and Swift abstractions of a file system.
This is true, and is why using it as an analogy doesn’t work.
> There is nothing on the iOS experience that requires a file system with POSIX semantics.
Nobody mentioned posix before now. This is moving the goalposts.
> In fact that isn't what app developers using directly, rather Objective-C and Swift abstractions of a file system.
This is not true.
iOS provides all levels of Unix file system access from posix and libc upwards. Many apps and libraries make use of lower level access than Swift and Obj-C apis.
In addition, even those abstractions won’t work without a file system. They depend on concepts like files and directories.
This is why iOS had to have one when it shipped, and why a car power train is not a valid analogy.
Last time I checked, UNIX and POSIX go hand in hand, no one is moving goalposts here.
The existence of a file system has nothing to do with UNIX, unless you now mean only UNIX has filesystems.
https://developer.apple.com/library/archive/documentation/Fi...
Nobody said a POSIX file system was required.
The comment says that because iOS is a Unix, therefore it has a filesystem.
It doesn’t say anything about it needing to be POSIX.
The idea that anyone was saying it needed to be posix was introduced only by you and is moving the goalposts.
> The existence of a file system has nothing to do with UNIX,
The existence of the iOS filesystem has lot to do with Unix.
> unless you now mean only UNIX has filesystems.
I’m not sure why you’d think anyone would mean that.
Nothing in your comment addresses the problem with your analogy.
To recap:
iOS provides all levels of Unix file system access from posix and libc upwards. Many apps and libraries make use of lower level access than Swift and Obj-C apis.
In addition, even those abstractions won’t work without a file system. They depend on concepts like files and directories.
This is why iOS had to have one when it shipped, and why a car power train is not a valid analogy.
I would provide you the links to prove that, but I don't want to shatter dreams of UNIX worshiping.
Nobody here has said that. Even if they were, it would be irrelevant.
> I would provide you the links to prove that,
Why would you feel the need to prove something that nobody is disputing, and is irrelevant?
> but I don't want to shatter dreams of UNIX worshiping
Why would you think anyone here worships Unix?
As for its relevancy on iOS,
"POSIX Has Become Outdated"
http://www.cs.columbia.edu/~vatlidak/resources/POSIXmagazine...
By the way, the new secure networking APIs don't work with BSD sockets.