It is obvious NTFS is the top critical priority over all file systems out there (except for FAT32) since it comes by default on all Windows products. BTRFS can shall wait for a bit until the rest of the development is done and buggy-free.

You know that the main reason for Pierre Schweitzer to add a big amount of IFS drivers is mainly bugfixing? I hope so... Check recent commits of him and you know what he is doing. All these commits are needed for NTFS sooner or later too

ReactOS is still in alpha stage, meaning it is not feature-complete and is recommended only for evaluation and testing purposes.

Fraizeraust wrote:It is obvious NTFS is the top critical priority over all file systems out there (except for FAT32) since it comes by default on all Windows products. BTRFS can shall wait for a bit until the rest of the development is done and buggy-free.

NTFS will be developed only if we have developer assigned to it. But we do not have one, until CoderTrevor decides to continue his work. At the moment I see him on hiatus.

In case of BTRFS we have a developer who is assigned to it, and thus it will make progress. And BTEFS driver is already in mature and in feature complete state.

Fraizeraust wrote:It is obvious NTFS is the top critical priority over all file systems out there (except for FAT32) since it comes by default on all Windows products. BTRFS can shall wait for a bit until the rest of the development is done and buggy-free.

NTFS will be developed only if we have developer assigned to it. But we do not have one, until CoderTrevor decides to continue his work. At the moment I see him on hiatus.

In case of BTRFS we have a developer who is assigned to it, and thus it will make progress. And BTEFS driver is already in mature and in feature complete state.

Winbtrfs* There is a difference between btrfs and Winbtrfs. btrfs has been stable for a long time now, but only recently winbtrfs was made stable, with 1.0 released September 4th 2017. btrfs was also made by a variety of people and organizations (facebook, oracle, intel, and of course red hat and Linux foundation) where as winbtrfs is only being made by one person.

Anyways, it was reported that btrfs is slightly faster then ntfs. btrfs also has higher limitations then ntfs. ntfs = volume 256tb, file size 16eb and around 4 million max files vs btrfs = 16EB for both volume and file size and around 18 quintillion max files. btrfs is also more evolve in general as the last updates to ntfs were in 2001 when XP was released vs btrfs still being updated to this day.

However, MS will probably eventually replace ntfs with ReFS, as that has become the standard for the server edition of windows now. I don't know much about ReFS other then it has no limits to max files and the volume and max file size are pretty much tripled compared to btrfs.

Jedi-to-be wrote:And we should not forget that feature complete NTFS driver in ReactOS still does not exist. And will not exist in next 2 years approx.While WinBTRFS is almost ready.

And? ReactOS itself is still far from production ready. What does it matter if the NTFS driver takes the same amount of time ReactOS would take to become more stable? It's not as if switching from FAT right now would mean anything when so many other parts of the kernel have severe stability issues at the moment.

You have all the positive aspects of ZFS, like included Software RAIDs etc. The FS is a nice thing. But NTFS will follow sooner or later.And if our devs skilled in that direction have no spare time to do that, then we have to wait. I already explained that to you @jedi-to-be and a accusation/attack against Trevor is not what I wanna see here!

ReactOS is still in alpha stage, meaning it is not feature-complete and is recommended only for evaluation and testing purposes.