The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
What universe are you living in? Having spent a significant amount of time living and working in Mexico, Venezuela, Ecuador and Bolivia I can tell you that the kids there lack a generous application of La Chancla.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
CP Daily News just landed in the inbox, with the following headline:
Why are there no true cross-platform filesystems? Well, there is: OpenAFS[^]
OpenAFS is a caching, distributed, network-based filesystem for securely and efficiently sharing files over a private network or over the internet. OpenAFS stores files on file server machines. OpenAFS clients read and write data to the file servers. Data is cached locally by clients, making subsequent reads very fast. File servers automatically notify clients when when data is changed, keeping data in sync. OpenAFS clients integrate with the client operating system to create a seamless network file system. Client side support is provided for wide-range of operating systems, including Windows, MacOS, Solaris, and Linux.
touch /dev/null wrote:
There isn’t a single quality modern filesystem that is cross-platform. NTFS is the closest, but it suffers from performance problems on non-Windows systems.
Maybe I should just buckle-down for the next 2-3 years, and make it myself. I am just more of a high-level developer. I live in languages that are interpreted or on VMs. I know enough C/C++ to get by, but not enough to make efficient OS drivers.
I think this is an issue that needs to be remedied. At least OSX and Linux. Windows can come after.
For the same reason there is no truly cross platform C library. Most devs who are capable of writing it are committed to 1 platform and either dont know the others well enough or in certain cases actively dont want to support Windows. Oh and the other reason of course is that Ive been more than a little busy
"The secret of happiness is freedom, and the secret of freedom, courage."
Thucydides (B.C. 460-400)
processor? Why would I want it to run on a processor? As far as I know processors aren't RESTless ... I think it's time to move forward, and in the spirit of the noSQL movement, we should rally around the noProcessor movement - no stacks, no instruction pointers, no registers, in short just say no ...
Because each platform is different and interacts with disks in a different way. What's important is that they can talk to each other (i.e. cross platform transfer protocols) and file system specs for removable media (which seem to be already cross platform). A system that can work everywhere by definition isn't taking advantage of platform-specific features so it will always be less usable than the specialised system for that platform.