i'm not offending developers who spend their precious time on this fantastic piece of work, just some thought about it
why not ditch wbfs and simply use FAT?
originally posted here: libwbfs thead

why not ditch wbfs and simply use FAT?
originally posted here: libwbfs thead
QUOTE said:Pros:
1st, we can simply translate ISO's into wbfs dump and copy them to a FAT file system on any OS, utilities only needs access to files, while accessing raw partition is, harder, at least in some situations, for example the windows utility takes drive letter to indicate the partition, got some report that users lost their drive letter, and windows was unable to assign a new driver letter to an unrecognized partition.
2nd, becoz of wbfs, if we wanna use sd loader, we have to partition it, this is not a big deal for linux users but windows can't create partitions on "removable drives", even if you created it under linux, windows can't recognize the later partitions after the first one.
3rd, miserable bugs like delete a game corrupt the whole file system will surely be gone.
4th, avoid partition on sd card also makes use of every bytes of our tini tiny little sd card simpler, imagine you've partitioned your 16GB sd card like this: FAT 1GB for homebrew/VC on SD, 15GB for wbfs, one day your FAT partition exceed it's capacity and you wanna install a new VC, you're f*cked and have to repartition the whole damn card even you have space in the wbfs partition.
Cons:
1st, the damn 4GB FAT32 file size cap, not quite a big deal, we can simply split the dump like ssbb.001/ssbb.002
2nd, additional FAT layer may slower the load speed a bit, not quite a big deal again since it will still way better than the optical drive, i think.
well i have not read the source code extensively, but theoradically that could be possible as of my acknowledgement, if i'm wrong, plz point me out